From: Artem Bityutskiy <dedekind1@gmail•com>
To: "Gupta, Pekon" <pekon@ti•com>
Cc: Olof Johansson <olof@lixom•net>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Arnd Bergmann <arnd@arndb•de>,
"linux-arm-kernel@lists•infradead.org"
<linux-arm-kernel@lists•infradead.org>,
"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
Mark Jackson <mpfj-list@newflow•co.uk>,
Tony Lindgren <tony@atomide•com>
Subject: Re: linux-next: manual merge of the arm-soc tree with the l2-mtd tree
Date: Tue, 02 Jul 2013 10:33:02 +0300 [thread overview]
Message-ID: <1372750382.9767.19.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73E9E3C27@DBDE04.ent.ti.com>
On Tue, 2013-07-02 at 06:18 +0000, Gupta, Pekon wrote:
> You may drop this patch if you wish so, but its not correct to say that this
> was not reviewed. Following are comments from "Arnd Bergmann"
> http://lists.infradead.org/pipermail/linux-mtd/2013-May/047030.html
> And follow-up reasoning..
> http://lists.infradead.org/pipermail/linux-mtd/2013-May/047032.html
Pekon, let me drop these 3 patches so far anyway. Please, re-submit it
with CC to the devicetree-discuss mailing list. Thanks!
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2013-07-02 7:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 5:29 linux-next: manual merge of the arm-soc tree with the l2-mtd tree Stephen Rothwell
2013-07-02 5:44 ` Gupta, Pekon
2013-07-02 6:00 ` Olof Johansson
2013-07-02 6:18 ` Gupta, Pekon
2013-07-02 7:33 ` Artem Bityutskiy [this message]
2013-07-02 7:30 ` Artem Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2013-07-02 5:33 Stephen Rothwell
2012-11-27 4:37 Stephen Rothwell
2012-11-26 10:16 Stephen Rothwell
2012-09-25 6:50 Stephen Rothwell
2012-09-24 9:39 Stephen Rothwell
2012-09-24 15:50 ` Jason Cooper
2012-05-14 8:47 Stephen Rothwell
2012-03-19 6:47 Stephen Rothwell
2012-03-19 9:00 ` Nicolas Ferre
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=1372750382.9767.19.camel@sauron.fi.intel.com \
--to=dedekind1@gmail$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mpfj-list@newflow$(echo .)co.uk \
--cc=olof@lixom$(echo .)net \
--cc=pekon@ti$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tony@atomide$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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