From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add entry for Analog Devices IIO drivers
Date: Tue, 19 Aug 2014 21:18:57 +0200 [thread overview]
Message-ID: <53F3A321.5090905@metafoo.de> (raw)
In-Reply-To: <53F3A214.6080003@kernel.org>
On 08/19/2014 09:14 PM, Jonathan Cameron wrote:
>> +ANALOG DEVICES INC IIO DRIVERS
>> +M: Lars-Peter Clausen <lars@metafoo.de>
>> +M: Michael Hennerich <Michael.Hennerich@analog.com>
Ah, damm, just saw this, somehow I messed up the indention here... Can you
fix this up before pushing the tree?
Thanks,
- Lars
next prev parent reply other threads:[~2014-08-19 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 8:08 [PATCH] MAINTAINERS: Add entry for Analog Devices IIO drivers Lars-Peter Clausen
2014-08-19 19:14 ` Jonathan Cameron
2014-08-19 19:18 ` Lars-Peter Clausen [this message]
2014-08-19 19:26 ` Jonathan Cameron
2014-08-19 19:18 ` Jonathan Cameron
2014-08-19 19:21 ` 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=53F3A321.5090905@metafoo.de \
--to=lars@metafoo.de \
--cc=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 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).