From: Lee Jones <lee@kernel.org>
To: Moritz Fischer <mdf@kernel.org>, Wu Hao <hao.wu@intel.com>,
Xu Yilun <yilun.xu@intel.com>, Tom Rix <trix@redhat.com>,
Lee Jones <lee@kernel.org>,
linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org,
Peter Colberg <peter.colberg@intel.com>
Cc: "Russ Weight" <russ.weight@linux.dev>,
"Marco Pagani" <marpagan@redhat.com>,
"Matthew Gerlach" <matthew.gerlach@linux.intel.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Russ Weight" <russell.h.weight@intel.com>
Subject: Re: (subset) [PATCH v2] mfd: intel-m10-bmc: Change staging size to a variable
Date: Fri, 12 Apr 2024 08:34:13 +0100 [thread overview]
Message-ID: <171290725366.2913077.13035135180909218343.b4-ty@kernel.org> (raw)
In-Reply-To: <20240402184925.1065932-1-peter.colberg@intel.com>
On Tue, 02 Apr 2024 14:49:25 -0400, Peter Colberg wrote:
> The secure update driver does a sanity-check of the image size in
> comparison to the size of the staging area in FLASH. Instead of
> hard-wiring M10BMC_STAGING_SIZE, move the staging size to the
> m10bmc_csr_map structure to make the size assignment more flexible.
>
>
Applied, thanks!
[1/1] mfd: intel-m10-bmc: Change staging size to a variable
commit: 770bb9cf4e857ac76f0671309cec689d2a3a4b46
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2024-04-12 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 18:49 [PATCH v2] mfd: intel-m10-bmc: Change staging size to a variable Peter Colberg
2024-04-09 2:38 ` Xu Yilun
2024-04-11 15:49 ` Lee Jones
2024-04-12 2:35 ` Xu Yilun
2024-04-12 7:25 ` Lee Jones
2024-04-12 7:34 ` Lee Jones [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=171290725366.2913077.13035135180909218343.b4-ty@kernel.org \
--to=lee@kernel.org \
--cc=hao.wu@intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marpagan@redhat.com \
--cc=matthew.gerlach@linux.intel.com \
--cc=mdf@kernel.org \
--cc=peter.colberg@intel.com \
--cc=russ.weight@linux.dev \
--cc=russell.h.weight@intel.com \
--cc=trix@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).