public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: "BAJWA, MEHAR" <mehar.bajwa@ti.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Navada Kanyana, Mukund" <navada@ti.com>,
	"liam.r.girdwood@intel.com" <liam.r.girdwood@intel.com>
Subject: Re: [RESEND: PATCH]: Mfd-Initial-support-for-Texas-Instruments-AIC-family-Codecs
Date: Fri, 5 Apr 2013 17:51:51 +0200	[thread overview]
Message-ID: <20130405155151.GG17363@zurbaran> (raw)
In-Reply-To: <7506746A41B00D4598AF8BB18AB156933E9116F8@DBDE01.ent.ti.com>

Hi Mehar,

On Sun, Feb 17, 2013 at 05:15:38AM +0000, BAJWA, MEHAR wrote:
> Hi Samuel,
>     I am re-sending the MFD support for AIC family of Audio CODECs
> from Texas Instruments. The patch was tested on mfd-for-linus-3.8-1.
> I would like to request that this be considered for inclusion in the kernel
> at the next available window. Could you please let me know if you have
> any comments/recommendations for this patch. We would like to work on it
> and get it up-streamed.
The patch looks good to me, but I'd like it to be splitted in several pieces.
You can probably place the core, the irq, the spi and the i2c pieces in their
own patches.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  reply	other threads:[~2013-04-05 15:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <511DFF8A.1080801@ti.com>
2013-02-17  5:15 ` [RESEND: PATCH]: Mfd-Initial-support-for-Texas-Instruments-AIC-family-Codecs BAJWA, MEHAR
2013-04-05 15:51   ` Samuel Ortiz [this message]
2013-04-15 12:11     ` [PATCH: v2]: Mfd-Initial-support-for-Texas-Instruments-AIC-family-Codecs x0172184
2013-04-15 13:25       ` 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=20130405155151.GG17363@zurbaran \
    --to=sameo@linux.intel.com \
    --cc=liam.r.girdwood@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mehar.bajwa@ti.com \
    --cc=navada@ti.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