From: Samuel Ortiz <samuel.ortiz@intel.com>
To: "Richard Röjfors" <richard.rojfors@pelagicore.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH] mfd: Add support for the timberdale FPGA.
Date: Thu, 11 Feb 2010 16:26:21 +0100 [thread overview]
Message-ID: <20100211152620.GA6025@sortiz.org> (raw)
In-Reply-To: <4B71D70A.6030806@pelagicore.com>
Hi Richard,
On Tue, Feb 09, 2010 at 09:43:38PM +0000, Richard Röjfors wrote:
> On 2/4/10 10:28 AM, Samuel Ortiz wrote:
> > On Wed, Feb 03, 2010 at 05:23:57PM +0000, Mauro Carvalho Chehab wrote:
> >>> Ok, thanks again for your understanding. This is definitely material for the
> >>> next merge window, so I'll merge it into my for-next branch.
> >>
> >> The last version of the driver is OK for merging. However, I noticed one issue:
> >> it depends on two drivers that were already merged on my tree:
> >>
> >> +config RADIO_TIMBERDALE
> >> + tristate "Enable the Timberdale radio driver"
> >> + depends on MFD_TIMBERDALE && VIDEO_V4L2
> >> + select RADIO_TEF6862
> >> + select RADIO_SAA7706H
> >>
> >> Currently, the dependency seems to happen only at Kconfig level.
> >>
> >> Maybe the better is to return to the previous plan: apply it via my tree, as the better
> >> is to have it added after those two radio i2c drivers.
> > I'm fine with that. Richard sent me a 2nd version of his patch that I was
> > about to merge.
> > Richard, could you please post this patch here, or to lkml with Mauro cc'ed ?
> > I'll add my SOB to it and then it will go through Mauro's tree.
>
> Now when the radio driver made it into the media tree, can I post an
> updated MFD which defines these drivers too?
> Is a complete MFD patch preferred, or just an incremental against the
> last one?
Since the mfd driver is currently merged into Mauro's tree, you should make
incremental patches against it. At least that's how I'd take it in my tree.
Mauro, do you agree ?
Cheers,
Samuel.
>
> --Richard
--
Intel Open Source Technology Centre
http://oss.intel.com/
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number: 302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
next prev parent reply other threads:[~2010-02-11 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 12:04 [PATCH] mfd: Add support for the timberdale FPGA Richard Röjfors
2010-02-03 9:16 ` Mauro Carvalho Chehab
2010-02-03 9:43 ` Richard Röjfors
2010-02-03 9:51 ` Mauro Carvalho Chehab
2010-02-03 10:03 ` Samuel Ortiz
2010-02-03 10:18 ` Mauro Carvalho Chehab
2010-02-03 12:36 ` Samuel Ortiz
2010-02-03 17:23 ` Mauro Carvalho Chehab
2010-02-04 9:28 ` Samuel Ortiz
2010-02-09 21:43 ` Richard Röjfors
2010-02-11 15:26 ` Samuel Ortiz [this message]
2010-02-11 15:28 ` 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=20100211152620.GA6025@sortiz.org \
--to=samuel.ortiz@intel.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=richard.rojfors@pelagicore.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