From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: carolyn.j.smith@exgate.tek.com,
Stephen Rothwell <sfr@canb.auug.org.au>,
Artem Bityutskiy <dedekind1@gmail.com>,
dedekind@infradead.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Jim Cromie <jim.cromie@gmail.com>,
Sachin P Sant <sachinp@linux.vnet.ibm.com>,
linux-next <linux-next@vger.kernel.org>,
linux-mtd@lists.infradead.org,
Linuxppc-dev <Linuxppc-dev@ozlabs.org>,
Scott Wood <scottwood@freescale.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: [PATCH Resend2] Remove 'SBC8240 Wind River' Device Driver Code
Date: Fri, 10 Jul 2009 14:28:44 +0530 [thread overview]
Message-ID: <1247216324.6630.10.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <1247216007.29541.2.camel@macbook.infradead.org>
On Fri, 2009-07-10 at 09:53 +0100, David Woodhouse wrote:
> On Fri, 2009-07-10 at 14:17 +0530, Subrata Modak wrote:
> > Is it possible to get this patch through and before 2.6.31 stable is
> > released ?
>
Hi David,
> Hm, I was ignoring this until I was sure all the last-minute fixes for
> 2.6.31 were out of the way; I was planning to submit it for 2.6.32.
>
> Do we really need to submit it for 2.6.31? It's not a regression, is it?
> It's been like this for _ages_.
True. But it gives annoying build fails on randconfig next trees. And
we(Sachin & myself) has been reporting it from March/April. If you feel
there is still room to be pushed to 2.6.31, then please do it. Else,
2.6.32 will be fine. Thanks for your support.
Regards--
Subrata
>
prev parent reply other threads:[~2009-07-10 8:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 13:52 [PATCH Resend] Remove 'SBC8240 Wind River' Device Driver Code Subrata Modak
2009-07-06 2:17 ` [PATCH Resend2] " Subrata Modak
2009-07-10 5:59 ` Artem Bityutskiy
2009-07-10 6:15 ` Subrata Modak
2009-07-10 6:18 ` Artem Bityutskiy
2009-07-10 7:12 ` Subrata Modak
2009-07-10 7:14 ` Artem Bityutskiy
2009-07-10 8:47 ` Subrata Modak
2009-07-10 8:53 ` David Woodhouse
2009-07-10 8:58 ` Subrata Modak [this message]
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=1247216324.6630.10.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=carolyn.j.smith@exgate.tek.com \
--cc=dedekind1@gmail.com \
--cc=dedekind@infradead.org \
--cc=dwmw2@infradead.org \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=sachinp@linux.vnet.ibm.com \
--cc=scottwood@freescale.com \
--cc=sfr@canb.auug.org.au \
/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).