public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexey Klimov <klimov.linux@gmail.com>,
	linux-media@vger.kernel.org, abogani@texware.it
Subject: Re: [patch 1/6] radio-mr800.c: missing mutex include
Date: Wed, 10 Jun 2009 21:36:00 -0300	[thread overview]
Message-ID: <20090610213600.09d592cd@pedra.chehab.org> (raw)
In-Reply-To: <20090610162344.3f29de3c.akpm@linux-foundation.org>

Em Wed, 10 Jun 2009 16:23:44 -0700
Andrew Morton <akpm@linux-foundation.org> escreveu:

> 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.

Hi Andrew,

Thanks for remind us about those 6 patches. I'll double check if those are
already on my staging tree. If they aren't I'll apply or comment.

Since I'm currently in the proccess updating my trees, I should be adding 
several pending patches on my -git tree, probably in time for tomorrow's
linux-next tree.



Cheers,
Mauro

      reply	other threads:[~2009-06-11  0:36 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
2009-06-11  0:36     ` Mauro Carvalho Chehab [this message]

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=20090610213600.09d592cd@pedra.chehab.org \
    --to=mchehab@infradead.org \
    --cc=abogani@texware.it \
    --cc=akpm@linux-foundation.org \
    --cc=klimov.linux@gmail.com \
    --cc=linux-media@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