From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org
Cc: Jonathan Cameron <jic23@kernel.org>
Subject: [PATCH 0/3] IIO break info_mask into a pair of masks - Additional drivers 2 (missed ones)
Date: Mon, 4 Mar 2013 21:16:17 +0000 [thread overview]
Message-ID: <1362431780-27682-1-git-send-email-jic23@kernel.org> (raw)
As Lars-Peter noticed, I missed these 3 drivers for some reason in the earlier
two series of patches. Oops. Have now deployed grep more carefully/thoroughly.
These will shortly appear at an appropriate spot in the info_mask_split branch
of iio.git.
This short series applies the equivalent changes to three drivers missed
from the series in
[PATCH 00/67 V2] IIO break info_mask into a pair of masks
was under way.
If there are no issues, I'll slot these in just before patch 67 of that
series.
As a quick summary for anyone just looking at these, I am proposing to
split info_mask into info_mask_separate and info_mask_shared_by_type
so as to simplify the handling, shorten the code and make more space
for new elements. With the benefit of hindsight info_mask should
have been done like this in the first place.
Jonathan
Jonathan Cameron (3):
staging:iio:adc:spear move to info_mask_(shared_by_type/separate)
staging:iio:adc:mxs move to info_mask_(shared_by_type/separate)
staging:iio:adc:lpc32xx move to info_mask_(shared_by_type/separate)
drivers/staging/iio/adc/lpc32xx_adc.c | 2 +-
drivers/staging/iio/adc/mxs-lradc.c | 2 +-
drivers/staging/iio/adc/spear_adc.c | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
--
1.8.1.4
next reply other threads:[~2013-03-04 21:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 21:16 Jonathan Cameron [this message]
2013-03-04 21:16 ` [PATCH 1/3] staging:iio:adc:spear move to info_mask_(shared_by_type/separate) Jonathan Cameron
2013-03-05 7:28 ` Stefan Roese
2013-03-04 21:16 ` [PATCH 2/3] staging:iio:adc:mxs " Jonathan Cameron
2013-03-04 21:23 ` Marek Vasut
2013-03-04 21:16 ` [PATCH 3/3] staging:iio:adc:lpc32xx " 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=1362431780-27682-1-git-send-email-jic23@kernel.org \
--to=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
/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.