From: Kevin Hilman <khilman@baylibre.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the omap tree
Date: Mon, 16 Dec 2024 10:53:16 -0800 [thread overview]
Message-ID: <7ha5cvcvdv.fsf@baylibre.com> (raw)
In-Reply-To: <20241216113416.3e78369f@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> The following commit is also in the drivers-memory tree as a different
> commit (but the same patch):
>
> 56d96fc55390 ("memory: omap-gpmc: deadcode a pair of functions")
>
> This is commit
>
> 5119e6b44f8a ("memory: omap-gpmc: deadcode a pair of functions")
>
> in the drivers-memory tree.
Yes, this one was my fault. It's now dropped from the omap tree.
Kevin
next prev parent reply other threads:[~2024-12-16 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 0:34 linux-next: duplicate patch in the omap tree Stephen Rothwell
2024-12-16 18:53 ` Kevin Hilman [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-18 0:54 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=7ha5cvcvdv.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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