From: Tom Rix <trix@redhat.com>
To: Russ Weight <russell.h.weight@intel.com>,
mdf@kernel.org, lee.jones@linaro.org, linux-fpga@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: lgoncalv@redhat.com, yilun.xu@intel.com, hao.wu@intel.com,
matthew.gerlach@intel.com
Subject: Re: [PATCH v7 0/6] Intel MAX10 BMC Secure Update Driver
Date: Tue, 19 Jan 2021 12:49:28 -0800 [thread overview]
Message-ID: <b13a487f-7437-0278-6a9e-f10a5273065b@redhat.com> (raw)
In-Reply-To: <20210105230855.15019-1-russell.h.weight@intel.com>
On 1/5/21 3:08 PM, Russ Weight wrote:
...
> .../testing/sysfs-driver-intel-m10-bmc-secure | 61 ++
> MAINTAINERS | 2 +
> drivers/fpga/Kconfig | 11 +
> drivers/fpga/Makefile | 3 +
> drivers/fpga/intel-m10-bmc-secure.c | 543 ++++++++++++++++++
> include/linux/mfd/intel-m10-bmc.h | 85 +++
I am having trouble pulling this into my testing branch where i am tracking some other changes to intel-m10-bmc.h
https://lore.kernel.org/lkml/20210114231648.199685-1-russell.h.weight@intel.com/
https://lore.kernel.org/lkml/1609999628-12748-3-git-send-email-yilun.xu@intel.com/
so I am wondering if it makes sense to split the intel-m10-bmc.h change out of this patchset and sent as a single patch to mfd subsystem ? The change is a bunch of #defines that don't do anything on their own, but will conflict with other similar additions to the h file.
Tom
> 6 files changed, 705 insertions(+)
> create mode 100644 Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-secure
> create mode 100644 drivers/fpga/intel-m10-bmc-secure.c
>
next prev parent reply other threads:[~2021-01-19 20:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 23:08 [PATCH v7 0/6] Intel MAX10 BMC Secure Update Driver Russ Weight
2021-01-05 23:08 ` [PATCH v7 1/6] mfd: intel-m10-bmc: support for MAX10 BMC Secure Updates Russ Weight
2021-01-05 23:08 ` [PATCH v7 2/6] fpga: m10bmc-sec: create max10 bmc secure update driver Russ Weight
2021-01-05 23:08 ` [PATCH v7 3/6] fpga: m10bmc-sec: expose max10 flash update count Russ Weight
2021-01-05 23:08 ` [PATCH v7 4/6] fpga: m10bmc-sec: expose max10 canceled keys in sysfs Russ Weight
2021-01-05 23:08 ` [PATCH v7 5/6] fpga: m10bmc-sec: add max10 secure update functions Russ Weight
2021-01-05 23:08 ` [PATCH v7 6/6] fpga: m10bmc-sec: add max10 get_hw_errinfo callback func Russ Weight
2021-01-19 20:49 ` Tom Rix [this message]
2021-01-21 20:06 ` [PATCH v7 0/6] Intel MAX10 BMC Secure Update Driver Russ Weight
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=b13a487f-7437-0278-6a9e-f10a5273065b@redhat.com \
--to=trix@redhat.com \
--cc=hao.wu@intel.com \
--cc=lee.jones@linaro.org \
--cc=lgoncalv@redhat.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@intel.com \
--cc=mdf@kernel.org \
--cc=russell.h.weight@intel.com \
--cc=yilun.xu@intel.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;
as well as URLs for NNTP newsgroup(s).