public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: "Richard Röjfors" <richard.rojfors.ext@mocean-labs.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/9] MFD: Added Timberdale driver
Date: Mon, 15 Jun 2009 08:56:54 -0700	[thread overview]
Message-ID: <20090615085654.d8504527.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090615101116.GB4094@sortiz.org>

On Mon, 15 Jun 2009 12:11:19 +0200 Samuel Ortiz <sameo@linux.intel.com> wrote:

> On Fri, Jun 05, 2009 at 03:41:45PM +0200, Richard R__jfors wrote:
> > MFD driver for the Timberdale FPGA The FPGA can be found on the
> > Intel Atom development board, Russellville for in-vechicle infotainment
> > 
> > The FPGA is connected via PCIe
> > 
> > The driver basically exposes a lot of platform devices for the
> > different IPs within the FPGA, and doing IRQ multiplexing
> > 
> > Signed-off-by: Richard R__jfors <richard.rojfors.ext@mocean-labs.com>
> patch #4 of this serie is an mfd driver too, so I guess I should have been
> cc'ed on it too.
> So, if I understand this thread correctly, we should proceed like that:
> 
> 1) Richard comes up with an updated xilinx patch (patch #2).
> 2) Andrew sends all patches but patch 7 to the relevant maintainers.
> 3) When all patches but 7 are in Linus tree, I take patch 7 and include it in
> my pull request to Linus.
> 
> Andrew, does that make sense to you? Do you want me to take patch #4 as well?

We could do it that way.  Or maintainers could just review-and-ack the
relevant patches and I could merge them.


  reply	other threads:[~2009-06-15 15:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 13:41 [PATCH 7/9] MFD: Added Timberdale driver Richard Röjfors
2009-06-15 10:11 ` Samuel Ortiz
2009-06-15 15:56   ` Andrew Morton [this message]
2009-06-16  9:21     ` Samuel Ortiz

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=20090615085654.d8504527.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.rojfors.ext@mocean-labs.com \
    --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