From: Jonathan Cameron <jic23@cam.ac.uk>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: linux-iio@vger.kernel.org, lars@metafoo.de,
Michael.Hennerich@analog.com,
device-drivers-devel@blackfin.uclinux.org
Subject: Re: [PATCH] staging:iio: header reorganization
Date: Fri, 21 Oct 2011 10:28:18 +0100 [thread overview]
Message-ID: <4EA13B32.1020209@cam.ac.uk> (raw)
In-Reply-To: <4EA13782.9050405@cam.ac.uk>
On 10/21/11 10:12, Jonathan Cameron wrote:
> Oops - forgot to say what this sits on.
> https://github.com/jic23/linux-iio master branch.
>
> That means it may well clash with a lot of the patches that have
> gone to Greg over last day or so.
>
I've rebased this and demux branches so all should now be fine.
For now I've also stuck this patch on top of master
(and hence at bottom of demux)
next prev parent reply other threads:[~2011-10-21 9:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 7:21 Userspace event handling and header files Lars-Peter Clausen
2011-10-21 8:02 ` Hennerich, Michael
2011-10-21 8:58 ` Jonathan Cameron
2011-10-21 9:09 ` [PATCH] staging:iio: header reorganization Jonathan Cameron
2011-10-21 9:12 ` Jonathan Cameron
2011-10-21 9:28 ` Jonathan Cameron [this message]
2011-10-21 10:42 ` Lars-Peter Clausen
2011-10-21 10:59 ` Jonathan Cameron
2011-10-21 11:15 ` Jonathan Cameron
2011-10-21 10:59 ` [PATCH 1/2] staging:iio: Add missing ioctl.h include to events.h Lars-Peter Clausen
2011-10-21 10:59 ` [PATCH 2/2] staging:iio: Use userspace types for iio_event_data Lars-Peter Clausen
2011-10-21 11:39 ` Jonathan Cameron
2011-10-21 11:00 ` [PATCH 1/2] staging:iio: Add missing ioctl.h include to events.h Jonathan Cameron
2011-10-21 9:42 ` Userspace event handling and header files Lars-Peter Clausen
2011-10-21 9:44 ` Jonathan Cameron
2011-10-21 9:51 ` 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=4EA13B32.1020209@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=Michael.Hennerich@analog.com \
--cc=device-drivers-devel@blackfin.uclinux.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;
as well as URLs for NNTP newsgroup(s).