From: Jarkko Nikula <jhnikula@gmail.com>
To: Mauro Carvalho Chehab <maurochehab@gmail.com>
Cc: Eduardo Valentin <eduardo.valentin@nokia.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH 1/2] V4L/DVB: radio-si4713: Release i2c adapter in driver cleanup paths
Date: Mon, 23 Aug 2010 13:50:09 +0300 [thread overview]
Message-ID: <20100823135009.f362e812.jhnikula@gmail.com> (raw)
In-Reply-To: <20100802130952.bc968de6.jhnikula@gmail.com>
Hi
On Mon, 2 Aug 2010 13:09:52 +0300
Jarkko Nikula <jhnikula@gmail.com> wrote:
> On Mon, 05 Jul 2010 16:28:30 -0300
> Mauro Carvalho Chehab <maurochehab@gmail.com> wrote:
>
> > Hi Eduardo,
> >
> > Could you please review those two patches?
> >
> Hmm.. are these two patches already late for 2.6.36? I have two another
> patches to arch/arm/mach-omap2/board-rx51-peripherals.c and
> sound/soc/omap/rx51.c that are pending from patch 2/2.
>
Is there anything I can do with these two patches? Would reposting to
lkml make any sense (like getting nak/ack about regulator framework
conversion etc)? At least I would like to drive these patches to some
conclusion :-)
https://patchwork.kernel.org/patch/105846/
https://patchwork.kernel.org/patch/105847/
--
Jarkko
next prev parent reply other threads:[~2010-08-23 10:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-13 18:09 [PATCH 1/2] V4L/DVB: radio-si4713: Release i2c adapter in driver cleanup paths Jarkko Nikula
2010-06-13 18:09 ` [PATCH 2/2] V4L/DVB: radio-si4713: Add regulator framework support Jarkko Nikula
2010-06-29 6:32 ` Jarkko Nikula
2010-09-07 19:49 ` Eduardo Valentin
2010-09-08 5:59 ` Jarkko Nikula
2010-09-08 12:11 ` Eduardo Valentin
2010-09-08 13:00 ` Jarkko Nikula
2010-07-05 19:28 ` [PATCH 1/2] V4L/DVB: radio-si4713: Release i2c adapter in driver cleanup paths Mauro Carvalho Chehab
2010-08-02 10:09 ` Jarkko Nikula
2010-08-23 10:50 ` Jarkko Nikula [this message]
2010-09-07 19:15 ` Eduardo Valentin
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=20100823135009.f362e812.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=eduardo.valentin@nokia.com \
--cc=linux-media@vger.kernel.org \
--cc=maurochehab@gmail.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.