From: Greg KH <gregkh@linuxfoundation.org>
To: Xu Yilun <yilun.xu@intel.com>
Cc: linux-fpga@vger.kernel.org, hao.wu@intel.com, mdf@kernel.org
Subject: Re: [GIT PULL] FPGA MAINTAINERS changes for 6.3-final
Date: Mon, 29 May 2023 14:50:54 +0100 [thread overview]
Message-ID: <2023052937-bluish-remold-48d4@gregkh> (raw)
In-Reply-To: <ZFYkMMpovbmoItUS@yilunxu-OptiPlex-7050>
On Sat, May 06, 2023 at 05:56:00PM +0800, Xu Yilun wrote:
> The following changes since commit dc70eb868b9cd2ca01313e5a394e6ea001d513e9:
>
> fpga: bridge: properly initialize bridge device before populating children (2023-04-07 00:10:04 +0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/fpga/linux-fpga tags/fpga-for-6.3-final-2
This doesn't apply at all anymore, can you resend these as patches?
thanks,
greg k-h
prev parent reply other threads:[~2023-05-29 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 9:56 [GIT PULL] FPGA MAINTAINERS changes for 6.3-final Xu Yilun
2023-05-29 13:50 ` Greg KH [this message]
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=2023052937-bluish-remold-48d4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=mdf@kernel.org \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).