All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Rosin <peda@axentia.se>
To: <linux-kernel@vger.kernel.org>
Cc: Peter Rosin <peda@axentia.se>,
	Jonathan Cameron <jic23@kernel.org>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Sanchayan Maity <maitysanchayan@gmail.com>,
	Gregor Boirie <gregor.boirie@parrot.com>,
	Alison Schofield <amsfield22@gmail.com>,
	Ken Lin <ken.lin@advantech.com>, <linux-iio@vger.kernel.org>
Subject: [PATCH v2 0/2] iio: pressure: do not rely on structure field ordering
Date: Wed, 1 Feb 2017 21:40:55 +0100	[thread overview]
Message-ID: <1485981657-14586-1-git-send-email-peda@axentia.se> (raw)

Hi!

v1 -> v2 changes:

- improved commit messages
- added tested-by tag

These two patches are needed to fix some fallout from adding the
available attribute.

Jonathan, it was a bitch to rebase with that line starting with a #. Please
make sure that it stays where it should be in case you decide to fixup
anything...

Cheers,
peda

Peter Rosin (2):
  iio: pressure: mpl3115: do not rely on structure field ordering
  iio: pressure: mpl115: do not rely on structure field ordering

 drivers/iio/pressure/mpl115.c  | 1 +
 drivers/iio/pressure/mpl3115.c | 4 ++--
 2 files changed, 3 insertions(+), 2 deletions(-)

-- 
2.1.4

             reply	other threads:[~2017-02-01 20:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 20:40 Peter Rosin [this message]
2017-02-01 20:40 ` [PATCH v2 1/2] iio: pressure: mpl3115: do not rely on structure field ordering Peter Rosin
2017-02-05  9:37   ` Jonathan Cameron
2017-02-10 22:35     ` [PULL] IIO fixes for 4.10 set 3 - a couple of regression fixes Peter Rosin
2017-02-11  7:17       ` Greg Kroah-Hartman
2017-02-11  9:16         ` Jonathan Cameron
2017-02-14 14:29           ` Peter Rosin
2017-02-01 20:40 ` [PATCH v2 2/2] iio: pressure: mpl115: do not rely on structure field ordering Peter Rosin
2017-02-05  9:38   ` Jonathan Cameron

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=1485981657-14586-1-git-send-email-peda@axentia.se \
    --to=peda@axentia.se \
    --cc=amsfield22@gmail.com \
    --cc=gregor.boirie@parrot.com \
    --cc=jic23@kernel.org \
    --cc=ken.lin@advantech.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maitysanchayan@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.