From: Kevin Hilman <khilman@baylibre.com>
To: soc@kernel.org
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] ARM: dts: OMAP updates for v6.13
Date: Mon, 04 Nov 2024 11:03:46 -0800 [thread overview]
Message-ID: <7hikt2om7h.fsf@baylibre.com> (raw)
In-Reply-To: <7hmsieomrt.fsf@baylibre.com>
Kevin Hilman <khilman@baylibre.com> writes:
> The following changes since commit 9852d85ec9d492ebef56dc5f229416c925758edc:
>
> Linux 6.12-rc1 (2024-09-29 15:06:19 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap.git tags/omap-for-v6.13/dt-signed
>
> for you to fetch changes up to 13746595a1581e09289adf9b5202e237c5e0814b:
>
> ARM: dts: omap4-kc1: fix twl6030 power node (2024-11-04 10:42:22 -0800)
Oops, ignore this one. I got an email from linux-next that one of these
patches is missing an SoB. Will fixup and resend.
I deleted this tag to avoid pulling the wrong one.
Kevin
prev parent reply other threads:[~2024-11-04 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 18:51 [GIT PULL] ARM: dts: OMAP updates for v6.13 Kevin Hilman
2024-11-04 19:03 ` Kevin Hilman [this message]
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=7hikt2om7h.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=soc@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).