From: Avinash Patil <patila@marvell.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Amitkumar Karwar <akarwar@marvell.com>,
Cathy Luo <cluo@marvell.com>, "Marc Yang" <yangyang@marvell.com>
Subject: Re: [1/8] mwifiex: remove redundant nick_name variable
Date: Tue, 27 Jan 2015 16:45:37 +0530 [thread overview]
Message-ID: <1422357337.20608.1.camel@pe-lt950> (raw)
In-Reply-To: <87lhktl843.fsf@kamboji.qca.qualcomm.com>
On Fri, 2015-01-23 at 09:28 -0800, Kalle Valo wrote:
> Kalle Valo <kvalo@codeaurora.org> writes:
>
> >> This is not used anywhere execpt initialization.
> >>
> >> Signed-off-by: Avinash Patil <patila@marvell.com>
> >> Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
> >> Signed-off-by: Cathy Luo <cluo@marvell.com>
> >
> > Thanks, 6 patches applied to wireless-drivers-next.git:
> >
> > 5e7f03b102eb mwifiex: remove redundant nick_name variable
> > 534cfed66caf mwifiex: set wiphy params only once
> > bb2703cffb2f mwifiex: do not declare wdev as pointer
> > 7d2d4fbf4e8e mwifiex: add init parameter to init command routine
> > 16b21941fa9a mwifiex: handle PS events on AP interface as well
> > 770c385d2744 mwifiex: support conversion to any virtual interface type
> >
> > 2 patches failed to apply:
> >
> > Applying: mwifiex: store permanant mac address in adapter structure
> > error: patch failed: drivers/net/wireless/mwifiex/init.c:285
> > error: drivers/net/wireless/mwifiex/init.c: patch does not apply
> > Patch failed at 0001 mwifiex: store permanant mac address in adapter structure
> >
> > Applying: mwifiex: manage virtual interface limits efficiently
> > error: patch failed: drivers/net/wireless/mwifiex/init.c:286
> > error: drivers/net/wireless/mwifiex/init.c: patch does not apply
> > Patch failed at 0001 mwifiex: manage virtual interface limits efficiently
>
> But mwifiex doesn't compile any more so I had to drop all patches.
> Please resend the whole series.
>
Hi Kalle,
I will rebase patches on top of master and resend.
Thanks,
Avinash
next prev parent reply other threads:[~2015-01-27 5:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 11:38 [PATCH 0/8] mwifiex change virtual interface enhancements Avinash Patil
2015-01-13 11:38 ` [PATCH 1/8] mwifiex: remove redundant nick_name variable Avinash Patil
2015-01-23 17:22 ` [1/8] " Kalle Valo
2015-01-23 17:28 ` Kalle Valo
2015-01-27 11:15 ` Avinash Patil [this message]
2015-01-13 11:38 ` [PATCH 2/8] mwifiex: set wiphy params only once Avinash Patil
2015-01-13 11:38 ` [PATCH 3/8] mwifiex: do not declare wdev as pointer Avinash Patil
2015-01-13 11:38 ` [PATCH 4/8] mwifiex: store permanant mac address in adapter structure Avinash Patil
2015-01-13 11:38 ` [PATCH 5/8] mwifiex: add init parameter to init command routine Avinash Patil
2015-01-13 11:38 ` [PATCH 6/8] mwifiex: manage virtual interface limits efficiently Avinash Patil
2015-01-13 11:38 ` [PATCH 7/8] mwifiex: handle PS events on AP interface as well Avinash Patil
2015-01-13 11:38 ` [PATCH 8/8] mwifiex: support conversion to any virtual interface type Avinash Patil
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=1422357337.20608.1.camel@pe-lt950 \
--to=patila@marvell.com \
--cc=akarwar@marvell.com \
--cc=cluo@marvell.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=yangyang@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).