From: Dan Carpenter <dan.carpenter@oracle.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jonathan Cameron <jic23@kernel.org>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 3/4] staging:iio: Add missing event code extract macros
Date: Sat, 11 Feb 2012 21:08:57 +0300 [thread overview]
Message-ID: <20120211180857.GJ4141@mwanda> (raw)
In-Reply-To: <4F363F37.4010508@metafoo.de>
[-- Attachment #1: Type: text/plain, Size: 347 bytes --]
On Sat, Feb 11, 2012 at 11:13:11AM +0100, Lars-Peter Clausen wrote:
> >>
> >> Breaks the build.
> >>
> >
> > Oops. This isn't a rename. It doesn't break the build. Why are
> > we adding macros which nobody uses?
>
> Patch 4 in this series adds a user.
Ah. That's fine then. My bad. Sorry for that.
regards,
dan carpenter
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-11 18:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 18:14 [PATCH 1/4] staging:iio:events: Remove obsolete documentation Lars-Peter Clausen
2012-02-10 18:14 ` [PATCH 2/4] staging:iio: Rename IIO_EVENT_CODE_EXTRACT_NUM to IIO_EVENT_CODE_EXTRACT_CHAN Lars-Peter Clausen
2012-02-10 18:30 ` Greg Kroah-Hartman
2012-02-10 20:44 ` Dan Carpenter
2012-02-10 18:15 ` [PATCH 3/4] staging:iio: Add missing event code extract macros Lars-Peter Clausen
2012-02-10 20:45 ` Dan Carpenter
2012-02-10 20:47 ` Dan Carpenter
2012-02-11 10:13 ` Lars-Peter Clausen
2012-02-11 18:08 ` Dan Carpenter [this message]
2012-02-10 18:15 ` [PATCH 4/4] staging:iio: Add event monitor example application Lars-Peter Clausen
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=20120211180857.GJ4141@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox