From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>,
hverkuil@xs4all.nl, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 00/12] Driver for Si476x series of chips
Date: Thu, 18 Apr 2013 14:57:53 -0300 [thread overview]
Message-ID: <20130418145753.7bacee9b@redhat.com> (raw)
In-Reply-To: <20130418174547.GV8798@zurbaran>
Em Thu, 18 Apr 2013 19:45:47 +0200
Samuel Ortiz <sameo@linux.intel.com> escreveu:
> On Thu, Apr 18, 2013 at 02:28:00PM -0300, Mauro Carvalho Chehab wrote:
> > Em Thu, 18 Apr 2013 09:58:26 -0700
> > Andrey Smirnov <andrew.smirnov@gmail.com> escreveu:
> >
> > > Driver for Si476x series of chips
> > >
> > > This is a eight version of the patchset originaly posted here:
> > > https://lkml.org/lkml/2012/9/13/590
> > >
> > > Second version of the patch was posted here:
> > > https://lkml.org/lkml/2012/10/5/598
> > >
> > > Third version of the patch was posted here:
> > > https://lkml.org/lkml/2012/10/23/510
> > >
> > > Fourth version of the patch was posted here:
> > > https://lkml.org/lkml/2013/2/18/572
> > >
> > > Fifth version of the patch was posted here:
> > > https://lkml.org/lkml/2013/2/26/45
> > >
> > > Sixth version of the patch was posted here:
> > > https://lkml.org/lkml/2013/2/26/257
> > >
> > > Seventh version of the patch was posted here:
> > > https://lkml.org/lkml/2013/2/27/22
> > >
> > > Eighth version of the patch was posted here:
> > > https://lkml.org/lkml/2013/3/26/891
> > >
> > > To save everyone's time I'll repost the original description of it:
> > >
> > > This patchset contains a driver for a Silicon Laboratories 476x series
> > > of radio tuners. The driver itself is implemented as an MFD devices
> > > comprised of three parts:
> > > 1. Core device that provides all the other devices with basic
> > > functionality and locking scheme.
> > > 2. Radio device that translates between V4L2 subsystem requests into
> > > Core device commands.
> > > 3. Codec device that does similar to the earlier described task, but
> > > for ALSA SoC subsystem.
> > >
> > > v9 of this driver has following changes:
> > > - MFD part of the driver no longer depends on the header file added
> > > by the radio driver(media/si476x.h) which should potential
> > > restore the bisectability of the patches
> > >
> > > Mauro, I am not sure if you reverted changes in patches 5 - 7, so I am
> > > including them just in case.
> >
> > No, I didn't revert all patches. I just reverted two patches: the
> > last one, and the one that Samuel asked me.
> Sorry I didn't have time to check your email from yesterday, but I was
> actually hoping you would revert the whole patchset, then pull from my
> mfd-next/topic/si476x branch to fetch the MFD bits and then apply the
> v4l2/media ones (From patchset v9) on top of that.
> Does that make sense to you ?
I don't rebase my tree, as this would cause troubles for everybody that
relies on it.
Reverting the entire patchset is hard, as there are lots of patches after
them, and some patches touch at V4L2 core. Even reverting those
two patches hit conflicts, that I needed to manage, in order to avoid
compilation breakages.
So, I really prefer to confine the patch reversion to the absolute
minimum.
--
Cheers,
Mauro
next prev parent reply other threads:[~2013-04-18 17:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 16:58 [PATCH v9 00/12] Driver for Si476x series of chips Andrey Smirnov
2013-04-18 16:58 ` [PATCH 01/12] mfd: Add commands abstraction layer for SI476X MFD Andrey Smirnov
2013-04-18 16:58 ` [PATCH 02/12] mfd: Add the main bulk of core driver for SI476x code Andrey Smirnov
2013-04-18 16:58 ` [PATCH 03/12] mfd: Add chip properties handling code for SI476X MFD Andrey Smirnov
2013-04-18 16:58 ` [PATCH 04/12] mfd: Add header files and Kbuild plumbing for SI476x MFD core Andrey Smirnov
2013-04-18 16:58 ` [PATCH 05/12] v4l2: Fix the type of V4L2_CID_TUNE_PREEMPHASIS in the documentation Andrey Smirnov
2013-04-18 16:58 ` [PATCH 06/12] v4l2: Add standard controls for FM receivers Andrey Smirnov
2013-04-18 16:58 ` [PATCH 07/12] v4l2: Add documentation for the FM RX controls Andrey Smirnov
2013-04-18 16:58 ` [PATCH 08/12] v4l2: Add private controls base for SI476X Andrey Smirnov
2013-04-18 16:58 ` [PATCH 09/12] v4l2: Add a V4L2 driver for SI476X MFD Andrey Smirnov
2013-04-18 22:26 ` Samuel Ortiz
2013-04-18 16:58 ` [PATCH 10/12] radio-si476x: vidioc_s* now uses a const parameter Andrey Smirnov
2013-04-18 16:58 ` [PATCH 11/12] si476x: Fix some config dependencies and a compile warnings Andrey Smirnov
2013-04-18 17:56 ` Samuel Ortiz
2013-04-18 16:58 ` [PATCH 12/12] radio-si476x: Fix incorrect pointer checking Andrey Smirnov
2013-04-18 17:48 ` Dan Carpenter
2013-04-18 17:28 ` [PATCH v9 00/12] Driver for Si476x series of chips Mauro Carvalho Chehab
2013-04-18 17:45 ` Samuel Ortiz
2013-04-18 17:57 ` Mauro Carvalho Chehab [this message]
2013-04-18 18:17 ` Samuel Ortiz
2013-04-18 18:23 ` Samuel Ortiz
2013-04-18 20:27 ` Mauro Carvalho Chehab
2013-04-19 21:31 ` Samuel Ortiz
2013-04-19 21:48 ` Andrey Smirnov
2013-04-21 5:53 ` Andrey Smirnov
2013-04-21 9:33 ` Mauro Carvalho Chehab
2013-04-22 2:01 ` Andrey Smirnov
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=20130418145753.7bacee9b@redhat.com \
--to=mchehab@redhat.com \
--cc=andrew.smirnov@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sameo@linux.intel.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;
as well as URLs for NNTP newsgroup(s).