From: Richard Cochran <richardcochran@gmail.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Tony Lindgren <tony@atomide.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 20:27:32 +0200 [thread overview]
Message-ID: <20121018182732.GC2350@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:
>
> It doesn't necessarily mean that the driver is usable in that kernel
> release.
Well, it should. We have staging for half-baked stuff.
> Either way, the patch is likely to make it into the mainline kernel.
> It's just that it will probably take a few weeks longer than you might
> like.
I don't mind waiting for a driver that is held off because of missing
background support.
I *do* mind if y'all go merging all kinds of code that has never been
tested. Those who submit and their reviewers should ensure that the
code is actually working. Before buying hardware or starting projects,
I often check what is in mainline. I expect that mainline has been at
least minimally tested.
Maybe that is just me, or maybe people working on the ARM tree have
different expectations.
Thanks,
Richard
next prev parent reply other threads:[~2012-10-18 18:27 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 [this message]
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=20121018182732.GC2350@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