From: Kevin Hilman <khilman@baylibre.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Tony Lindgren <tony@atomide.com>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: update omap branches for linux-next
Date: Mon, 15 Jul 2024 10:18:12 -0700 [thread overview]
Message-ID: <7h5xt67ewb.fsf@baylibre.com> (raw)
Hi Stephen,
I'll be taking over from Tony on maintaining the omap trees for
linux-next.
Could you please update the omap entries for the trees/branches pulled
into linux-next? Patch below against next-20240715.
Thanks,
Kevin
diff --git a/Next/Trees b/Next/Trees
index 13308bb5322b..22b02f8c81ba 100644
--- a/Next/Trees
+++ b/Next/Trees
@@ -63,7 +63,7 @@ v4l-dvb-fixes git https://git.linuxtv.org/media_stage.git#fixes
reset-fixes git https://git.pengutronix.de/git/pza/linux#reset/fixes
mips-fixes git git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git#mips-fixes
at91-fixes git git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git#at91-fixes
-omap-fixes git git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git#fixes
+omap-fixes git git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap.git#fixes
kvm-fixes git git://git.kernel.org/pub/scm/virt/kvm/kvm.git#master
kvms390-fixes git git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git#master
hwmon-fixes git git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git#hwmon
@@ -134,7 +134,7 @@ drivers-memory git https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-me
imx-mxs git git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git#for-next
mediatek git git://git.kernel.org/pub/scm/linux/kernel/git/mediatek/linux.git#for-next
mvebu git git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu.git#for-next
-omap git git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git#for-next
+omap git git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap.git#for-next
qcom git git://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git#for-next
renesas git git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git#next
reset git https://git.pengutronix.de/git/pza/linux#reset/next
next reply other threads:[~2024-07-15 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 17:18 Kevin Hilman [this message]
2024-07-15 22:31 ` update omap branches for linux-next Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7h5xt67ewb.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox