From: Chris Wright <chrisw@osdl.org>
To: Fabian Frederick <Fabian.Frederick@skynet.be>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.5-mm4] Trivial : emu10k1 definition redundancy
Date: Wed, 14 Apr 2004 13:20:41 -0700 [thread overview]
Message-ID: <20040414132041.S22989@build.pdx.osdl.net> (raw)
In-Reply-To: <1081973268.5445.35.camel@bluerhyme.real3>; from Fabian.Frederick@skynet.be on Wed, Apr 14, 2004 at 10:07:48PM +0200
* Fabian Frederick (Fabian.Frederick@skynet.be) wrote:
> Remove emu10k1_t definition redundancy
This one's probably fine. It'd be nice if you could inline the patches
in your mail (making sure whitespaces won't get munged and lines won't
get linewrapped by your mailer). Makes it easier to view the patch and
reply with comments inlined in the patch.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
prev parent reply other threads:[~2004-04-14 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 20:07 Fabian Frederick
2004-04-14 20:20 ` Chris Wright [this message]
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=20040414132041.S22989@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=Fabian.Frederick@skynet.be \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®