All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <sboyce@blueyonder.co.uk>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Is the OMAP patch process badly flawed?
Date: Wed, 18 Nov 2009 03:20:45 +0000	[thread overview]
Message-ID: <4B03680D.6010808@blueyonder.co.uk> (raw)
In-Reply-To: <94a0d4530911171407r6e1f378al9acb3b985196158b@mail.gmail.com>

On 17/11/09 22:07, Felipe Contreras wrote:
> On Tue, Nov 17, 2009 at 3:30 PM, Sid Boyce <sboyce@blueyonder.co.uk> wrote:
>> I'm curious - I download, build and test kernels on x86 and x86_64
>> platforms, -rc, -rc-git and -git all build and run.
> 
> [...]
> 
>> I would expect patches sent upstream would result in all the basics for
>> long established platforms to be fully covered. Appreciating that
>> development is quite fast paced with mods and supporting new platforms.
>> Could someone please enlighten me?
> 
> Previously all the linux-omap work had to be queued through the
> linux-arm tree, that made it a bit difficult to push things to the
> mainline, but now Tony is sending the pull requests directly to Linus,
> so maybe kernels post 2.6.32 will be much better.
> 
I certainly hope so, it would be nice for the mainline to catch up so we
can work from the one code base.

> However, the only way to make sure that there's good OMAP support in
> Linux is for the community to actively test the mainline and make sure
> the patches are properly pushed and queued, and regressions are found
> quickly, not only on the linux-omap tree, but linux-usb, fbdev, etc.
> Unfortunately we haven't done such a great job on that, perhaps
> because many people use old "stable" aka "frozen" kernels, but things
> are improving.
> 
> Cheers.
> 

Thanks, I use vanilla kernels exclusively on my x86 and x86_64 boxes,
looking for anything that's regressed or broken with API changes.
Regards
Sid.
-- 
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks


      reply	other threads:[~2009-11-18  3:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16  5:04 linux-next: manual merge of the omap_dss2 tree with the omap tree Stephen Rothwell
2009-11-16  5:04 ` Stephen Rothwell
2009-11-16 10:06 ` Tomi Valkeinen
2009-11-16 18:34   ` Tony Lindgren
2009-11-17 10:00     ` Tomi Valkeinen
2009-11-17 23:49       ` Stephen Rothwell
2009-11-17  3:08 ` Sid Boyce
2009-11-17 13:30   ` Is the OMAP patch process badly flawed? Sid Boyce
2009-11-17 13:34     ` Gadiyar, Anand
2009-11-17 14:00       ` Sid Boyce
2009-11-17 14:51         ` Gadiyar, Anand
2009-11-17 21:44           ` Sid Boyce
2009-11-17 22:07     ` Felipe Contreras
2009-11-18  3:20       ` Sid Boyce [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=4B03680D.6010808@blueyonder.co.uk \
    --to=sboyce@blueyonder.co.uk \
    --cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.