linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Christian Lamparter <chunkeey@web.de>
Cc: linux-wireless@vger.kernel.org, John W Linville <linville@tuxdriver.com>
Subject: Re: [PATCH 3/4] p54pci: cache firmware for suspend/resume v2.1
Date: Sun, 16 Nov 2008 09:35:06 -0600	[thread overview]
Message-ID: <49203DAA.3000102@lwfinger.net> (raw)
In-Reply-To: <200811161220.32828.chunkeey@web.de>

Christian Lamparter wrote:
> Johannes pointed out that the driver has cache the firmware for
> suspend/resume cycles. 
>  
> Signed-off-by: Christian Lamparter <chunkeey@web.de>
> ---
> v1 removed a bit too much. it was very chatty about the firmware capabilities...
> v2 forget release_firmware. d'oh!

Christian,

When you post updated versions, please indicate them in the subject line, as in
"[PATCH 3/4 V3] ...." or a similar indication. When several versions have the
same subject, it gets hard to keep them separate.

Thanks,

Larry

  reply	other threads:[~2008-11-16 15:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14 18:41 [PATCH 3/4] p54: protect against sudden firmware file changes Christian Lamparter
2008-11-14 22:00 ` Johannes Berg
2008-11-14 23:54   ` Christian Lamparter
2008-11-15  0:02     ` Johannes Berg
2008-11-15  0:42       ` [PATCH 3/4] p54pci: cache firmware for suspend/resume Christian Lamparter
2008-11-15 18:30         ` [PATCH 3/4] p54pci: cache firmware for suspend/resume v2 Christian Lamparter
2008-11-16 11:20           ` [PATCH 3/4] p54pci: cache firmware for suspend/resume v2.1 Christian Lamparter
2008-11-16 15:35             ` Larry Finger [this message]
2008-11-16 15:36               ` Johannes Berg
2008-11-15  0:35     ` [PATCH 3/4] p54: protect against sudden firmware file changes Luis R. Rodriguez

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=49203DAA.3000102@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=chunkeey@web.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).