From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.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 clockevents tree
Date: Fri, 16 May 2025 11:11:46 +0200 [thread overview]
Message-ID: <de1e4c74-2ee6-46fb-b058-db3bb72bc346@linaro.org> (raw)
In-Reply-To: <20250516164342.74fd3f15@canb.auug.org.au>
On 5/16/25 08:43, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the tip tree as a different commit
> (but the same patch):
>
> 1732e45b79bb ("genirq: Fix typo in IRQ_NOTCONNECTED comment")
>
> This is commit
>
> 0128816c42b5 ("genirq: Fix typo in IRQ_NOTCONNECTED comment")
>
> in the tip tree.
Fixed, thanks!
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2025-05-16 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 6:43 linux-next: duplicate patch in the clockevents tree Stephen Rothwell
2025-05-16 9:11 ` Daniel Lezcano [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-22 1:45 Stephen Rothwell
2025-07-16 10:48 Stephen Rothwell
2025-07-16 13:13 ` AngeloGioacchino Del Regno
2024-10-17 7:20 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=de1e4c74-2ee6-46fb-b058-db3bb72bc346@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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).