From: Kalle Valo <kvalo@codeaurora.org>
To: Amitkumar Karwar <akarwar@marvell.com>
Cc: "linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>, "Cathy Luo" <cluo@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>,
"rajatja\@google.com" <rajatja@google.com>,
"briannorris\@google.com" <briannorris@google.com>,
"dmitry.torokhov\@gmail.com" <dmitry.torokhov@gmail.com>,
Xinming Hu <huxm@marvell.com>
Subject: Re: [1/2] mwifiex: code rearrangement in pcie.c and sdio.c
Date: Tue, 17 Jan 2017 13:10:07 +0200 [thread overview]
Message-ID: <87bmv6osc0.fsf@codeaurora.org> (raw)
In-Reply-To: <01b93ecb7f4e43799ff6a9087daed1b5@SC-EXCH04.marvell.com> (Amitkumar Karwar's message of "Tue, 17 Jan 2017 08:34:18 +0000")
Amitkumar Karwar <akarwar@marvell.com> writes:
> Hi Kalle,
>
>> From: Kalle Valo [mailto:kvalo@codeaurora.org]
>> Sent: Thursday, January 12, 2017 8:25 PM
>> To: Amitkumar Karwar
>> Cc: linux-wireless@vger.kernel.org; Cathy Luo; Nishant Sarmukadam;
>> rajatja@google.com; briannorris@google.com; dmitry.torokhov@gmail.com;
>> Xinming Hu
>> Subject: Re: [1/2] mwifiex: code rearrangement in pcie.c and sdio.c
>>
>> Amitkumar Karwar <akarwar@marvell.com> writes:
>>
>> >> But these didn't. Can you please rebase these and resubmit in one
>> >> patchset? Less conflicts that way.
>> >>
>> >
>> > The problem here is you tried to apply the patches in reverse order.
>> Sorry for the confusion.
>> > Please apply pending patches in below order.
>> >
>> > [v3,1/5] mwifiex: don't wait for main_process in shutdown_drv ---
>> Apply this patch first.
>> > [v3,2/5] mwifiex: do not free firmware dump memory in shutdown_drv
>> > [v3,3/5] mwifiex: get rid of drv_info* adapter variables [v3,4/5]
>> > mwifiex: wait firmware dump complete during card remove process
>> > [v3,5/5] mwifiex: move pcie_work and related variables inside card
>> >
>> > [1/2] mwifiex: code rearrangement in pcie.c and sdio.c [2/2] mwifiex:
>> > get rid of global user_rmmod flag
>> >
>> > mwifiex: use module_*_driver helper macros
>> >
>> > [1/5] mwifiex: get rid of mwifiex_do_flr wrapper [2/5] mwifiex:
>> > cleanup in PCIe flr code path [3/5] mwifiex: sdio card reset
>> > enhancement [4/5] mwifiex: get rid of __mwifiex_sdio_remove helper
>> > [5/5] mwifiex: get rid of global save_adapter and sdio_work
>>
>> Thanks, now I was able to apply these but please do double check the
>> result in wireless-drivers-next.
>>
>> I also noticed a new warning:
>>
>> drivers/net/wireless/marvell/mwifiex/pcie.c: In function
>> 'mwifiex_pcie_remove':
>> drivers/net/wireless/marvell/mwifiex/pcie.c:303:5: warning: 'fw_status'
>> may be used uninitialized in this function [-Wmaybe-uninitialized]
>> if (fw_status == FIRMWARE_READY_PCIE && !adapter->mfg_mode) {
>>
>> Actually I'm not sure if this warning was caused by these patches as I
>> have recently updated my ancient gcc to a newer one (5.4.0), but please
>> take a look and send a fix if it's a valid warning.
>>
>
> Below CL fixes this warning.
>
> https://patchwork.kernel.org/patch/9515899/
Good, thanks. I'll apply that shortly.
--
Kalle Valo
next prev parent reply other threads:[~2017-01-17 11:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 14:52 [PATCH 1/2] mwifiex: code rearrangement in pcie.c and sdio.c Amitkumar Karwar
2016-11-30 14:52 ` [PATCH 2/2] mwifiex: get rid of global user_rmmod flag Amitkumar Karwar
2016-11-30 18:38 ` Dmitry Torokhov
2016-12-01 13:11 ` Amitkumar Karwar
2016-12-05 11:09 ` [1/2] mwifiex: code rearrangement in pcie.c and sdio.c Kalle Valo
2016-12-07 10:52 ` Amitkumar Karwar
2016-12-30 11:28 ` Kalle Valo
2017-01-11 15:47 ` Amitkumar Karwar
2017-01-12 14:55 ` Kalle Valo
2017-01-17 8:34 ` Amitkumar Karwar
2017-01-17 11:10 ` Kalle Valo [this message]
2016-12-30 11:24 ` Kalle Valo
2017-01-12 14:46 ` 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=87bmv6osc0.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=akarwar@marvell.com \
--cc=briannorris@google.com \
--cc=cluo@marvell.com \
--cc=dmitry.torokhov@gmail.com \
--cc=huxm@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nishants@marvell.com \
--cc=rajatja@google.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).