From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: linux-mtd@lists.infradead.org
Cc: Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
Marek Vasut <marek.vasut@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Richard Weinberger <richard@nod.at>,
Anthony Wong <anthony.wong@canonical.com>,
Bin Meng <bmeng.cn@gmail.com>
Subject: Re: [PATCH v2 1/2] spi-nor: intel-spi: Fix atomic sequence handling
Date: Tue, 3 Apr 2018 16:48:36 +0300 [thread overview]
Message-ID: <20180403134836.GD2173@lahna.fi.intel.com> (raw)
In-Reply-To: <20180227165142.GL2424@lahna.fi.intel.com>
On Tue, Feb 27, 2018 at 06:51:42PM +0200, Mika Westerberg wrote:
> On Mon, Feb 05, 2018 at 02:32:59PM +0300, Mika Westerberg wrote:
> > Changes from v1:
> >
> > - Added atomic_preopcode field and only when it is set, enable atomic
> > sequence.
> > - Return -EINVAL if the requested WREN operation cannot be found from
> > PREOP register instead of silently pretending it is supported.
> > - Updated patch subject to match more closely what is being fixed.
>
> Any comments on these two? I did the changes Cyrille asked me to do.
Ping. If no comments, could someone pick these up please.
next prev parent reply other threads:[~2018-04-03 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 11:32 [PATCH v2 1/2] spi-nor: intel-spi: Fix atomic sequence handling Mika Westerberg
2018-02-05 11:33 ` [PATCH v2 2/2] spi-nor: intel-spi: Explicitly mark the driver as dangerous in Kconfig Mika Westerberg
2018-02-27 16:51 ` [PATCH v2 1/2] spi-nor: intel-spi: Fix atomic sequence handling Mika Westerberg
2018-04-03 13:48 ` Mika Westerberg [this message]
2018-04-04 8:21 ` Marek Vasut
2018-04-04 19:22 ` Boris Brezillon
2018-05-18 5:20 ` Mika Westerberg
2018-05-18 6:53 ` Boris Brezillon
2018-05-18 20:01 ` Boris Brezillon
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=20180403134836.GD2173@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=anthony.wong@canonical.com \
--cc=bmeng.cn@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
/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).