From: Lee Jones <lee@kernel.org>
To: Xu Yilun <yilun.xu@linux.intel.com>
Cc: "Peter Colberg" <peter.colberg@intel.com>,
"Moritz Fischer" <mdf@kernel.org>, "Wu Hao" <hao.wu@intel.com>,
"Xu Yilun" <yilun.xu@intel.com>, "Tom Rix" <trix@redhat.com>,
linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org,
"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: [PATCH v2] mfd: intel-m10-bmc: Change staging size to a variable
Date: Fri, 12 Apr 2024 08:25:31 +0100 [thread overview]
Message-ID: <20240412072531.GN2399047@google.com> (raw)
In-Reply-To: <ZhieBC124oq/Fcqa@yilunxu-OptiPlex-7050>
On Fri, 12 Apr 2024, Xu Yilun wrote:
> On Thu, Apr 11, 2024 at 04:49:56PM +0100, Lee Jones wrote:
> > On Tue, 02 Apr 2024, Peter Colberg wrote:
> >
> > > From: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> > >
> > > 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.
> > >
> > > Co-developed-by: Russ Weight <russell.h.weight@intel.com>
> > > Signed-off-by: Russ Weight <russell.h.weight@intel.com>
> > > Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> > > Signed-off-by: Peter Colberg <peter.colberg@intel.com>
> >
> > Xu Yilun, Peter,
> >
> > Do you require a pull-request from an immutable branch for this?
>
> No need. The patchset could all be applied to mfd branch.
Prefect, thank you.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2024-04-12 7:25 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 [this message]
2024-04-12 7:34 ` (subset) " Lee Jones
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=20240412072531.GN2399047@google.com \
--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 \
--cc=yilun.xu@linux.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