From: Jonathan Cameron <jic23@cam.ac.uk>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Srinidhi KASAGAR <srinidhi.kasagar@stericsson.com>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH] staging: iio: add lsm303dlh magnetometer driver
Date: Mon, 09 Apr 2012 19:04:51 +0100 [thread overview]
Message-ID: <4F8324C3.9080407@cam.ac.uk> (raw)
In-Reply-To: <CACRpkdYi990U+9LEZo18C0ueqPVqDf6_JHA5Efy5aH3YoQjQAw@mail.gmail.com>
On 04/09/2012 06:50 PM, Linus Walleij wrote:
> On Mon, Apr 9, 2012 at 1:34 PM, Srinidhi KASAGAR
> <srinidhi.kasagar@stericsson.com> wrote:
>
>> Add support for lsm303dlh magnetometer device.
>>
>> Signed-off-by: srinidhi kasagar <srinidhi.kasagar@stericsson.com>
>> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>
> Jonathan are you funneling patches to IIO or shall we send them directly
> to Greg?
>
> Thanks,
> Linus Walleij
Technically I only ever took patches through my tree when there were big
changes afoot (to avoid mass breakages as the sets hit Greg). There's
no formal requirement but what usually happens is that changes go to
linux-iio and someone (not necessarily me (thanks as always to the
others who help with this!) reviews them. If I want to take a look (or
anyone else does) and I don't have time in the first few days, I tend to
drop the author email asking them to hold it till I've commented. I'll
also often suggest sending on to Greg anything I have acked (as long as
there are no other outstanding comments from others to be addressed), or
suggest who else I want some feedback from before
it goes to Greg so he has the most information possible when chosing
whether to merge or not.
So I operate a sort of informal maintainership. Note that any fixes
for blindingly obvious stuff such as build fixes tend to go to Greg
at the same point they go to linux-iio.
Jonathan
next prev parent reply other threads:[~2012-04-09 18:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 11:34 [PATCH] staging: iio: add lsm303dlh magnetometer driver Srinidhi KASAGAR
2012-04-09 17:50 ` Linus Walleij
2012-04-09 18:04 ` Jonathan Cameron [this message]
2012-04-09 20:51 ` Jonathan Cameron
2012-04-13 11:09 ` Srinidhi Kasagar
2012-04-13 13:55 ` Jonathan Cameron
2012-04-17 6:01 ` Srinidhi Kasagar
2012-04-17 6:14 ` Jonathan Cameron
2012-04-17 6:29 ` Shubhrajyoti Datta
2012-04-17 6:47 ` Srinidhi Kasagar
2012-04-17 7:22 ` 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=4F8324C3.9080407@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=srinidhi.kasagar@stericsson.com \
/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).