From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "AnilKumar, Chimata" <anilkumar@ti.com>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
"greg@kroah.com" <greg@kroah.com>,
"eric.piel@tremplin-utc.net" <eric.piel@tremplin-utc.net>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Nori, Sekhar" <nsekhar@ti.com>
Subject: Re: [PATCH] lis3lv02d: Add STMicroelectronics lis33ldlh digital
Date: Tue, 17 Jan 2012 10:54:42 +0000 [thread overview]
Message-ID: <20120117105441.GC2944@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13177CDA4@DBDE01.ent.ti.com>
On Tue, Jan 17, 2012 at 07:32:47AM +0000, AnilKumar, Chimata wrote:
> Recalling the patch, provide the comments if there are any if not please include
> this patch to v3.3 kernel.
There's no way this is going to make it into the 3.3 kernel at this
point, we're almost at the end of the merge window.
next prev parent reply other threads:[~2012-01-17 10:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1324617892-14576-1-git-send-email-anilkumar@ti.com>
2011-12-23 11:18 ` [PATCH] lis3lv02d: Add STMicroelectronics lis33ldlh digital Mark Brown
2011-12-28 9:14 ` AnilKumar, Chimata
2012-01-17 7:32 ` AnilKumar, Chimata
2012-01-17 10:54 ` Mark Brown [this message]
2012-01-17 16:03 ` greg
2012-01-18 5:48 ` AnilKumar, Chimata
2012-01-17 23:47 ` Andrew Morton
2012-01-18 7:51 ` AnilKumar, Chimata
2012-01-18 14:03 ` Arnd Bergmann
2012-01-18 14:43 ` Jean Delvare
2012-01-18 14:49 ` Arnd Bergmann
2012-01-18 15:00 ` Jean Delvare
2012-01-18 16:47 ` Jonathan Cameron
2012-01-18 17:11 ` Arnd Bergmann
2012-01-19 5:30 ` AnilKumar, Chimata
2012-01-19 17:10 ` Arnd Bergmann
2012-01-19 17:29 ` Mark Brown
2012-07-25 8:57 ` AnilKumar, Chimata
2012-01-18 21:36 ` Andi
2012-01-19 14:26 ` Arnd Bergmann
2012-01-19 17:15 ` 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=20120117105441.GC2944@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=akpm@linux-foundation.org \
--cc=anilkumar@ti.com \
--cc=arnd@arndb.de \
--cc=eric.piel@tremplin-utc.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.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).