From: Andrew Morton <akpm@linux-foundation.org>
To: Alexey Klimov <klimov.linux@gmail.com>
Cc: mchehab@infradead.org, linux-media@vger.kernel.org, abogani@texware.it
Subject: Re: [patch 1/6] radio-mr800.c: missing mutex include
Date: Wed, 10 Jun 2009 16:23:44 -0700 [thread overview]
Message-ID: <20090610162344.3f29de3c.akpm@linux-foundation.org> (raw)
In-Reply-To: <208cbae30906101621v6ba12fbbsf29c0d6ec35768d8@mail.gmail.com>
On Thu, 11 Jun 2009 03:21:36 +0400 Alexey Klimov <klimov.linux@gmail.com> wrote:
> On Wed, Jun 10, 2009 at 11:44 PM, <akpm@linux-foundation.org> wrote:
> > From: Alessio Igor Bogani <abogani@texware.it>
> >
> > radio-mr800.c uses struct mutex, so while <linux/mutex.h> seems to be
> > pulled in indirectly by one of the headers it already includes, the right
> > thing is to include it directly.
>
> It was already applied to v4l-dvb tree (and probably to v4l git tree).
It isn't in today's linux-next.
next prev parent reply other threads:[~2009-06-10 23:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 19:44 [patch 1/6] radio-mr800.c: missing mutex include akpm
2009-06-10 23:21 ` Alexey Klimov
2009-06-10 23:23 ` Andrew Morton [this message]
2009-06-11 0:36 ` Mauro Carvalho Chehab
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=20090610162344.3f29de3c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=abogani@texware.it \
--cc=klimov.linux@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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