From: Jarek Poplawski <jarkao2@o2.pl>
To: Jeff Garzik <jeff@garzik.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] fix for system lockups in 2.6.18-rcX caused by bcm43xx
Date: Thu, 14 Sep 2006 10:25:32 +0200 [thread overview]
Message-ID: <20060914082532.GA2513@ff.dom.local> (raw)
In-Reply-To: <4505DD51.5090000@garzik.org>
On 12-09-2006 00:04, Jeff Garzik wrote:
> John W. Linville wrote:
...
>> Not too explicitly, but I think Andrew mentions it in "The Perfect
>> Patch":
>>
>> http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
>>
>> While you are looking, you might review Jeff's version of the same idea:
>>
>> http://linux.yyz.us/patch-format.html
>
> And also Documentation/SubmittingPatches, which ATM seems to have more
> detail than either page.
>
> Jeff
"Attachments are discouraged, but some corporate mail systems
provide no other way to send patches."
I thought they didn't read this but now I understand for whom
Mozilla Firefox is breaking all those lines with no mercy!
Jarek P.
next prev parent reply other threads:[~2006-09-14 8:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-09 1:47 [PATCH] fix for system lockups in 2.6.18-rcX caused by bcm43xx Larry Finger
[not found] ` <45021D4A.6040805-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-09-09 15:23 ` John W. Linville
2006-09-09 16:04 ` Larry Finger
[not found] ` <4502E62B.5060601-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-09-09 19:42 ` Daniel Drake
2006-09-11 19:28 ` John W. Linville
2006-09-11 19:59 ` Larry Finger
[not found] ` <4505C005.2070302-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-09-11 20:35 ` John W. Linville
2006-09-11 22:04 ` Jeff Garzik
2006-09-14 8:25 ` Jarek Poplawski [this message]
2006-09-14 8:29 ` Jarek Poplawski
2006-10-05 20:52 ` Randy Dunlap
2006-10-06 5:57 ` Jarek Poplawski
2006-10-06 6:19 ` Jarek Poplawski
2006-10-06 6:57 ` Jarek Poplawski
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=20060914082532.GA2513@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=jeff@garzik.org \
--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 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.