From: Lee Jones <lee.jones@linaro.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Peter Tyser <ptyser@xes-inc.com>,
key.seong.lim@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] spi-nor: Add support for Intel SPI serial flash controller
Date: Tue, 30 Aug 2016 10:13:30 +0100 [thread overview]
Message-ID: <20160830091330.GH1661@dell> (raw)
In-Reply-To: <20160829071125.GX1812@lahna.fi.intel.com>
On Mon, 29 Aug 2016, Mika Westerberg wrote:
> On Mon, Aug 15, 2016 at 10:10:41AM +0300, Mika Westerberg wrote:
> > Hi,
> >
> > This is third version of the series. Previous versions can be found:
> >
> > v2: http://lists.infradead.org/pipermail/linux-mtd/2016-June/068277.html
> > v1: https://lkml.org/lkml/2016/6/14/269
> >
> > This series adds support for the Intel SPI serial flash controller found on
> > many recent Intel CPUs including Baytrail and Braswell. This driver makes
> > it possible to access the BIOS and other platform data which is stored on
> > the SPI serial flash. It is also possible to upgrade the BIOS using this
> > driver if it has not been protected by special hardware bits.
> >
> > The patch [1/3] includes documentation how to upgrade BIOS on MinnowBoard
> > MAX.
> >
> > Since poking the SPI serial flash can brick the machine, this driver can
> > only be enabled when CONFIG_EXPERT=y and even then it will remain read-only
> > unless instructed othwerwise by module parameter.
> >
> > Lee can you ACK/NACK the MFD parts so that we can merge the whole series
> > through the MTD tree?
Why does it need to go into the MTD tree? What are the *build*
dependencies?
> Hi,
>
> Any comments on this series? It missed v4.8 already so it would be nice
> to get it merged for v4.9.
>
> Thanks.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2016-08-30 9:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 7:10 [PATCH v3 0/3] spi-nor: Add support for Intel SPI serial flash controller Mika Westerberg
2016-08-15 7:10 ` [PATCH v3 1/3] " Mika Westerberg
2016-08-15 7:10 ` [PATCH v3 2/3] mfd: lpc_ich: Add support for SPI serial flash host controller Mika Westerberg
2016-08-30 9:12 ` Lee Jones
2016-08-15 7:10 ` [PATCH v3 3/3] mfd: lpc_ich: Add support for Intel Apollo Lake SoC Mika Westerberg
2016-08-30 9:08 ` Lee Jones
2016-09-29 13:19 ` Kraemer, Matthias (Ferchau; ADITG/SW1)
2016-09-29 13:29 ` Mika Westerberg
2016-09-29 16:56 ` Lee Jones
2016-08-29 7:11 ` [PATCH v3 0/3] spi-nor: Add support for Intel SPI serial flash controller Mika Westerberg
2016-08-30 9:13 ` Lee Jones [this message]
2016-08-30 9:28 ` Mika Westerberg
2016-08-30 10:47 ` Lee Jones
2016-09-12 8:35 ` Mika Westerberg
2016-10-05 9:57 ` Stefan Roese
2016-10-05 10:27 ` Mika Westerberg
2016-10-05 11:11 ` Stefan Roese
2016-10-05 11:18 ` Mika Westerberg
2016-10-05 11:31 ` Stefan Roese
2016-10-05 11:49 ` Mika Westerberg
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=20160830091330.GH1661@dell \
--to=lee.jones@linaro.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=key.seong.lim@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mika.westerberg@linux.intel.com \
--cc=ptyser@xes-inc.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).