All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: jassi brar <jassisinghbrar@gmail.com>
Cc: linux-samsung-soc@vger.kernel.org, Jassi Brar <jassi.brar@samsung.com>
Subject: Re: Revised patches for PCM Controller driver
Date: Wed, 4 Nov 2009 14:03:11 +0000	[thread overview]
Message-ID: <20091104140310.GB27652@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1b68c6790911040414jced4bf1i8852a9ce84c3ddf5@mail.gmail.com>

On Wed, Nov 04, 2009 at 09:14:45PM +0900, jassi brar wrote:

> One of the purposes of this list was to catch trivial mistakes in the
> patches before they are sent upstream for maintainer review. That should help
> save maintainers time and keep them 'receptive' to samsung's patches.

Speaking as one of these upstreams it's not surprising to see issues in
submissions, especially where the drivers are from people who are not
regular contributors to the subsystem.  Like I say, there are some
things where a lot of cleanup is required where not posting does make
sense but much of the code that is being posted is of a perfectly
reasonable standard.  For example, even with posting initially to this
list the first response wasn't raising fundamental issues so there
should be no reason not to have moved upstream with the second round.

Some of the other SoCs have followed an approach similar to this one -
it tends to cause bad experiences with code never getting merged and
with developers becoming reluctant to work with the general kernel
community since they become used to the platform-specific environment
which gives limited subsystem-specific feedback.

> Second purpose being peer review withing samsung.

Sure, and it does make sense to also send the patches to this list when
submitting upstream - it's also useful for people outside Samsung to
keep up to speed on all the latest kernel support for their boards.  I
think it's a really good idea to have the list and keep it in the loop
like that.

  reply	other threads:[~2009-11-04 14:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04  8:27 Revised patches for PCM Controller driver jassisinghbrar
2009-11-04  9:33 ` Ben Dooks
2009-11-04 12:16   ` jassi brar
2009-11-04 11:05 ` Mark Brown
2009-11-04 12:14   ` jassi brar
2009-11-04 14:03     ` Mark Brown [this message]
2009-11-06  2:29       ` When to post patches to this list or upstream Harald Welte

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=20091104140310.GB27652@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=jassi.brar@samsung.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-samsung-soc@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.