From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
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 s390 tree
Date: Thu, 19 Sep 2024 07:55:39 +1000 [thread overview]
Message-ID: <20240919075539.27f5b782@canb.auug.org.au> (raw)
In-Reply-To: <CAHmME9pX5AiKHGW=+umdDW-JDpHjqomDLstrCMLqCm13ZQ_+4g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Hi Jason,
On Wed, 18 Sep 2024 23:28:11 +0200 "Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>
> On Wed, Sep 18, 2024 at 11:26 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > The following commit is also in Linus Torvalds' tree as a different commit
> > (but the same patch):
> >
> > 0147addc4fb7 ("s390/facility: Disable compile time optimization for decompressor code")
> >
> > This is commit
> >
> > 26d4959681e3 ("s390/facility: Disable compile time optimization for decompressor code")
> >
> > in Linus' tree.
>
> From [1]:
>
> "Please note that the first patch of this series is already in linux-next
> [1], but given that it is so small it seems to be the easiest to apply it
> also on your tree; but I'm sure somebody will complain :)"
>
> So I think this is to be expected.
Yeah, no worries. I just report them in case there was a mistake or
lack of communication. Clearly not in this case.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-09-18 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 21:26 linux-next: duplicate patch in the s390 tree Stephen Rothwell
2024-09-18 21:28 ` Jason A. Donenfeld
2024-09-18 21:55 ` Stephen Rothwell [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=20240919075539.27f5b782@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Jason@zx2c4.com \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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