From: Alessandro Rubini <rubini@gnudd.com>
To: linux-kernel@vger.kernel.org
Cc: riehecky@fnal.gov, federico.vaga@cern.ch, gregkh@linuxfoundation.org
Subject: [PATCH V3 0/5] Update kernel to latest FMC bus release
Date: Tue, 18 Jul 2017 08:32:32 +0200 [thread overview]
Message-ID: <20170718063232.GA23411@mail.gnudd.com> (raw)
Version 3:
fixed From: line to set Federico Vaga as author,
added my Acked-by: line.
removed drivers_other@kernel-bugs as recipient (NXDOMAIN)
Version 2 (posted by Pat Riehecky):
added Tested-by: and (incorrect) From:
Comments by Pat, original poster, for version 1:
The following patches sync up the mainline kernel's FMC bus with the
upstream release tagged v2017-06.
Commits (written by Federico Vaga) have been squashed into logical units.
These patches address kernel bug 195653.
These specific changes have been live within the FMC repo since 2015
and in active use by FMC projects since then.
The patches include 1 bugfix and 4 enhancements:
Bugfix:
0001-fmc-remove-unused-variable.patch - remove an unused int
Enhancements:
0002-fmc-hide-fmc-operations-behind-helpers.patch - user helper
functions to hide internal semantics
0003-fmc-The-only-way-to-dump-the-SDB-is-from-debugfs.patch - use
debugfs to dump the device
0004-fmc-change-registration-prototype.patch - add a second
prototype for device registration
0005-fmc-carrier-can-program-FPGA-on-registration.patch - permit
programming the FPGA on registration
Upstream git repo:
http://www.ohwr.org/projects/fmc-bus/repository/show?rev=fmc-bus-v2017-06
FMC maintainer: Alessandro Rubini <rubini@gnudd.com>
Initial approver of FMC: Greg KH <gregkh@linuxfoundation.org>
Federico Vaga (5):
drivers/fmc: remove unused variable
drivers/fmc: hide fmc operations behind helpers
drivers/fmc: The only way to dump the SDB is from debugfs
drivers/fmc: change registration prototype
drivers/fmc: carrier can program FPGA on registration
drivers/fmc/Makefile | 1 +
drivers/fmc/fmc-chardev.c | 3 +-
drivers/fmc/fmc-core.c | 95 ++++++++++++++++++++--
drivers/fmc/fmc-debug.c | 173 +++++++++++++++++++++++++++++++++++++++++
drivers/fmc/fmc-dump.c | 41 ----------
drivers/fmc/fmc-match.c | 2 +-
drivers/fmc/fmc-private.h | 9 +++
drivers/fmc/fmc-sdb.c | 119 ++++++----------------------
drivers/fmc/fmc-trivial.c | 20 ++---
drivers/fmc/fmc-write-eeprom.c | 8 +-
drivers/fmc/fru-parse.c | 3 +-
include/linux/fmc.h | 39 +++++++++-
12 files changed, 349 insertions(+), 164 deletions(-)
create mode 100644 drivers/fmc/fmc-debug.c
create mode 100644 drivers/fmc/fmc-private.h
--
2.1.4
reply other threads:[~2017-07-18 6:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170718063232.GA23411@mail.gnudd.com \
--to=rubini@gnudd.com \
--cc=federico.vaga@cern.ch \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riehecky@fnal.gov \
/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
Powered by JetHome