linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ganapathi Bhat <gbhat@marvell.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Cathy Luo" <cluo@marvell.com>, Zhiyuan Yang <yangzy@marvell.com>,
	James Cao <jcao@marvell.com>, Rakesh Parmar <rakeshp@marvell.com>,
	Hemantkumar Suthar <shemant@marvell.com>
Subject: RE: [PATCH v3] mwifiex: add support for sd8977 chipset
Date: Thu, 10 Jan 2019 09:11:45 +0000	[thread overview]
Message-ID: <CY4PR18MB1237E6B9605D4BC3A4E8BEC1A0840@CY4PR18MB1237.namprd18.prod.outlook.com> (raw)
In-Reply-To: <87wonc6g4q.fsf@purkki.adurom.net>

Hi Kalle,
> Subject: Re: [PATCH v3] mwifiex: add support for sd8977 chipset
> 
> Ganapathi Bhat <gbhat@marvell.com> writes:
> 
> > From: Hemantkumar Suthar <shemant@marvell.com>
> >
> > This patch adds support for 8977 chipset to mwifiex with SDIO
> > interface. Register offsets and supported feature flags are updated.
> > Firmware image used will be mrvl/sd8977_uapsta.bin.
> >
> > Signed-off-by: Hemantkumar Suthar <shemant@marvell.com>
> > Signed-off-by: Rakesh Parmar <rakeshp@marvell.com>
> > Signed-off-by: Cathy Luo <cluo@marvell.com>
> > Signed-off-by: Ganapathi Bhat <gbhat@marvell.com>
> 
> Changelog missing:
> 
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingp
> atches#changelog_missing
> 
> But no need to resend, just reply to this mail and explain what changed from
> v2.

v3: Remove commit ID('From  a0f96e63...') in v2

> 
Regards,
Ganapathi

  reply	other threads:[~2019-01-10  9:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10  8:45 [PATCH v3] mwifiex: add support for sd8977 chipset Ganapathi Bhat
2019-01-10  9:01 ` Kalle Valo
2019-01-10  9:11   ` Ganapathi Bhat [this message]
2019-02-01 12:11 ` Kalle Valo

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=CY4PR18MB1237E6B9605D4BC3A4E8BEC1A0840@CY4PR18MB1237.namprd18.prod.outlook.com \
    --to=gbhat@marvell.com \
    --cc=cluo@marvell.com \
    --cc=jcao@marvell.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rakeshp@marvell.com \
    --cc=shemant@marvell.com \
    --cc=yangzy@marvell.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).