From: Greg KH <greg@kroah.com>
To: Olaf Hering <olh@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH] be more verbose in gen-devlist
Date: Sun, 13 Mar 2005 00:27:36 -0800 [thread overview]
Message-ID: <20050313082736.GA21182@kroah.com> (raw)
In-Reply-To: <20050313081709.GA26100@suse.de>
On Sun, Mar 13, 2005 at 09:17:09AM +0100, Olaf Hering wrote:
> On Sat, Mar 12, Greg KH wrote:
>
> > Why #if this? Why not just always do this?
>
> Because it always triggers with current sf.net snapshot.
Someone said they were going to submit those shorter strings that the
kernel has, back to sf.net. Guess that didn't happen yet, and is the
main reason I can't just sync up all the time with that repository.
Oh well, we'll be dropping support for the pci.ids file by the end of
the year or so, so it's not that big of a deal.
thanks,
greg k-h
next prev parent reply other threads:[~2005-03-13 8:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 19:28 [PATCH] be more verbose in gen-devlist Olaf Hering
2005-03-12 20:36 ` Greg KH
2005-03-13 8:17 ` Olaf Hering
2005-03-13 8:27 ` Greg KH [this message]
2005-03-13 8:33 ` Olaf Hering
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=20050313082736.GA21182@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=olh@suse.de \
/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