From: "Magnus Damm" <magnus.damm@gmail.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Magnus Damm <damm@igel.co.jp>,
video4linux-list@redhat.com, Paul Mundt <lethal@linux-sh.org>,
linux-sh@vger.kernel.org
Subject: Re: A patch got applied to v4l bypassing v4l lists
Date: Fri, 19 Dec 2008 04:38:10 +0000 [thread overview]
Message-ID: <aec7e5c30812182038v5d89c2bnfc2a71ebd61783b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0812181613050.5510@axis700.grange>
Hi Guennadi,
On Fri, Dec 19, 2008 at 12:23 AM, Guennadi Liakhovetski
<g.liakhovetski@gmx.de> wrote:
> just stumbled upon a patch
>
> sh: sh_mobile ceu clock framework support
>
> 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?
That specific patch set improved clock framework support and changed
quite a few SuperH drivers. I should have CC-ed you. Sorry about that,
will do next time.
/ magnus
next prev parent reply other threads:[~2008-12-19 4:38 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
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 [this message]
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=aec7e5c30812182038v5d89c2bnfc2a71ebd61783b@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=damm@igel.co.jp \
--cc=g.liakhovetski@gmx.de \
--cc=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.org \
--cc=video4linux-list@redhat.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