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: Arnd Bergmann <arnd@arndb.de>, Moritz Fischer <mdf@kernel.org>,
	Xu Yilun <yilun.xu@intel.com>, Wu Hao <hao.wu@intel.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 char-misc tree
Date: Fri, 18 Jul 2025 09:54:22 +0200	[thread overview]
Message-ID: <2025071805-visibly-henna-b5a4@gregkh> (raw)
In-Reply-To: <20250718174129.24c0e968@canb.auug.org.au>

On Fri, Jul 18, 2025 at 05:41:29PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> The following commit is also in the fpga-fixes tree as a different commit
> (but the same patch):
> 
>   29f4103b2585 ("MAINTAINERS: Update FPGA MANAGER maintainer")
> 
> This is commit
> 
>   1c6a132cb309 ("MAINTAINERS: Update FPGA MANAGER maintainer")
> 
> in he fpga-fixes tree.

Yeah, I already applied this before the fpga tree did, we talked about
it :)

thanks

greg k-h

  reply	other threads:[~2025-07-18  7:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18  7:41 linux-next: duplicate patch in the char-misc tree Stephen Rothwell
2025-07-18  7:54 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-07-17  5:37 Stephen Rothwell
2025-07-17  6:01 ` Greg KH
2025-02-24  5:00 Stephen Rothwell
2025-02-24  6:16 ` Greg KH
2024-06-06  2:34 Stephen Rothwell
2024-01-08  3:07 Stephen Rothwell
2024-01-08  7:54 ` Greg KH
2024-01-08  2:58 Stephen Rothwell
2024-01-08  7:37 ` Helge Deller
2024-01-08  7:46   ` 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=2025071805-visibly-henna-b5a4@gregkh \
    --to=greg@kroah.com \
    --cc=arnd@arndb.de \
    --cc=hao.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mdf@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=yilun.xu@intel.com \
    /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.