From: Michael Buesch <mb@bu3sch.de>
To: linville@tuxdriver.com
Cc: Jeff Garzik <jeff@garzik.org>,
netdev@vger.kernel.org, bcm43xx-dev@lists.berlios.de
Subject: Please re-apply the pwork macsuspend patch
Date: Fri, 30 Jun 2006 19:38:08 +0200 [thread overview]
Message-ID: <200606301938.08285.mb@bu3sch.de> (raw)
Hi John,
Please re-apply the "Suspend MAC in periodic work" now.
I neither remember the exact name, nor do I still have
the patch. Well, I deleted it since it was applied... hrm...
But I assume you know which patch I mean.
Please re-apply it because:
* It does _NO_ harm.
* It _fixes_ a bug.
* I am doing development which depends on this patch
My development is stalled without the patch going
into the tree. (Or at least it is a _lot_ more painful).
* It does _NO_ harm.
* Every "bug" or inconvenience (udelay), that Jeff saw, was
not introduced by this patch. It was only in the _context_.
In fact, that udelay loop has been there _forever_.
Thanks.
--
Greetings Michael.
reply other threads:[~2006-06-30 17:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200606301938.08285.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=jeff@garzik.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
/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).