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>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: Jianlin Li <ljianlin99@gmail.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 tip tree
Date: Wed, 04 Oct 2023 07:32:26 -0600	[thread overview]
Message-ID: <874jj64iol.fsf@meer.lwn.net> (raw)
In-Reply-To: <20231004133306.3285d8de@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):
>
>   c53cbc54ccff ("x86/iommu/docs: Update AMD IOMMU specification document URL")
>
> This is commit
>
>   73c5f76ecbdb ("x86/iommu/docs: Update AMD IOMMU specification document URL")
>
> in the jc_docs tree.

Hmm...I thought I even checked for that.  No worries, I can drop my
copy.

Thanks,

jon

  reply	other threads:[~2023-10-04 13:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04  2:33 linux-next: duplicate patch in the tip tree Stephen Rothwell
2023-10-04 13:32 ` Jonathan Corbet [this message]
2023-10-04 15:41   ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2024-03-11 21:28 Stephen Rothwell
2023-06-02  3:04 Stephen Rothwell
2023-06-02 17:05 ` Andrew Morton
2023-01-13  1:40 Stephen Rothwell
2023-01-13 16:27 ` Jonathan Corbet
2023-01-13 21:51   ` 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=874jj64iol.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=ljianlin99@gmail.com \
    --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).