* Re: [PATCH 2.6] pci.ids for e1000
@ 2003-09-12 20:15 Xose Vazquez Perez
0 siblings, 0 replies; 4+ messages in thread
From: Xose Vazquez Perez @ 2003-09-12 20:15 UTC (permalink / raw)
To: netdev, linux-kernel
Jeff Garzik wrote:
> The general idea is to keep 2.4, 2.6, and pciids.sf.net in sync.
is there sync between 2.4, 2.6, and pciids.sf.net ? ;-)
Linus and Marcelo should not accept patches against pci.ids,
all updates should go to pciids.sf.net. And every X time
to do a sync with 2.4 and 2.6.
It's the easiest, because otherwise is a chaos and it
takes too much work to do several merges:
2.4 <-> 2.6
2.4 <-> pciids
2.4 <-> 2.6
--
Que trabajen los romanos, que tienen el pecho de lata.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH 2.6] pci.ids for e1000
@ 2003-09-12 19:07 Xose Vazquez Perez
2003-09-30 6:25 ` David S. Miller
2003-09-30 23:32 ` Greg KH
0 siblings, 2 replies; 4+ messages in thread
From: Xose Vazquez Perez @ 2003-09-12 19:07 UTC (permalink / raw)
To: netdev, linux-kernel
Jeff Garzik wrote:
> The general idea is to keep 2.4, 2.6, and pciids.sf.net in sync.
is there sync between 2.4, 2.6, and pciids.sf.net ? ;-)
Linus and Marcelo should not accept patches against pci.ids,
all updates should go to pciids.sf.net. And every X time
to do a sync with 2.4 and 2.6.
It's the easiest, because otherwise is a chaos and it
takes too much work to do several merges:
2.4 <-> 2.6
2.4 <-> pciids
2.4 <-> 2.6
--
Que trabajen los romanos, que tienen el pecho de lata.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH 2.6] pci.ids for e1000
2003-09-12 19:07 Xose Vazquez Perez
@ 2003-09-30 6:25 ` David S. Miller
2003-09-30 23:32 ` Greg KH
1 sibling, 0 replies; 4+ messages in thread
From: David S. Miller @ 2003-09-30 6:25 UTC (permalink / raw)
To: Xose Vazquez Perez; +Cc: netdev, linux-kernel
On Fri, 12 Sep 2003 21:07:17 +0200
Xose Vazquez Perez <xose@wanadoo.es> wrote:
> Linus and Marcelo should not accept patches against pci.ids,
> all updates should go to pciids.sf.net. And every X time
> to do a sync with 2.4 and 2.6.
I don't know if this is the best idea.
When merging in a driver, it makes perfect sense to add the
appropriate device IDs to all PCI ID files.
On the other hand this could make life difficult for the
pciids.sf.net person.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH 2.6] pci.ids for e1000
2003-09-12 19:07 Xose Vazquez Perez
2003-09-30 6:25 ` David S. Miller
@ 2003-09-30 23:32 ` Greg KH
1 sibling, 0 replies; 4+ messages in thread
From: Greg KH @ 2003-09-30 23:32 UTC (permalink / raw)
To: Xose Vazquez Perez; +Cc: netdev, linux-kernel
On Fri, Sep 12, 2003 at 09:07:17PM +0200, Xose Vazquez Perez wrote:
> Jeff Garzik wrote:
>
> > The general idea is to keep 2.4, 2.6, and pciids.sf.net in sync.
>
> is there sync between 2.4, 2.6, and pciids.sf.net ? ;-)
>
> Linus and Marcelo should not accept patches against pci.ids,
> all updates should go to pciids.sf.net. And every X time
> to do a sync with 2.4 and 2.6.
I'd love to see a volunteer to try to sync these files up and routinely
send updates to the pci maintainers of the different kernel trees.
Anyone?
I also agree with David, it's completly acceptable for drivers to add
their ids to this file when they are added to the kernel tree.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2003-09-30 23:52 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-09-12 20:15 [PATCH 2.6] pci.ids for e1000 Xose Vazquez Perez
-- strict thread matches above, loose matches on Subject: below --
2003-09-12 19:07 Xose Vazquez Perez
2003-09-30 6:25 ` David S. Miller
2003-09-30 23:32 ` Greg KH
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).