From: Domen Puncer <domen@coderock.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH 2.4.28 1/1] networking: improve readability of
Date: Sat, 18 Jun 2005 11:38:45 +0000 [thread overview]
Message-ID: <20050618113845.GA29699@nd47.coderock.org> (raw)
In-Reply-To: <20050618044041.68ba1006@TANG-FOUR-TWENTY-FIVE.MIT.EDU>
[-- Attachment #1: Type: text/plain, Size: 383 bytes --]
Hi!
On 18/06/05 04:40 -0400, David wrote:
> A trivial patch to improve the readability of dev_set_promiscuity() in
> net/core/dev.c. New code does exactly the same thing as original code.
2.4 is pretty much closed for everything but bug-fixes.
Create patches against latest 2.6.x-rcY (or release if no -rc yet).
That said, I see no beginner mistakes in patch, good work!
Domen
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2005-06-18 11:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 8:40 [KJ] [PATCH 2.4.28 1/1] networking: improve readability of David
2005-06-18 11:38 ` Domen Puncer [this message]
2005-06-18 18:02 ` David
2005-06-19 8:41 ` Domen Puncer
2005-06-20 1:20 ` David
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=20050618113845.GA29699@nd47.coderock.org \
--to=domen@coderock.org \
--cc=kernel-janitors@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.