From: Michael Tokarev <mjt@tls.msk.ru>
To: Jarl Friis <jarl@softace.dk>
Cc: "Stefano Brivio" <stefano.brivio@polimi.it>,
"Gábor Stefanik" <netrolller.3d@gmail.com>,
linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org,
netdev@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: [PATCH 1/2] Added information about which firmware file is being requested.
Date: Wed, 19 Sep 2012 22:42:14 +0400 [thread overview]
Message-ID: <505A1206.4020606@msgid.tls.msk.ru> (raw)
In-Reply-To: <1348053493-22955-1-git-send-email-jarl@softace.dk>
On 19.09.2012 15:18, Jarl Friis wrote:
> + b43info(ctx->dev->wl, "Requesting firmware file '%s'\n", ctx->fwname);
> err = request_firmware(&blob, ctx->fwname, ctx->dev->dev->dev);
Hmm. I wonder if this should be printed in request_firmware()
itself instead of in all callers?
/mjt
WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Jarl Friis <jarl@softace.dk>
Cc: "Stefano Brivio" <stefano.brivio@polimi.it>,
"Gábor Stefanik" <netrolller.3d@gmail.com>,
linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org,
netdev@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 1/2] Added information about which firmware file is being requested.
Date: Wed, 19 Sep 2012 22:42:14 +0400 [thread overview]
Message-ID: <505A1206.4020606@msgid.tls.msk.ru> (raw)
In-Reply-To: <1348053493-22955-1-git-send-email-jarl@softace.dk>
On 19.09.2012 15:18, Jarl Friis wrote:
> + b43info(ctx->dev->wl, "Requesting firmware file '%s'\n", ctx->fwname);
> err = request_firmware(&blob, ctx->fwname, ctx->dev->dev->dev);
Hmm. I wonder if this should be printed in request_firmware()
itself instead of in all callers?
/mjt
next prev parent reply other threads:[~2012-09-19 18:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 11:18 [PATCH 1/2] Added information about which firmware file is being requested Jarl Friis
2012-09-19 11:18 ` Jarl Friis
2012-09-19 11:18 ` [PATCH 2/2] Using LP firmware for taking advantage of the low-power capabilities Jarl Friis
2012-09-19 11:18 ` Jarl Friis
2012-09-19 15:08 ` Larry Finger
2012-09-19 15:08 ` Larry Finger
2012-09-19 18:54 ` Jarl Friis
2012-09-19 18:54 ` Jarl Friis
2012-09-19 18:54 ` Jarl Friis
2012-09-19 19:33 ` Arend van Spriel
2012-09-19 19:33 ` Arend van Spriel
2012-09-19 19:33 ` Arend van Spriel
2012-09-19 19:40 ` Jarl Friis
2012-09-19 19:40 ` Jarl Friis
2012-09-19 20:10 ` Jarl Friis
2012-09-19 20:10 ` Jarl Friis
2012-09-19 20:10 ` Jarl Friis
2012-09-20 6:05 ` Rafał Miłecki
2012-09-20 6:05 ` Rafał Miłecki
2012-09-20 6:32 ` Jarl Friis
2012-09-20 6:32 ` Jarl Friis
2012-09-20 6:32 ` Jarl Friis
2012-09-19 12:39 ` [PATCH 1/2] Added information about which firmware file is being requested Julian Calaby
2012-09-19 12:39 ` Julian Calaby
2012-09-19 12:39 ` Julian Calaby
2012-09-19 18:42 ` Michael Tokarev [this message]
2012-09-19 18:42 ` Michael Tokarev
2012-09-19 18:56 ` Jarl Friis
2012-09-19 18:56 ` Jarl Friis
2012-09-19 18:56 ` Jarl Friis
2012-09-20 6:06 ` Rafał Miłecki
2012-09-20 6:06 ` Rafał Miłecki
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=505A1206.4020606@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=b43-dev@lists.infradead.org \
--cc=jarl@softace.dk \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=netrolller.3d@gmail.com \
--cc=stefano.brivio@polimi.it \
/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.