linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Baoquan He <bhe@redhat.com>,
	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 char-misc tree
Date: Mon, 7 Aug 2023 08:40:20 +0200	[thread overview]
Message-ID: <2023080703-renewable-rust-233d@gregkh> (raw)
In-Reply-To: <20230807154457.062a8a1a@canb.auug.org.au>

On Mon, Aug 07, 2023 at 03:44:57PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> The following commits are also in the mm tree as different commits
> (but the same patches):
> 
>   acdbfa04816a ("pcmcia : make PCMCIA depend on HAS_IOMEM")
>   aefc8b57af77 ("misc: open-dice: make OPEN_DICE depend on HAS_IOMEM")
>   806eb9e4160d ("char: xillybus: make XILLYBUS_OF depend on HAS_IOMEM")
> 
> These are commits
> 
>   2ef95c7f4177 ("pcmcia : make PCMCIA depend on HAS_IOMEM")
>   3650ce6d8409 ("misc: open-dice: make OPEN_DICE depend on HAS_IOMEM")
>   420d959a77fe ("char: xillybus: make XILLYBUS_OF depend on HAS_IOMEM")
> 
> in the mm tree.

Thanks for the notice, should be fine if they end up getting merged both
ways.

greg k-h

  reply	other threads:[~2023-08-07  6:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07  5:44 linux-next: duplicate patches in the char-misc tree Stephen Rothwell
2023-08-07  6:40 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-08  3:02 Stephen Rothwell
2024-01-08  7:54 ` Greg KH
2023-11-29  1:24 Stephen Rothwell
2023-11-29  9:26 ` Greg KH
2023-06-02  3:26 Stephen Rothwell
2023-06-02  7:54 ` Linus Walleij
2023-06-02  8:01   ` Greg KH

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=2023080703-renewable-rust-233d@gregkh \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=bhe@redhat.com \
    --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).