linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>
Cc: ARM <linux-arm-kernel@lists.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 jc_docs tree
Date: Mon, 14 Oct 2024 08:52:27 -0600	[thread overview]
Message-ID: <87r08iu47o.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20241014130336.06b99889@canb.auug.org.au>

Stephen Rothwell <sfr@canb.auug.org.au> writes:

> Hi all,
>
> The following commit is also in the arm-soc-fixes tree as a different
> commit (but the same patch):
>
>   6330e80ef1a2 ("Documentation/process: maintainer-soc: clarify submitting patches")
>
> This is commit
>
>   29ce0bca6d5f ("Documentation/process: maintainer-soc: clarify submitting patches")
>
> in the arm-soc-fixes tree.

I can drop my copy, I guess.

Thanks,

jon

  reply	other threads:[~2024-10-14 14:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14  2:03 linux-next: duplicate patch in the jc_docs tree Stephen Rothwell
2024-10-14 14:52 ` Jonathan Corbet [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-07  1:19 Stephen Rothwell
2025-05-07  6:51 ` Jonathan Corbet
2025-05-07  1:18 Stephen Rothwell
2025-02-19  0:32 Stephen Rothwell
2025-02-14  5:10 Stephen Rothwell
2025-02-14 13:20 ` Palmer Dabbelt
2025-01-17  1:02 Stephen Rothwell
2024-02-13  4:49 Stephen Rothwell
2024-02-13 14:36 ` Jonathan Corbet
2024-02-12 23:37 Stephen Rothwell
2024-02-12 23:41 ` Jonathan Corbet
2023-04-11  5:16 Stephen Rothwell
2023-04-11 22:16 ` Jonathan Corbet
2023-01-13  0:11 Stephen Rothwell
2023-01-13 16:29 ` Jonathan Corbet

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=87r08iu47o.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=olof@lixom.net \
    --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;
as well as URLs for NNTP newsgroup(s).