From: Greg KH <gregkh@linuxfoundation.org>
To: Moritz Fischer <mdf@kernel.org>
Cc: moritzf@google.com, linux-fpga@vger.kernel.org
Subject: Re: [GIT PULL] FPGA Manager changes for 5.7
Date: Mon, 30 Mar 2020 16:15:06 +0200 [thread overview]
Message-ID: <20200330141506.GA438143@kroah.com> (raw)
In-Reply-To: <20200327162944.GA4118@epycbox.lan>
On Fri, Mar 27, 2020 at 09:29:44AM -0700, Moritz Fischer wrote:
> The following changes since commit bb6d3fb354c5ee8d6bde2d576eb7220ea09862b9:
>
> Linux 5.6-rc1 (2020-02-09 16:08:48 -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.7
>
> for you to fetch changes up to 3d5a5417ad064a6ca64a33f0c554d917311c79f4:
>
> fpga: dfl: afu: support debug access to memory-mapped afu regions (2020-03-21 13:14:30 -0700)
This is too late for 5.7-rc1 as stuff needed to be in my tree last week
(and not Friday), to give it time to test in linux-next.
Care to break this up into two trees, stuff for 5.7-final with bugfixes,
and stuff for 5.8-rc1?
thanks,
greg k-h
next prev parent reply other threads:[~2020-03-30 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 16:30 [GIT PULL] FPGA Manager changes for 5.7 Moritz Fischer
2020-03-30 14:15 ` Greg KH [this message]
2020-03-31 1:28 ` Moritz Fischer
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=20200330141506.GA438143@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-fpga@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=moritzf@google.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