From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] resync ATI PCI idents into base kernel
Date: Tue, 08 Mar 2005 10:15:30 +0000 [thread overview]
Message-ID: <1110276929.28860.93.camel@localhost.localdomain> (raw)
In-Reply-To: <20050308053941.GA16450@kroah.com>
> Was there a reason you did this without using tabs, like the rest of the
> file?
No but I'll send Linus an update to fix that now.
> Again, the maintainer chain is well documented...
Really - so does it go to the PCI maintainer, the IDE maintainer or the
DRI maintainer or someone else, or all of them, or in bits to different
ones remembering there are dependancies and I don't use bitcreeper ?
Alan
next prev parent reply other threads:[~2005-03-08 10:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200503072216.j27MGxtP024504@hera.kernel.org>
2005-03-08 5:39 ` [PATCH] resync ATI PCI idents into base kernel Greg KH
2005-03-08 10:15 ` Alan Cox [this message]
2005-03-08 10:42 ` Bartlomiej Zolnierkiewicz
2005-03-08 11:25 ` Alan Cox
2005-03-08 22:33 ` Christoph Hellwig
2005-03-09 15:45 ` Alan Cox
2005-03-09 22:00 ` Christoph Hellwig
2005-03-09 22:29 ` Alan Cox
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=1110276929.28860.93.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--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