From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3] ASoC: Davinci: machine: Add device tree binding
Date: Fri, 31 Aug 2012 10:27:30 -0700 [thread overview]
Message-ID: <20120831172729.GE25575@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1BAFE6F6C881BF42822005164F1491C33EA70165@DBDE01.ent.ti.com>
On Fri, Aug 31, 2012 at 08:55:39AM +0000, Hebbar, Gururaja wrote:
>
> Gentle Ping. Any updates about this version or can it be pulled into the tree.
>
> On Thu, Aug 30, 2012 at 09:29:55, Hebbar, Gururaja wrote:
Please don't do this:
- Never top post.
- If the patch genuinely has been forgotten you need to resend it.
- You've allowed less than 24 hours for a reply, this is unreasonable.
Unless there's a critical bug fix you should only be worrying after a
few weeks or so.
next prev parent reply other threads:[~2012-08-31 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 10:13 [PATCH V3] ASoC: Davinci: machine: Add device tree binding Hebbar, Gururaja
2012-08-30 4:01 ` Hebbar, Gururaja
2012-08-31 8:55 ` Hebbar, Gururaja
2012-08-31 17:27 ` Mark Brown [this message]
2012-09-03 5:21 ` Hebbar, Gururaja
2012-09-12 7:55 ` Hebbar, Gururaja
2012-09-12 7:57 ` Mark Brown
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=20120831172729.GE25575@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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).