From: "Arnd Bergmann" <arnd@arndb.de>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the asm-generic tree
Date: Wed, 10 Jan 2024 08:37:35 +0100 [thread overview]
Message-ID: <a74946d3-3fa1-47ce-8dee-13123c0fdfca@app.fastmail.com> (raw)
In-Reply-To: <20240110083442.6728646c@canb.auug.org.au>
On Tue, Jan 9, 2024, at 22:34, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
>
> e8cf41b96bc9 ("asm-generic: make sparse happy with odd-sized
> put_unaligned_*()")
>
> This is commit
>
> 1ab33c03145d ("asm-generic: make sparse happy with odd-sized
> put_unaligned_*()")
>
> in Linus' tree.
I ropped mine now, thanks for the report. It was still on top
of the branch, so I'll just send the pull request without this
one.
Arnd
next prev parent reply other threads:[~2024-01-10 7:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 21:34 linux-next: duplicate patch in the asm-generic tree Stephen Rothwell
2024-01-10 7:37 ` Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-03 7:38 Stephen Rothwell
2024-07-01 21:46 Stephen Rothwell
2024-01-28 3:54 Stephen Rothwell
2023-12-06 2:33 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=a74946d3-3fa1-47ce-8dee-13123c0fdfca@app.fastmail.com \
--to=arnd@arndb.de \
--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