From: Helge Deller <deller@gmx.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Parisc List <linux-parisc@vger.kernel.org>,
Randy Dunlap <rdunlap@infradead.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, 1 Mar 2023 04:34:46 +0100 [thread overview]
Message-ID: <b675efb2-19ac-ac2b-a86d-98b2c2841956@gmx.de> (raw)
In-Reply-To: <20230301101303.2223f88e@canb.auug.org.au>
On 3/1/23 00:13, Stephen Rothwell wrote:
> The following commit is also in the parisc-hd tree as a different commit
> (but the same patch):
>
> 586dc36226dd ("Input: hp_sdc_rtc - mark an unused function as __maybe_unused")
>
> This is commit
>
> ab898955932e ("input/misc: hp_sdc_rtc: mark an unused function as __maybe_unused")
>
> in the parisc-hd tree.
I've dropped the patch from my git tree.
Helge
next prev parent reply other threads:[~2023-03-01 3:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 23:13 linux-next: duplicate patch in the input tree Stephen Rothwell
2023-03-01 3:34 ` Helge Deller [this message]
2023-12-13 20:45 Stephen Rothwell
2023-12-14 5:29 ` Dmitry Torokhov
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=b675efb2-19ac-ac2b-a86d-98b2c2841956@gmx.de \
--to=deller@gmx.de \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=rdunlap@infradead.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).