All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.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 nvmem tree
Date: Mon, 11 Dec 2023 11:34:19 +0100	[thread overview]
Message-ID: <20231211113419.327947a7@xps-13> (raw)
In-Reply-To: <20231211084841.11b2ee48@canb.auug.org.au>

Hi Stephen,

sfr@canb.auug.org.au wrote on Mon, 11 Dec 2023 08:48:41 +1100:

> Hi all,
> 
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
> 
>   05349b48e254 ("nvmem: Do not expect fixed layouts to grab a layout driver")
> 
> This is commit
> 
>   b7c1e53751cb ("nvmem: Do not expect fixed layouts to grab a layout driver")
> 
> in Linus' tree.
> 
> Also, please keep all the commit message tags together at the end of
> the commit message.
> 

This is actually fine, Srinivas needs this fix in his tree for
applying other patches, but he anyway sends a big "series" to GKH at
-rc6 who finally applies the content of the nvmem-next branch.

Thanks for the reports,
Miquèl

  reply	other threads:[~2023-12-11 10:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-10 21:48 linux-next: duplicate patch in the nvmem tree Stephen Rothwell
2023-12-11 10:34 ` Miquel Raynal [this message]
2023-12-11 11:09   ` Srinivas Kandagatla
  -- strict thread matches above, loose matches on Subject: below --
2025-11-25  6:17 Stephen Rothwell
2025-11-25  7:10 ` Greg KH
2025-07-14  7:34 Stephen Rothwell
2025-07-14  7:51 ` Greg KH
2024-06-12  6:28 Stephen Rothwell
2024-06-12 12:55 ` Rob Herring
2023-10-30  4:10 Stephen Rothwell
2023-10-30  6:46 ` Rafał Miłecki

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=20231211113419.327947a7@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=srinivas.kandagatla@linaro.org \
    /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.