From: CityK <cityk@rogers.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Tobias Klauser <tklauser@distanz.ch>,
mchehab@infradead.org, linux-media@vger.kernel.org,
video4linux-list@redhat.com, kernel-janitors@vger.kernel.org,
trivial@kernel.org
Subject: Re: [PATCH] V4L: Storage class should be before const qualifier
Date: Thu, 19 Feb 2009 00:52:43 +0000 [thread overview]
Message-ID: <499CAD5B.9010106@rogers.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0902170313310.18110@jikos.suse.cz>
Jiri Kosina wrote:
> On Mon, 16 Feb 2009, CityK wrote:
>
>
>>>> .... [inline patch] ....
>>>>
>>> This doesn't seem to be picked by anyone for current -next/-mmotm, I have
>>> applied it to trivial tree. Thanks,
>>>
>> Will this create any complication? As it is indeed queued in our
>> patchwork: http://patchwork.kernel.org/project/linux-media/list/
>>
>
> Hmm, patchwork ... did this land in any actual code tree? It has been
> submitted by Tobias on 9th Feb and I was not able to find it in any tree
> today, so I applied to to trivial tree (to which the patch has been
> originally CCed).
>
> If you guys actually have queued in some tree, please let me know and I
> will drop it.
I'll defer to Mauro for the absolutes, but it looks like it got applied
to V4L-DVB mainline Hg yesterday and is in Mauro's Linux-next git.
WARNING: multiple messages have this Message-ID (diff)
From: CityK <cityk@rogers.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Tobias Klauser <tklauser@distanz.ch>,
mchehab@infradead.org, linux-media@vger.kernel.org,
video4linux-list@redhat.com, kernel-janitors@vger.kernel.org,
trivial@kernel.org
Subject: Re: [PATCH] V4L: Storage class should be before const qualifier
Date: Wed, 18 Feb 2009 19:52:43 -0500 [thread overview]
Message-ID: <499CAD5B.9010106@rogers.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0902170313310.18110@jikos.suse.cz>
Jiri Kosina wrote:
> On Mon, 16 Feb 2009, CityK wrote:
>
>
>>>> .... [inline patch] ....
>>>>
>>> This doesn't seem to be picked by anyone for current -next/-mmotm, I have
>>> applied it to trivial tree. Thanks,
>>>
>> Will this create any complication? As it is indeed queued in our
>> patchwork: http://patchwork.kernel.org/project/linux-media/list/
>>
>
> Hmm, patchwork ... did this land in any actual code tree? It has been
> submitted by Tobias on 9th Feb and I was not able to find it in any tree
> today, so I applied to to trivial tree (to which the patch has been
> originally CCed).
>
> If you guys actually have queued in some tree, please let me know and I
> will drop it.
I'll defer to Mauro for the absolutes, but it looks like it got applied
to V4L-DVB mainline Hg yesterday and is in Mauro's Linux-next git.
next prev parent reply other threads:[~2009-02-19 0:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 21:06 [PATCH] V4L: Storage class should be before const qualifier Tobias Klauser
2009-02-09 21:06 ` Tobias Klauser
2009-02-16 12:53 ` Jiri Kosina
2009-02-16 12:53 ` Jiri Kosina
2009-02-16 18:04 ` CityK
2009-02-16 18:04 ` CityK
2009-02-17 2:15 ` Jiri Kosina
2009-02-17 2:15 ` Jiri Kosina
2009-02-19 0:52 ` CityK [this message]
2009-02-19 0:52 ` CityK
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=499CAD5B.9010106@rogers.com \
--to=cityk@rogers.com \
--cc=jkosina@suse.cz \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=tklauser@distanz.ch \
--cc=trivial@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 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.