From: Stefan Schmidt <stefan@datenfreihafen.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Alexander Aring <alex.aring@gmail.com>
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 wpan-next tree
Date: Mon, 30 Sep 2024 07:53:31 +0200 [thread overview]
Message-ID: <ca2fd1e7-772a-4c77-af11-7f1156a7a506@datenfreihafen.org> (raw)
In-Reply-To: <20240930111849.09fa7c9a@canb.auug.org.au>
Hello Stephen,
On 9/30/24 03:18, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the wpan tree as a different commit
> (but the same patch):
>
> ace2b5331355 ("net: ieee802154: mcr20a: Use IRQF_NO_AUTOEN flag in request_ir
> q()")
>
> This is commit
>
> 09573b1cc76e ("net: ieee802154: mcr20a: Use IRQF_NO_AUTOEN flag in request_irq()")
>
> in the wpan tree.
Totally my fault. This should only be in wpan. I will get rid of it in
wpan-next.
Thanks for letting us know.
regards
Stefan Schmidt
prev parent reply other threads:[~2024-09-30 6:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 1:18 Stephen Rothwell
2024-09-30 5:53 ` Stefan Schmidt [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=ca2fd1e7-772a-4c77-af11-7f1156a7a506@datenfreihafen.org \
--to=stefan@datenfreihafen.org \
--cc=alex.aring@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--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
all inboxes | Powered by JetHome®