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: Mon, 16 Feb 2009 13:04:38 -0500 [thread overview]
Message-ID: <4999AAB6.4090904@rogers.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0902161353150.18110@jikos.suse.cz>
Jiri Kosina wrote:
> On Mon, 9 Feb 2009, Tobias Klauser 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/
next prev parent reply other threads:[~2009-02-16 18:04 UTC|newest]
Thread overview: 5+ 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-16 12:53 ` Jiri Kosina
2009-02-16 18:04 ` CityK [this message]
2009-02-17 2:15 ` Jiri Kosina
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=4999AAB6.4090904@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox