All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Amitkumar Karwar <akarwar@marvell.com>
Cc: <linux-wireless@vger.kernel.org>, Cathy Luo <cluo@marvell.com>,
	Nishant Sarmukadam <nishants@marvell.com>,
	Xinming Hu <huxm@marvell.com>,
	Amitkumar Karwar <akarwar@marvell.com>
Subject: Re: [1/4] mwifiex: fix missing debug messages
Date: Thu,  7 Jan 2016 09:15:44 +0000 (UTC)	[thread overview]
Message-ID: <20160107091544.35438605BE@smtp.codeaurora.org> (raw)
In-Reply-To: <1451571855-29449-1-git-send-email-akarwar@marvell.com>


> From: Xinming Hu <huxm@marvell.com>
> 
> Some critical messages are missed until "adapter->dev"
> gets initialized in mwifiex_register_dev().
> We will use pr_* print message instead of mwifiex_dbg at
> those places to resolve the problem.
> 
> Signed-off-by: Xinming Hu <huxm@marvell.com>
> Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>

Thanks, 3 patches applied to wireless-drivers-next.git:

fdb1e28e05c9 mwifiex: fix missing debug messages
91442431c3f9 mwifiex: increase priority for critical message
ee548d4b1036 mwifiex: reduce cloned skb queue size

Kalle Valo

      parent reply	other threads:[~2016-01-07  9:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-31 14:24 [PATCH 1/4] mwifiex: fix missing debug messages Amitkumar Karwar
2015-12-31 14:24 ` [PATCH 2/4] mwifiex: enable pcie MSIx interrupt mode support Amitkumar Karwar
2015-12-31 16:31   ` kbuild test robot
2015-12-31 18:03   ` kbuild test robot
2016-01-05 12:57     ` Amitkumar Karwar
2016-01-07  9:17   ` Kalle Valo
2015-12-31 14:24 ` [PATCH 3/4] mwifiex: increase priority for critical message Amitkumar Karwar
2015-12-31 14:24 ` [PATCH 4/4] mwifiex: reduce cloned skb queue size Amitkumar Karwar
2016-01-07  9:15 ` Kalle Valo [this message]

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=20160107091544.35438605BE@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=akarwar@marvell.com \
    --cc=cluo@marvell.com \
    --cc=huxm@marvell.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nishants@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.