fromupstream: use lore.kernel.org, not lkml.kernel.org

Per the sysadmin's recommendation ;)
https://lore.kernel.org/ksummit-discuss/CAMwyc-RX7Sin1W=m8OXeq81TqT1Auhuxm=htgekXFpHHdgu3Yg@mail.gmail.com/

They're effectively identical, but 'lore' doesn't imply that the message
must be on LKML proper.

BUG=none
TEST=none

Change-Id: If4eedd992716ab2b66bde27c86054457e6930ce0
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/dev-util/+/2220183
Tested-by: Brian Norris <briannorris@chromium.org>
Auto-Submit: Brian Norris <briannorris@chromium.org>
Commit-Queue: Stephen Boyd <swboyd@chromium.org>
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
diff --git a/contrib/fromupstream.py b/contrib/fromupstream.py
index c8165bf..408d034 100755
--- a/contrib/fromupstream.py
+++ b/contrib/fromupstream.py
@@ -191,7 +191,7 @@
     if args['source_line'] is None:
         args['source_line'] = '(am from %s/patch/%d/)' % (url, patch_id)
         for url_template in [
-            'https://lkml.kernel.org/r/%s',
+            'https://lore.kernel.org/r/%s',
             # hostap project (and others) are here, but not kernel.org.
             'https://marc.info/?i=%s',
             # public-inbox comes last as a "default"; it has a nice error page