Linux bluetooth development
 help / color / mirror / Atom feed
From: Amitkumar Karwar <akarwar@marvell.com>
To: Rob Herring <robh@kernel.org>
Cc: "linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	Nishant Sarmukadam <nishants@marvell.com>,
	"wnhuang@chromium.com" <wnhuang@chromium.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Cathy Luo <cluo@marvell.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Xinming Hu <huxm@marvell.com>
Subject: RE: [PATCH v4 1/3] mwifiex: register platform specific driver
Date: Mon, 29 Feb 2016 14:04:44 +0000	[thread overview]
Message-ID: <6e3955140c3d46e0ab3094432ae941ec@SC-EXCH04.marvell.com> (raw)
In-Reply-To: <20160218143803.GX9654@rob-hp-laptop>

Hi Rob,

> From: Rob Herring [mailto:robh@kernel.org]
> Sent: Thursday, February 18, 2016 8:08 PM
> To: Amitkumar Karwar
> Cc: linux-bluetooth@vger.kernel.org; Nishant Sarmukadam;
> wnhuang@chromium.com; devicetree@vger.kernel.org; Cathy Luo; linux-
> kernel@vger.kernel.org; Xinming Hu
> Subject: Re: [PATCH v4 1/3] mwifiex: register platform specific driver
> 
> On Tue, Feb 16, 2016 at 01:14:37AM -0800, Amitkumar Karwar wrote:
> > From: Xinming Hu <huxm@marvell.com>
> >
> > Platform device and driver provides easy way to interact with
> > device-tree-enabled system.
> >
> > This patch registers platform driver and reorganise existing device
> > tree specific code. Corresponding device tree binding file is also
> > created.
> >
> > Signed-off-by: Xinming Hu <huxm@marvell.com>
> > Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
> > ---
> > v3: Don't update adapter->dt_node if mwifiex_plt_dev is NULL
> > v4: Corrected the 'name' and 'compatible' property names.(Arnd
> Bergmann and Rob
> >     Herring)
> >     Patch description wraped in 72 columns(Rob Herring)
> >     Moved DT binding file to bindings/net/wireless/(Rob Herring)
> > ---

Thanks for reviewing mwifiex and btmrvl patch series.
We are working on a updated version which will address your review comments.

Regards,
Amitkumar

      reply	other threads:[~2016-02-29 14:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16  9:14 [PATCH v4 1/3] mwifiex: register platform specific driver Amitkumar Karwar
2016-02-16  9:14 ` [PATCH v4 2/3] mwifiex: parse chip specific gpio from device tree Amitkumar Karwar
2016-02-18 14:37   ` Rob Herring
2016-02-16  9:14 ` [PATCH v4 3/3] mwifiex: parse host wakeup configuration from device Amitkumar Karwar
2016-02-18 14:37   ` Rob Herring
2016-02-16 11:28 ` [PATCH v4 1/3] mwifiex: register platform specific driver Arnd Bergmann
2016-02-18 14:38 ` Rob Herring
2016-02-29 14:04   ` Amitkumar Karwar [this message]

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=6e3955140c3d46e0ab3094432ae941ec@SC-EXCH04.marvell.com \
    --to=akarwar@marvell.com \
    --cc=cluo@marvell.com \
    --cc=devicetree@vger.kernel.org \
    --cc=huxm@marvell.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nishants@marvell.com \
    --cc=robh@kernel.org \
    --cc=wnhuang@chromium.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