From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alan Tull <atull@kernel.org>
Cc: Moritz Fischer <mdf@kernel.org>,
linux-kernel@vger.kernel.org, linux-fpga@vger.kernel.org
Subject: Re: [RESEND 0/2] fpga fixes for 4.20
Date: Mon, 12 Nov 2018 11:46:02 -0800 [thread overview]
Message-ID: <20181112194602.GA3329@kroah.com> (raw)
In-Reply-To: <1542051514-5205-1-git-send-email-atull@kernel.org>
On Mon, Nov 12, 2018 at 01:38:32PM -0600, Alan Tull wrote:
> Hi Greg,
>
> Here's a reposting of the two small fixes for fpga, please
> take them in. They've been reviewed on the mailing list
> and apply cleanly on today's char-misc-test.
This isn't a bugfix, they should just go into my "next" branch to be
merged for the next -rc1 release, right? I thought that is what I said
last time...
thanks,
greg k-h
prev parent reply other threads:[~2018-11-12 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 19:38 [RESEND 0/2] fpga fixes for 4.20 Alan Tull
2018-11-12 19:38 ` [RESEND 1/2] fpga: of-fpga-region: Use platform_set_drvdata Alan Tull
2018-11-12 19:38 ` [RESEND 2/2] fpga: dfl-fme-region: Use platform_get_drvdata() Alan Tull
2018-11-12 19:46 ` Greg Kroah-Hartman [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=20181112194602.GA3329@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=atull@kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@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 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.