public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: A patch got applied to v4l bypassing v4l lists
Date: Thu, 18 Dec 2008 16:08:41 +0000	[thread overview]
Message-ID: <20081218160841.GA13851@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0812181613050.5510@axis700.grange>

On Thu, Dec 18, 2008 at 04:23:53PM +0100, Guennadi Liakhovetski wrote:
> Hi Magnus, Paul,
> 
> just stumbled upon a patch
> 
> sh: sh_mobile ceu clock framework support
> 
> http://marc.info/?l=linux-sh&m\x122545217725877&w=2
> 
> with diffstat
> 
>  arch/sh/boards/board-ap325rxa.c            |    2 +-
>  arch/sh/boards/mach-migor/setup.c          |    2 +-
>  drivers/media/video/sh_mobile_ceu_camera.c |   20 +++++++++++++++++++-
>  3 files changed, 21 insertions(+), 3 deletions(-)
> 
> that has been pulled through linux-sh ML and the sh tree without even 
> being cc-ed to the v4l list, which wasn't a very good idea IMHO. Now this 
> patch has to be manually "back-ported" to v4l hg repos using the 
> "kernel-sync:" tag and only in part, because arch/sh directory is not in 
> hg at all. Can we please avoid this in the future?
> 
It wasn't cc-ed to the v4l list because there was nothing v4l specific
about it. The patch in question likewise has a dependency on arch/sh/
changes, and it makes no sense to merge the v4l component out of order.

The last time v4l patches related to sh drivers got merged out of order
with the board support patches, both the driver and the boards were
broken for over a week. When there is something relevant to v4l, then the
list will be CCed, but I will not hold trivial patches hostage to
overzealous patchflow enforcement when the end result is likely to cause
more trouble than it prevents.

When touching files outside of arch/sh/, it is always a judgement call
whether it makes sense to include it through that subsystem's tree or
whether to simply merge it directly. In this case, given that it is an
sh-specific driver, and the changes are trivial in nature, with an
inherent dependency on other bits, I see no reason to force this change
through the v4l tree.

If you wish to be CC-ed on all trivial patches relating to sh drivers in
the v4l space, that is certainly something we can watch out for in the
future, but I will still be applying the patches where it makes sense.

  reply	other threads:[~2008-12-18 16:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18 15:23 A patch got applied to v4l bypassing v4l lists Guennadi Liakhovetski
2008-12-18 16:08 ` Paul Mundt [this message]
2008-12-18 16:22   ` Guennadi Liakhovetski
2008-12-18 16:24 ` Paul Mundt
2008-12-18 16:49   ` Guennadi Liakhovetski
2008-12-18 21:18     ` Mauro Carvalho Chehab
2008-12-18 23:30       ` Guennadi Liakhovetski
2008-12-18 22:57         ` Mauro Carvalho Chehab
2008-12-19  7:15           ` Guennadi Liakhovetski
2008-12-18 19:36 ` Jean-Christophe PLAGNIOL-VILLARD
2008-12-18 20:12   ` Guennadi Liakhovetski
2008-12-19  4:38 ` Magnus Damm
2008-12-19  7:52 ` Paul Mundt

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=20081218160841.GA13851@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-sh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox