From: Jonathan Corbet <corbet@lwn.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "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 tip tree
Date: Fri, 13 Jan 2023 09:27:38 -0700 [thread overview]
Message-ID: <87358es8lh.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230113124053.5a75633d@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> The following commit is also in the jc_docs tree as a different commit
> (but the same patch):
>
> 379af13b31fa ("docs: locking: Discourage from calling disable_irq() in atomic")
>
> This is commit
>
> ac6fadf4aa60 ("docs: kernel-hacking: discourage from calling disable_irq() in atomic")
>
> in the jc_docs tree.
I'm sure I checked before applying that ... I guess maybe not. I've
disappeared it now, thanks.
jon
next prev parent reply other threads:[~2023-01-13 16:33 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 [this message]
2023-01-13 21:51 ` Stephen Rothwell
-- 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=87358es8lh.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--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).