All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Xu Yilun <yilun.xu@linux.intel.com>
Cc: yilun.xu@intel.com, linux-fpga@vger.kernel.org, mdf@kernel.org
Subject: Re: [GIT PULL] FPGA Manager changes for 6.16-final
Date: Wed, 16 Jul 2025 19:22:01 +0200	[thread overview]
Message-ID: <2025071619-epic-confined-3bfd@gregkh> (raw)
In-Reply-To: <aHfYjZ62LMw2VCCU@yilunxu-OptiPlex-7050>

On Thu, Jul 17, 2025 at 12:51:25AM +0800, Xu Yilun wrote:
> The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
> 
>   Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/fpga/linux-fpga tags/fpga-for-6.16-final
> 
> for you to fetch changes up to 1c6a132cb30909aba5b37ffc1739f3c288330603:
> 
>   MAINTAINERS: Update FPGA MANAGER maintainer (2025-07-12 02:52:40 +0800)
> 
> ----------------------------------------------------------------
> FPGA Manager changes for 6.16-final
> 
> - FPGA DFL DRIVERS Maintainer change from Wu Hao to Yilun
> 
> All patches have been reviewed on the mailing list, and have been in the
> last linux-next releases (as part of our fixes branch)
> 
> Signed-off-by: Xu Yilun <yilun.xu@intel.com>
> 
> ----------------------------------------------------------------
> Xu Yilun (1):
>       MAINTAINERS: Update FPGA MANAGER maintainer
> 
>  MAINTAINERS | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)

I already took this in my -next branch, any reason it has to be in
6.16-final?

thanks,

greg k-h

  reply	other threads:[~2025-07-16 17:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16 16:51 [GIT PULL] FPGA Manager changes for 6.16-final Xu Yilun
2025-07-16 17:22 ` Greg KH [this message]
2025-07-17  1:55   ` Xu Yilun

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=2025071619-epic-confined-3bfd@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=mdf@kernel.org \
    --cc=yilun.xu@intel.com \
    --cc=yilun.xu@linux.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.