From: Lars-Peter Clausen <lars@metafoo.de>
To: Peter Rosin <peda@axentia.se>, linux-kernel@vger.kernel.org
Cc: Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Alison Schofield <amsfield22@gmail.com>,
Gregor Boirie <gregor.boirie@parrot.com>,
Sanchayan Maity <maitysanchayan@gmail.com>,
Ken Lin <ken.lin@advantech.com>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 0/2] iio: pressure: do not rely on structure field ordering
Date: Wed, 1 Feb 2017 09:52:45 +0100 [thread overview]
Message-ID: <0bee87fa-ee69-c39a-61bb-37960d287889@metafoo.de> (raw)
In-Reply-To: <1485936567-3367-1-git-send-email-peda@axentia.se>
On 02/01/2017 09:09 AM, Peter Rosin wrote:
> Hi!
>
> These two patches are needed to fix some fallout from adding the
> available attribute.
I put together a quick cocci script to check for other occurrences of this
issue and these were the only two drivers affected by the issue.
prev parent reply other threads:[~2017-02-01 8:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 8:09 [PATCH 0/2] iio: pressure: do not rely on structure field ordering Peter Rosin
2017-02-01 8:09 ` [PATCH 1/2] iio: pressure: mpl3115: " Peter Rosin
2017-02-01 9:10 ` Peter Meerwald-Stadler
2017-02-01 9:13 ` Peter Rosin
2017-02-01 9:31 ` Peter Meerwald-Stadler
2017-02-01 9:43 ` Peter Rosin
2017-02-01 9:57 ` Peter Meerwald-Stadler
2017-02-01 10:18 ` Peter Rosin
[not found] ` <WM!e12d26e0b57c992627516bbebee1f0ac620aa97ce815547b240a5ff4318cef8602c115af08639804344b7a648bbe4b31!@dg.advantech.com>
[not found] ` <03B5A3CA1724CE4EAC32B27E39292A677FC7512F94@AUSMAIL1.AUS.ADVANTECH.CORP>
2017-02-01 18:24 ` Ken.Lin
2017-02-01 11:21 ` Jonathan Cameron
2017-02-01 8:09 ` [PATCH 2/2] iio: pressure: mpl115: " Peter Rosin
2017-02-01 8:52 ` Lars-Peter Clausen [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=0bee87fa-ee69-c39a-61bb-37960d287889@metafoo.de \
--to=lars@metafoo.de \
--cc=amsfield22@gmail.com \
--cc=gregor.boirie@parrot.com \
--cc=jic23@kernel.org \
--cc=ken.lin@advantech.com \
--cc=knaack.h@gmx.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maitysanchayan@gmail.com \
--cc=peda@axentia.se \
--cc=pmeerw@pmeerw.net \
/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).