From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Rob Herring <robh@kernel.org>,
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 input tree
Date: Wed, 13 Dec 2023 21:29:11 -0800 [thread overview]
Message-ID: <ZXqSp_Fejj0XGuwX@google.com> (raw)
In-Reply-To: <20231214074546.453a926b@canb.auug.org.au>
Hi Stephen,
On Thu, Dec 14, 2023 at 07:45:46AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
>
> 877ee02cd962 ("dt-bindings: input: qcom,pm8921-keypad: convert to YAML format")
>
> This is commit
>
> 53ed3233e6b5 ("dt-bindings: input: qcom,pm8921-keypad: convert to YAML format")
>
> in Linus' tree.
Thank you for letting me know, I dropped the commit from my tree.
--
Dmitry
next prev parent reply other threads:[~2023-12-14 5:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 20:45 linux-next: duplicate patch in the input tree Stephen Rothwell
2023-12-14 5:29 ` Dmitry Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-28 23:13 Stephen Rothwell
2023-03-01 3:34 ` Helge Deller
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=ZXqSp_Fejj0XGuwX@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).