From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jonathan Corbet <corbet@lwn•net>
Cc: Thomas Gleixner <tglx@linutronix•de>,
Ingo Molnar <mingo@redhat•com>, "H. Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@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 tip tree
Date: Sat, 14 Jan 2023 08:51:53 +1100 [thread overview]
Message-ID: <20230114085153.59c0866e@canb.auug.org.au> (raw)
In-Reply-To: <87358es8lh.fsf@meer.lwn.net>
[-- Attachment #1: Type: text/plain, Size: 324 bytes --]
Hi Jon,
On Fri, 13 Jan 2023 09:27:38 -0700 Jonathan Corbet <corbet@lwn•net> wrote:
>
> I'm sure I checked before applying that ... I guess maybe not. I've
> disappeared it now, thanks.
You may well have checked, both commits appeared in linux-next for the
first time yesterday.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-01-13 21:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 1:40 linux-next: duplicate patch in the tip tree Stephen Rothwell
2023-01-13 16:27 ` Jonathan Corbet
2023-01-13 21:51 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-02 3:04 Stephen Rothwell
2023-06-02 17:05 ` Andrew Morton
2023-10-04 2:33 Stephen Rothwell
2023-10-04 13:32 ` Jonathan Corbet
2023-10-04 15:41 ` Ingo Molnar
2024-03-11 21:28 Stephen Rothwell
2024-09-11 5:24 Stephen Rothwell
2024-10-29 2:34 Stephen Rothwell
2024-10-29 4:30 ` Andrew Morton
2024-10-29 6:05 ` Stephen Rothwell
2024-10-29 7:52 ` Thomas Gleixner
2024-10-29 11:08 ` Peter Zijlstra
2025-01-15 5:33 Stephen Rothwell
2025-02-27 3:44 Stephen Rothwell
2025-02-27 3:48 ` Stephen Rothwell
2025-02-27 4:40 ` Andrew Morton
2025-04-16 3:21 Stephen Rothwell
2025-04-16 14:38 ` Gregory CLEMENT
2025-05-07 3:22 Stephen Rothwell
2025-05-07 7:55 ` Thomas Gleixner
2025-05-07 17:44 ` Ingo Molnar
2025-05-12 5:04 Stephen Rothwell
2025-07-08 6:00 Stephen Rothwell
2025-07-08 6:48 ` Andrew Morton
2025-07-09 9:17 ` Borislav Petkov
2025-07-09 19:12 ` Andrew Morton
2025-07-09 19:43 ` Borislav Petkov
2025-09-12 3:09 Stephen Rothwell
2025-09-16 8:37 ` Lee Jones
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=20230114085153.59c0866e@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=corbet@lwn$(echo .)net \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@redhat$(echo .)com \
--cc=peterz@infradead$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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