All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Peter Rosin <peda@axentia.se>,
	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 mux tree
Date: Mon, 13 Jan 2025 06:20:10 +0100	[thread overview]
Message-ID: <2025011357-deceased-press-cbae@gregkh> (raw)
In-Reply-To: <20250113142640.54d5eceb@canb.auug.org.au>

On Mon, Jan 13, 2025 at 02:26:40PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> The following commit is also in the driver-core tree as a different commit
> (but the same patch):
> 
>   49a9b01803e4 ("mux: constify mux class")
> 
> This is commit
> 
>   7685ad5f08d9 ("mux: constify mux class")
> 
> in the driver-core tree.

Thanks, this should be fine, I thought no one had picked it up :(

  reply	other threads:[~2025-01-13  5:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-13  3:26 linux-next: duplicate patch in the mux tree Stephen Rothwell
2025-01-13  5:20 ` Greg KH [this message]
2025-01-13  8:53   ` Peter Rosin
2025-01-15  9:50     ` Bartosz Golaszewski

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=2025011357-deceased-press-cbae@gregkh \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=peda@axentia.se \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.