linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the i2c tree
Date: Sun, 21 Jan 2024 13:27:07 +0100	[thread overview]
Message-ID: <Za0Nm2GvQjy51sqN@kunai> (raw)
In-Reply-To: <20240121200534.57bf614a@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 152 bytes --]


> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):

Thanks, I fixed my trees and pushed out now.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-01-21 12:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-21  9:05 linux-next: duplicate patches in the i2c tree Stephen Rothwell
2024-01-21 12:27 ` Wolfram Sang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-07-15  3:06 Stephen Rothwell
2025-07-15  8:01 ` Wolfram Sang
2024-01-07 21:24 Stephen Rothwell
2024-01-07 21:55 ` Wolfram Sang
2023-08-15  2:16 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=Za0Nm2GvQjy51sqN@kunai \
    --to=wsa@the-dreams.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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).