From: Greg KH <gregkh@linuxfoundation.org>
To: Moritz Fischer <mdf@kernel.org>
Cc: linux-fpga@vger.kernel.org
Subject: Re: [GIT PULL] FPGA Manager change for 5.18-rc1
Date: Thu, 10 Mar 2022 22:39:16 +0100 [thread overview]
Message-ID: <YipwBCr5AbTDarAp@kroah.com> (raw)
In-Reply-To: <Yhx9R+OJ/Q3pwKi5@archbook>
On Sun, Feb 27, 2022 at 11:44:07PM -0800, Moritz Fischer wrote:
> On Mon, Feb 28, 2022 at 05:50:08AM +0100, Greg KH wrote:
> > On Sun, Feb 27, 2022 at 02:07:10PM -0800, Moritz Fischer wrote:
> > > The following changes since commit 21f0a239ecab4b6765269af78904512358beb802:
> > >
> > > fpga: dfl: pci: Remove usage of the deprecated "pci-dma-compat.h" API (2022-01-25 11:25:50 -0800)
> > >
> > > are available in the Git repository at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/mdf/linux-fpga.git tags/fpga-for-5.18-rc1
> > >
> > > for you to fetch changes up to 21f0a239ecab4b6765269af78904512358beb802:
> > >
> > > fpga: dfl: pci: Remove usage of the deprecated "pci-dma-compat.h" API (2022-01-25 11:25:50 -0800)
> > >
> > > ----------------------------------------------------------------
> > > FPGA Manager changes for 5.18-rc1
> > >
> > > Christophe's patch is part of a larger effort of removing the use of the
> > > deprecated pci-dma-compat API.
> > >
> > > All patches have been reviewed on the mailing list, and have been in the
> > > last few linux-next releases (as part of our for-next branch) without issues.
> > >
> > > Signed-off-by: Moritz Fischer <mdf@kernel.org>
> > >
> > > ----------------------------------------------------------------
> >
> > No diffstat?
>
> Ugh, yeah. Turns out there's no diff between fpga-for-5.18-rc1 and
> fpga-for-5.18-rc1.
>
> I can re-send ...
>
> Should've read like this:
>
> The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:
>
> Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mdf/linux-fpga.git tags/fpga-for-5.18-rc1
>
> for you to fetch changes up to 21f0a239ecab4b6765269af78904512358beb802:
>
Sorry for the delay, now pulled and pushed out.
greg k-h
prev parent reply other threads:[~2022-03-10 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 22:07 [GIT PULL] FPGA Manager change for 5.18-rc1 Moritz Fischer
2022-02-28 4:50 ` Greg KH
2022-02-28 7:44 ` Moritz Fischer
2022-03-10 21:39 ` 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=YipwBCr5AbTDarAp@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-fpga@vger.kernel.org \
--cc=mdf@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox