From: Marek Vasut <marex@denx.de>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: linux-iio@vger.kernel.org, Jonathan Cameron <jic23@kernel.org>,
Juergen Beisert <jbe@pengutronix.de>,
"Lars-Peter Clausen" <lars@metafoo.de>,
Wolfgang Denk <wd@denx.de>
Subject: Re: [PATCH 3/3] IIO: arm: Add LRADC to i.MX28 dts
Date: Tue, 14 Aug 2012 15:23:20 +0200 [thread overview]
Message-ID: <201208141523.20645.marex@denx.de> (raw)
In-Reply-To: <CAAQ0ZWSrqUTkRDyYfWv71R3iUtAwtWUxaUkXYEGUPvoK6RFBig@mail.gmail.com>
Dear Shawn Guo,
> On 14 August 2012 20:33, Marek Vasut <marex@denx.de> wrote:
> > Is there any key to those tags ? Or a document ?
>
> Is there any better document than git log on the file you are committing?
Yes, probably ... especially for newly commited files, I'd expect something to
be there.
> Regards,
> Shawn
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-08-14 13:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-12 15:21 [PATCH 0/3] i.MX28 LRADC driver Marek Vasut
2012-08-12 15:21 ` [PATCH 1/3 RESEND] IIO: Add 4-byte unsigned reads into generic-buffer example Marek Vasut
2012-08-12 15:21 ` [PATCH 2/3 V3] IIO: Add basic MXS LRADC driver Marek Vasut
2012-08-16 19:21 ` Jonathan Cameron
2012-08-16 19:29 ` Marek Vasut
2012-08-12 15:21 ` [PATCH 3/3] IIO: arm: Add LRADC to i.MX28 dts Marek Vasut
2012-08-14 1:56 ` Shawn Guo
2012-08-14 2:10 ` Marek Vasut
2012-08-14 2:23 ` Shawn Guo
2012-08-14 12:33 ` Marek Vasut
2012-08-14 13:15 ` Shawn Guo
2012-08-14 13:23 ` Marek Vasut [this message]
2012-08-17 2:48 ` Shawn Guo
2012-08-17 2:57 ` Marek Vasut
2012-08-17 3:02 ` Shawn Guo
2012-08-19 15:30 ` Marek Vasut
2012-08-20 7:29 ` Jonathan Cameron
2012-08-20 7:52 ` Shawn Guo
2012-08-20 7:57 ` Jonathan Cameron
2012-08-20 13:41 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2012-08-03 15:28 [PATCH 0/3] i.MX28 LRADC driver Marek Vasut
2012-08-03 15:28 ` [PATCH 3/3] IIO: arm: Add LRADC to i.MX28 dts Marek Vasut
2012-08-06 2:39 ` Shawn Guo
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=201208141523.20645.marex@denx.de \
--to=marex@denx.de \
--cc=jbe@pengutronix.de \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=wd@denx.de \
/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).