From: Alan Tull <atull@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Moritz Fischer <mdf@kernel.org>, Alan Tull <atull@kernel.org>,
linux-kernel@vger.kernel.org, linux-fpga@vger.kernel.org
Subject: [PATCH 0/5] fpga: patches for v4.19
Date: Wed, 12 Sep 2018 09:43:22 -0500 [thread overview]
Message-ID: <20180912144327.3130-1-atull@kernel.org> (raw)
Hi Greg,
Please take these five small patches for FPGA. They
have been reviewed on the mailing lists and apply cleanly
on linux-next/master and char-misc-testing.
Thanks,
Alan
Alan Tull (3):
fpga: do not access region struct after fpga_region_unregister
fpga: bridge: fix obvious function documentation error
docs: fpga: document fpga manager flags
Moritz Fischer (2):
fpga: of-fpga-region: Use platform_set_drvdata
fpga: dfl-fme-region: Use platform_get_drvdata()
Documentation/driver-api/fpga/fpga-mgr.rst | 5 +++++
drivers/fpga/dfl-fme-region.c | 6 ++++--
drivers/fpga/fpga-bridge.c | 2 +-
drivers/fpga/of-fpga-region.c | 5 +++--
include/linux/fpga/fpga-mgr.h | 20 ++++++++++++++------
5 files changed, 27 insertions(+), 11 deletions(-)
--
2.7.4
next reply other threads:[~2018-09-12 14:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 14:43 Alan Tull [this message]
2018-09-12 14:43 ` [PATCH 1/5] fpga: do not access region struct after fpga_region_unregister Alan Tull
2018-09-12 14:43 ` [PATCH 2/5] fpga: bridge: fix obvious function documentation error Alan Tull
2018-09-12 14:43 ` [PATCH 3/5] docs: fpga: document fpga manager flags Alan Tull
2018-09-12 14:43 ` [PATCH 4/5] fpga: of-fpga-region: Use platform_set_drvdata Alan Tull
2018-09-30 15:49 ` Greg Kroah-Hartman
2018-11-12 15:48 ` Alan Tull
2018-09-12 14:43 ` [PATCH 5/5] fpga: dfl-fme-region: Use platform_get_drvdata() Alan Tull
2018-09-30 15:48 ` Greg Kroah-Hartman
2018-11-12 15:46 ` Alan Tull
2018-11-12 18:02 ` Greg Kroah-Hartman
2018-11-12 19:39 ` Alan Tull
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=20180912144327.3130-1-atull@kernel.org \
--to=atull@kernel.org \
--cc=gregkh@linuxfoundation.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.