From: Samuel Ortiz <sameo@linux.intel.com>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 1/9] mfd: Add commands abstraction layer for SI476X MFD
Date: Tue, 9 Apr 2013 09:17:11 +0200 [thread overview]
Message-ID: <20130409071711.GB23447@zurbaran> (raw)
In-Reply-To: <CAHQ1cqGytarQ9bkOiq-MdpRbKiHBTRPJy90Cbg=Sr4J7MWNj+g@mail.gmail.com>
On Mon, Apr 08, 2013 at 01:40:40PM -0700, Andrey Smirnov wrote:
> On Mon, Apr 8, 2013 at 1:09 PM, Samuel Ortiz <sameo@linux.intel.com> wrote:
> > On Mon, Apr 08, 2013 at 11:34:43AM -0700, Andrey Smirnov wrote:
> > > On Mon, Apr 8, 2013 at 3:16 AM, Samuel Ortiz <sameo@linux.intel.com>
> > wrote:
> > > > This file doesn't exist yet, which breaks bisectability.
> > > > I'm fine with you including it with the first patch. I will prepare a
> > > branch
> > > > with the mfd patches from your serie for Mauro to pull from.
> > > >
> > >
> > > It was initially one single patch(in v1), and I split it in three upon
> > > Hans' request(for ease of reviewing).
> > It probably made sense then, but now, as I said, it breaks bisectability.
> > So
> > I'd appreciate if you could add this header file to this first patch so
> > that I
> > can merge the MFD parts independently.
> > Again, I will provide a branch for Mauro to pull from and apply the
> > remaining
> > patches on top of it.
> >
> >
> OK, I will squash the commits and make another version of the patches.
The separation of the patches as it is now looks good to me. But you need to
add the media header to the first MFD patches, no need to squash commits
together.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2013-04-09 7:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 2:47 [PATCH v8 0/9] Driver for Si476x series of chips Andrey Smirnov
2013-03-27 2:47 ` [PATCH v8 1/9] mfd: Add commands abstraction layer for SI476X MFD Andrey Smirnov
2013-04-08 10:16 ` Samuel Ortiz
[not found] ` <CAHQ1cqE4aokZA98VfCWwRtkaNPm6dMnegibVz4BHfYW_VrAUBA@mail.gmail.com>
2013-04-08 20:09 ` Samuel Ortiz
[not found] ` <CAHQ1cqGytarQ9bkOiq-MdpRbKiHBTRPJy90Cbg=Sr4J7MWNj+g@mail.gmail.com>
2013-04-09 7:17 ` Samuel Ortiz [this message]
2013-03-27 2:47 ` [PATCH v8 2/9] mfd: Add the main bulk of core driver for SI476x code Andrey Smirnov
2013-03-27 2:47 ` [PATCH v8 3/9] mfd: Add chip properties handling code for SI476X MFD Andrey Smirnov
2013-03-27 2:47 ` [PATCH v8 4/9] mfd: Add header files and Kbuild plumbing for SI476x MFD core Andrey Smirnov
2013-03-27 2:47 ` [PATCH v8 5/9] v4l2: Fix the type of V4L2_CID_TUNE_PREEMPHASIS in the documentation Andrey Smirnov
2013-03-27 2:47 ` [PATCH v8 6/9] v4l2: Add standard controls for FM receivers Andrey Smirnov
2013-03-27 2:47 ` [PATCH v8 7/9] v4l2: Add documentation for the FM RX controls Andrey Smirnov
2013-03-27 2:47 ` [PATCH v8 8/9] v4l2: Add private controls base for SI476X Andrey Smirnov
2013-03-27 2:47 ` [PATCH v8 9/9] v4l2: Add a V4L2 driver for SI476X MFD 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=20130409071711.GB23447@zurbaran \
--to=sameo@linux.intel.com \
--cc=andrew.smirnov@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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;
as well as URLs for NNTP newsgroup(s).