linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: Dmitry Torokhov <dtor@google.com>
Cc: Xinming Hu <huxinming820@gmail.com>,
	Linux Wireless <linux-wireless@vger.kernel.org>,
	Kalle Valo <kvalo@qca.qualcomm.com>,
	Rajat Jain <rajatja@google.com>,
	Amitkumar Karwar <akarwar@marvell.com>,
	Cathy Luo <cluo@marvell.com>, Xinming Hu <huxm@marvell.com>
Subject: Re: [PATCH 2/3] mwifiex: using general print function during device intialization
Date: Mon, 3 Apr 2017 11:42:08 -0700	[thread overview]
Message-ID: <20170403184208.GB116262@google.com> (raw)
In-Reply-To: <CAE_wzQ890=BCQviifEkcgfFO7XA+SNeFCUgn_Bx9_4n9uB1nsg@mail.gmail.com>

On Fri, Mar 31, 2017 at 03:46:58PM -0700, Dmitry Torokhov wrote:
> On Thu, Mar 30, 2017 at 2:19 AM, Xinming Hu <huxinming820@gmail.com> wrote:
> > From: Xinming Hu <huxm@marvell.com>
> >
> > adapter->dev is initialized after mwifiex_register done, before that
> > print message by general pr_* function
> 
> No, we should move away from naked pr_*() as much as possible. Please
> change  mwifiex_register() to accept "dev" parameter and assign
> adapter->dev early enough so that the standard mwifiex_err() calls are
> usable.

Agreed. You mean like I did here? :)

ba1c7e45ec22 mwifiex: set adapter->dev before starting to use mwifiex_dbg()

That's in v4.11-rc4, partly as a bugfix to this:

2e02b5814217 ("mwifiex: Allow mwifiex early access to device structure")

> Also consider changing _mwifiex_dbg() to handle cases when
> adapter->dev is NULL and fall back to pr_<level>.

That'd be nice. It would have mitigated the problems of commit
2e02b5814217 too.

Brian

> > Signed-off-by: Xinming Hu <huxm@marvell.com>
> > Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
> > ---
> >  drivers/net/wireless/marvell/mwifiex/pcie.c | 78 ++++++++++++-----------------
> >  drivers/net/wireless/marvell/mwifiex/sdio.c |  3 +-
> >  2 files changed, 34 insertions(+), 47 deletions(-)

[...]

  reply	other threads:[~2017-04-03 18:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30  9:19 [PATCH 1/3] mwifiex: remove unnecessary wakeup interrupt number sanity check Xinming Hu
2017-03-30  9:19 ` [PATCH 2/3] mwifiex: using general print function during device intialization Xinming Hu
2017-03-31 22:46   ` Dmitry Torokhov
2017-04-03 18:42     ` Brian Norris [this message]
2017-04-05  6:41       ` Xinming Hu
2017-03-30  9:19 ` [PATCH 3/3] mwifiex: pcie: avoid hardcode wifi-only firmware name Xinming Hu
2017-03-31 22:50   ` Dmitry Torokhov
2017-04-03 18:48     ` Brian Norris
2017-04-06  8:08       ` [EXT] " Xinming Hu
2017-04-06  8:05     ` Xinming Hu
2017-04-05 10:47   ` [3/3] " Kalle Valo
     [not found]   ` <20170405104711.1092260DC7@smtp.codeaurora.org>
2017-04-06  8:14     ` RE:] " Xinming Hu
2017-03-31 22:37 ` [PATCH 1/3] mwifiex: remove unnecessary wakeup interrupt number sanity check Dmitry Torokhov
2017-04-03 18:33   ` Brian Norris
2017-04-05  5:23     ` Xinming Hu
2017-04-05  5:16   ` [EXT] " Xinming Hu

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=20170403184208.GB116262@google.com \
    --to=briannorris@chromium.org \
    --cc=akarwar@marvell.com \
    --cc=cluo@marvell.com \
    --cc=dtor@google.com \
    --cc=huxinming820@gmail.com \
    --cc=huxm@marvell.com \
    --cc=kvalo@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --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).