From: Jonathan Cameron <jic23@cam.ac.uk>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: "Hennerich, Michael" <Michael.Hennerich@analog.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
Drivers <Drivers@analog.com>,
"device-drivers-devel@blackfin.uclinux.org"
<device-drivers-devel@blackfin.uclinux.org>
Subject: Re: IIO-onwards
Date: Wed, 18 May 2011 11:03:53 +0100 [thread overview]
Message-ID: <4DD39989.7000602@cam.ac.uk> (raw)
In-Reply-To: <4DD385B2.9070809@cam.ac.uk>
On 05/18/11 09:39, Jonathan Cameron wrote:
> On 05/18/11 08:58, Hennerich, Michael wrote:
>> Hi Jonathan,
>>
>> What are your plans for submitting IIO-onwards?
> It would have gone about a weak ago, but Thomas Gleixner wants some slight
> tweaks to the irq core exports patch that about 50% of
> our tree is dependent on. Getting this sorted is being slowed down by (I think)
> the fact Thomas is travelling at the moment and seems to only have
> intermittent email access. The outstanding issue is that irq_to_descs
> should not be exported, but rather handle_generic_irq shouldn't
> be inline. I'm waiting on a reply for where it should go as it
> doesn't obviously fit in any of the files under kernel/irq/.
>
> Greg knows what the situation is, so fingers crossed that we can
> get it cleared up in time to catch the merge window.
>
> I think I'll just plump for a vaguely reasonable location for the code
> and hope I guessed right as that will speed things up a touch and can't
> do any harm!
I've just pushed out exactly what I aim to send to Greg the moment
Thomas acks the irq element (or says he is pulling it via his tree).
Other than updates to that irq patch, I've cleaned up some commit
messages so it all looks nice and tidy ;)
prev parent reply other threads:[~2011-05-18 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 7:58 IIO-onwards Hennerich, Michael
2011-05-18 8:39 ` IIO-onwards Jonathan Cameron
2011-05-18 10:03 ` Jonathan Cameron [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=4DD39989.7000602@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=Drivers@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=device-drivers-devel@blackfin.uclinux.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.