From: Avinash Patil <patila@marvell.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Stable <stable@vger.kernel.org>,
Amitkumar Karwar <akarwar@marvell.com>,
Cathy Luo <cluo@marvell.com>, Marc Yang <yangyang@marvell.com>,
"Johannes Berg" <johannes@sipsolutions.net>
Subject: Re: [PATCH v2] mwifiex: set netif carrier off in ndo_open
Date: Wed, 28 Jan 2015 17:52:08 +0530 [thread overview]
Message-ID: <1422447728.16899.7.camel@pe-lt950> (raw)
In-Reply-To: <871tmgaznd.fsf@kamboji.qca.qualcomm.com>
On Tue, 2015-01-27 at 09:42 -0800, Kalle Valo wrote:
> Avinash Patil <patila@marvell.com> writes:
>
> > On Mon, 2015-01-19 at 02:24 -0800, Avinash Patil wrote:
> >> From: Johannes Berg <johannes@sipsolutions.net>
> >>
> >> This patch adds fix to set carrier state off during ndo_open.
> >> Carrier should be set to ON when device is ready to send data.
> >> In case of station/adhoc interface device is able to transfer
> >> data after successful association/join operation.
> >> For AP this would be after bss_active event.
> >>
> >> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
> >> Signed-off-by: Avinash Patil <patila@marvell.com>
>
> [...]
>
> > I do not see this patch in master branch as well as in patchworks
> > pending patchlist. Is this one also dropped? Do you want me to resend
> > this as well while I am sending rebased DFS patches?
>
> I had accidentally marked this patch as "Not Applicable" in patchwork,
> sorry about that. Good thing that you noticed. I have applied the patch
> now.
>
Thanks, Kalle.
-Avinash
next prev parent reply other threads:[~2015-01-28 6:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 10:24 [PATCH v2] mwifiex: set netif carrier off in ndo_open Avinash Patil
2015-01-27 12:12 ` Avinash Patil
2015-01-27 17:42 ` Kalle Valo
2015-01-28 12:22 ` Avinash Patil [this message]
2015-01-27 17:40 ` [v2] " 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=1422447728.16899.7.camel@pe-lt950 \
--to=patila@marvell.com \
--cc=akarwar@marvell.com \
--cc=cluo@marvell.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@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