From: Dave Jones <davej@redhat.com>
To: Jeff Garzik <jgarzik@pobox.com>,
dsaxena@plexity.net, greg@kroah.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH TRIVIAL] Add Intel IXP2400 & IXP2800 to PCI.ids
Date: Fri, 16 Jul 2004 21:01:13 +0100 [thread overview]
Message-ID: <20040716200113.GB20555@redhat.com> (raw)
In-Reply-To: <20040716194654.GA20555@redhat.com>
On Fri, Jul 16, 2004 at 08:46:54PM +0100, Dave Jones wrote:
> On Fri, Jul 16, 2004 at 01:28:00PM -0400, Jeff Garzik wrote:
>
> > >This is already in sf.net, just not upstream.
> >
> > Why not post a patch updating to latest sf.net?
> >
> > We really need to keep the two in sync.
>
> This could be trivially automated to have a script
> grab latest, generate diff, and send a mail to Linux-kernel
> once a week/month/whatever.
>
> I'll hack something up.
Nightly snapshots will appear here..
http://www.codemonkey.org.uk/projects/pci/
I've thought again on the regular sending.. as they can be
quite large diffs occasionally, it's probably better if
gregkh pulls this into his pci tree every so often,
that way it goes into mainline semi-automatically, and
also gets some visibility in -mm for a while.
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..
Looking at the diff is actually quite handy, theres some
bogons that have crept in there. I'll fix those up.
Dave
next prev parent reply other threads:[~2004-07-16 20:02 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 [this message]
2004-08-02 22:10 ` Greg KH
2004-08-02 23:36 ` Dave Jones
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=20040716200113.GB20555@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