From: Christoph Hellwig <hch@infradead.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, pcihpd-discuss@lists.sourceforge.net
Subject: Re: [PATCH] PCI update for 2.6.3
Date: Fri, 20 Feb 2004 19:19:27 +0000 [thread overview]
Message-ID: <20040220191927.A8816@infradead.org> (raw)
In-Reply-To: <10773039773934@kroah.com>; from greg@kroah.com on Fri, Feb 20, 2004 at 11:06:18AM -0800
On Fri, Feb 20, 2004 at 11:06:18AM -0800, Greg KH wrote:
> @@ -1,5 +1,9 @@
> /*
> - * linux/drivers/pci/msi.c
> + * File: msi.c
Please kill these silly comments. Everyone opening that file should
better know what he's looking at..
next prev parent reply other threads:[~2004-02-20 19:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 19:04 [BK PATCH] PCI update for 2.6.3 Greg KH
2004-02-20 19:06 ` [PATCH] " Greg KH
2004-02-20 19:06 ` Greg KH
2004-02-20 19:06 ` Greg KH
2004-02-20 19:06 ` Greg KH
2004-02-20 19:19 ` Christoph Hellwig [this message]
2004-02-20 19:41 ` Dave Jones
2004-02-20 19:53 ` Greg KH
[not found] <10773039792482@kroah.com>
2004-02-20 19:06 ` Greg KH
2004-02-20 19:06 ` Greg KH
2004-02-20 19:06 ` Greg KH
2004-02-20 19:06 ` Greg KH
2004-02-20 19:06 ` Greg KH
2004-02-20 19:06 ` Greg KH
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=20040220191927.A8816@infradead.org \
--to=hch@infradead.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
/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