From: richardcochran@gmail.com (Richard Cochran)
To: linux-arm-kernel@lists.infradead.org
Subject: Fwd: [PATCH 2/5] ARM: OMAP3+: hwmod: Add AM33XX HWMOD data for davinci_mdio
Date: Thu, 18 Oct 2012 20:44:43 +0200 [thread overview]
Message-ID: <20121018184443.GD2350@netboy.at.omicron.at> (raw)
In-Reply-To: <alpine.DEB.2.00.1210180313360.6893@utopia.booyaka.com>
On Thu, Oct 18, 2012 at 03:46:15AM +0000, Paul Walmsley wrote:
>
> Probably the driver was submitted before any SoC integration support was
> available. Grepping for 'cpsw' under arch/ turns up only AM33xx. AM335x
> didn't have device enumeration support in the mainline kernel until 3.7,
> via commit a2cfc509bc4eeef9f5c4607b1203f17f22ea2a36 ("ARM: OMAP3+: hwmod:
> Add AM33XX HWMOD data"). So I don't see how it could have worked with
> mainline.
...
> But it seems that the CPSW has never worked in the mainline kernel. So
> this particular patch is not fixing a regression. Therefore we shouldn't
> send it upstream during the -rc time period. Instead we'll schedule it to
> be sent a few weeks later, during the 3.8 merge window.
Let's think about this some more:
The driver's commit is from March and is included in v3.4-rc1.
You say it will be working in 3.8, after 3.7 comes out, in about
December.
So how long does it take between merging code and actually getting it
working?
Sorry to harp on this so much, but I try out my patches with the tip
of the appropriate tree before sending them, or when I cannot, at
least I put into the log "compile tested only" or something like that.
Thanks,
Richard
next prev parent reply other threads:[~2012-10-18 18:44 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
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 [this message]
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=20121018184443.GD2350@netboy.at.omicron.at \
--to=richardcochran@gmail.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).