From: Dave Jones <davej@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
dsaxena@plexity.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH TRIVIAL] Add Intel IXP2400 & IXP2800 to PCI.ids
Date: Tue, 3 Aug 2004 00:36:52 +0100 [thread overview]
Message-ID: <20040802233652.GI12724@redhat.com> (raw)
In-Reply-To: <20040802221047.GA15007@kroah.com>
On Mon, Aug 02, 2004 at 03:10:47PM -0700, Greg KH wrote:
> > How's that sound Greg? Or would you prefer I dump
> > this into a bk tree you can regularly pull from?
> > It's only a bit more scripting to do so..
>
> Sending me emails with the patches is fine for me. Feel free to
> automate it if you want to, that would really help out.
Ok, will do so.
> Do we have a way for patches to flow back into sf.net.
You can send unified diffs to pciids@lists.sf.net and the robot
should automatically recognise them, and add them to the
"to be approved" queue. Then its just a matter of how long it
takes for someone with rights to approve entries.
> I remember we
> had some "line too long" warnings that we had to fix up by hand in that
> file that probably didn't make it upstream.
Ah yes, I'd forgotten about those. I'm not sure if they got fixed
upstream or not. Holler if you spot anything odd, and I'll try my
best to get changes to such entries approved quickly.
> I'll go grab the latest version of the patch on your site to add to my
> bk-pci tree right now...
Cool.
Dave
next prev parent reply other threads:[~2004-08-02 23:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 17:08 [PATCH TRIVIAL] Add Intel IXP2400 & IXP2800 to PCI.ids Deepak Saxena
2004-07-16 17:28 ` Jeff Garzik
2004-07-16 19:46 ` Dave Jones
2004-07-16 20:01 ` Dave Jones
2004-08-02 22:10 ` Greg KH
2004-08-02 23:36 ` Dave Jones [this message]
2004-08-02 23:46 ` Greg KH
2004-08-03 0:31 ` Dave Jones
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=20040802233652.GI12724@redhat.com \
--to=davej@redhat.com \
--cc=dsaxena@plexity.net \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.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