From: Richard Cochran <richardcochran@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Paul Walmsley <paul@pwsan.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Mugunthan V N <mugunthanvnm@ti.com>
Subject: Re: Fwd: [PATCH 2/5] ARM: OMAP3+: hwmod: Add AM33XX HWMOD data for davinci_mdio
Date: Thu, 18 Oct 2012 05:06:54 +0200 [thread overview]
Message-ID: <20121018030654.GE2867@netboy.at.omicron.at> (raw)
In-Reply-To: <20121017235045.GB30550@atomide.com>
On Wed, Oct 17, 2012 at 04:50:46PM -0700, Tony Lindgren wrote:
> * Paul Walmsley <paul@pwsan.com> [121017 16:39]:
> > Hi Richard
> >
> > On Wed, 17 Oct 2012, Richard Cochran wrote:
> >
> > > Would you please take this bugfix for 3.7-rc2? The suggestion to mail
> > > you came from Toni Lindgren. The context where it came from is here:
> > >
> > > http://lists.arm.linux.org.uk/lurker/message/20121015.191630.bdae3c50.en.html
> >
> > This patch appears to add a new feature, correct? I don't think the CPSW
> > could have worked in the past without this data present. So it looks to
> > me like this is 3.8 material, unless Tony would like it to go in sooner?
>
> Yeah unless it fixes something, we should just queue it for v3.8 merge
> window.
So there has been this cpsw driver since v3.4-rc1~177^2~5
df82859 netdev: driver: ethernet: Add TI CPSW driver
and four people signed off on it, so it must have been working at one
point. Since the device tree make-over, the driver is a derelict, and
thus the present patch is fixing a regression.
I just want the already merged driver to work with the vanilla
kernel. Is that too much to ask?
Thanks,
Richard
next prev parent reply other threads:[~2012-10-18 3:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 18:13 Fwd: [PATCH 2/5] ARM: OMAP3+: hwmod: Add AM33XX HWMOD data for davinci_mdio Richard Cochran
2012-10-17 23:38 ` Paul Walmsley
2012-10-17 23:50 ` Tony Lindgren
2012-10-18 3:06 ` Richard Cochran [this message]
2012-10-18 3:46 ` Paul Walmsley
2012-10-18 18:27 ` Richard Cochran
2012-10-18 18:42 ` Paul Walmsley
2012-10-18 18:44 ` Richard Cochran
2012-10-18 19:27 ` Paul Walmsley
2012-10-19 6:08 ` Richard Cochran
2012-10-18 20:48 ` Vaibhav Hiremath
2012-10-19 6:16 ` Richard Cochran
2012-10-19 16:00 ` Tony Lindgren
2012-10-19 16:32 ` Matt Porter
2012-10-26 8:23 ` Hiremath, Vaibhav
2012-10-26 18:06 ` Tony Lindgren
2012-10-29 4:58 ` Hiremath, Vaibhav
2012-10-29 7:50 ` Richard Cochran
2012-10-29 8:27 ` Hiremath, Vaibhav
2012-10-23 10:12 ` Hiremath, Vaibhav
2012-10-24 5:08 ` Richard Cochran
2012-10-26 8:23 ` Hiremath, Vaibhav
2012-10-18 8:30 ` Koen Kooi
2012-10-18 20:48 ` Fwd: " Vaibhav Hiremath
2012-10-18 22:49 ` Paul Walmsley
2012-10-29 5:19 ` Paul Walmsley
2012-10-29 5:22 ` Hiremath, Vaibhav
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=20121018030654.GE2867@netboy.at.omicron.at \
--to=richardcochran@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mugunthanvnm@ti.com \
--cc=paul@pwsan.com \
--cc=tony@atomide.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