Re: [PATCH TRIVIAL] Add Intel IXP2400 & IXP2800 to PCI.ids

From: Greg KH (greg_at_kroah.com)
Date: 08/03/04

  • Next message: Francois Romieu: "Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related)"
    Date:	Mon, 2 Aug 2004 15:10:47 -0700
    To: Dave Jones <davej@redhat.com>, Jeff Garzik <jgarzik@pobox.com>, dsaxena@plexity.net, linux-kernel@vger.kernel.org
    
    

    On Fri, Jul 16, 2004 at 09:01:13PM +0100, Dave Jones wrote:
    > 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..

    Sending me emails with the patches is fine for me. Feel free to
    automate it if you want to, that would really help out.

    Do we have a way for patches to flow back into sf.net. 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.

    I'll go grab the latest version of the patch on your site to add to my
    bk-pci tree right now...

    thanks,

    greg k-h
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Francois Romieu: "Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related)"

    Relevant Pages

    • Re: 2.6.8-rc2 crashes
      ... I get my patches from ... >| kernel.org, either from the main Linus tree, or Andrews akpm tree. ... Additions to this message made by Gene Heskett are Copyright 2004, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.8-rc2 crashes
      ... I get my patches from ... |>| kernel.org, either from the main Linus tree, or Andrews akpm tree. ... |>| after a long session of doing something else that fails. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: merge status
      ... are our patches in it" ... closer this tree is to what mainline will be next release, ... > practicality. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: new dev model (was Re: Default cache_hot_time value back to 10ms)
      ... >> Major developers such as David and Al don't have trees that see wide ... >> allow for stabilization of the main tree prior to relesae. ... That's 500 patches which are either non-bugfixes or minor ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: RFD: Kernel release numbering
      ... > some patches that belong in the 2.6.X.Y tree go straight to you/Andrew, ... Think of how the -mm tree has evolved - with me and Andrew learning how ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)