* [PATCH 0/5] NetXen: Driver bug fixes
@ 2007-03-09 8:05 Linsys Contractor Mithlesh Thukral
2007-03-09 16:56 ` Jeff Garzik
0 siblings, 1 reply; 7+ messages in thread
From: Linsys Contractor Mithlesh Thukral @ 2007-03-09 8:05 UTC (permalink / raw)
To: netdev; +Cc: amitkale, jeff, mithlesh, netxenproj, rob
Hi All,
I will be sending updates to NetXen: 1G/10G Ethernet driver in subsequent mails.
The patches will be with respect to netdev#upstream.
Regards,
Mithlesh Thukral
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH 0/5] NetXen: Driver bug fixes
2007-03-09 8:05 [PATCH 0/5] NetXen: Driver bug fixes Linsys Contractor Mithlesh Thukral
@ 2007-03-09 16:56 ` Jeff Garzik
2007-03-10 7:09 ` Amit Kale
0 siblings, 1 reply; 7+ messages in thread
From: Jeff Garzik @ 2007-03-09 16:56 UTC (permalink / raw)
To: Linsys Contractor Mithlesh Thukral; +Cc: netdev, amitkale, netxenproj, rob
Linsys Contractor Mithlesh Thukral wrote:
> Hi All,
>
> I will be sending updates to NetXen: 1G/10G Ethernet driver in subsequent mails.
> The patches will be with respect to netdev#upstream.
Are you sure you don't want some of these in #upstream-fixes, queued for
2.6.21-rc?
Jeff
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH 0/5] NetXen: Driver bug fixes
2007-03-09 16:56 ` Jeff Garzik
@ 2007-03-10 7:09 ` Amit Kale
2007-03-10 11:22 ` Jeff Garzik
0 siblings, 1 reply; 7+ messages in thread
From: Amit Kale @ 2007-03-10 7:09 UTC (permalink / raw)
To: Jeff Garzik; +Cc: Linsys Contractor Mithlesh Thukral, netdev, netxenproj, rob
On Friday 09 March 2007 22:26, Jeff Garzik wrote:
> Linsys Contractor Mithlesh Thukral wrote:
> > Hi All,
> >
> > I will be sending updates to NetXen: 1G/10G Ethernet driver in subsequent
> > mails. The patches will be with respect to netdev#upstream.
>
> Are you sure you don't want some of these in #upstream-fixes, queued for
> 2.6.21-rc?
We really want them in both places. If we send them to #upstream-fixes,
they'll break #upstream. Should we send them against both of these branches?
Pardon for this newbie question :-).
Thanks.
-Amit
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH 0/5] NetXen: Driver bug fixes
2007-03-10 7:09 ` Amit Kale
@ 2007-03-10 11:22 ` Jeff Garzik
2007-03-12 6:16 ` Amit Kale
0 siblings, 1 reply; 7+ messages in thread
From: Jeff Garzik @ 2007-03-10 11:22 UTC (permalink / raw)
To: Amit Kale; +Cc: Linsys Contractor Mithlesh Thukral, netdev, netxenproj, rob
Amit Kale wrote:
> On Friday 09 March 2007 22:26, Jeff Garzik wrote:
>> Linsys Contractor Mithlesh Thukral wrote:
>>> Hi All,
>>>
>>> I will be sending updates to NetXen: 1G/10G Ethernet driver in subsequent
>>> mails. The patches will be with respect to netdev#upstream.
>> Are you sure you don't want some of these in #upstream-fixes, queued for
>> 2.6.21-rc?
>
> We really want them in both places. If we send them to #upstream-fixes,
> they'll break #upstream. Should we send them against both of these branches?
Well, I can drop NetXen patches in #upstream, apply these to
#upstream-fixes, and wait for a resend?
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH 0/5] NetXen: Driver bug fixes
2007-03-10 11:22 ` Jeff Garzik
@ 2007-03-12 6:16 ` Amit Kale
2007-03-12 14:31 ` Jeff Garzik
0 siblings, 1 reply; 7+ messages in thread
From: Amit Kale @ 2007-03-12 6:16 UTC (permalink / raw)
To: Jeff Garzik; +Cc: Linsys Contractor Mithlesh Thukral, netdev, netxenproj, rob
On Saturday 10 March 2007 16:52, Jeff Garzik wrote:
> Amit Kale wrote:
> > On Friday 09 March 2007 22:26, Jeff Garzik wrote:
> >> Linsys Contractor Mithlesh Thukral wrote:
> >>> Hi All,
> >>>
> >>> I will be sending updates to NetXen: 1G/10G Ethernet driver in
> >>> subsequent mails. The patches will be with respect to netdev#upstream.
> >>
> >> Are you sure you don't want some of these in #upstream-fixes, queued for
> >> 2.6.21-rc?
> >
> > We really want them in both places. If we send them to #upstream-fixes,
> > they'll break #upstream. Should we send them against both of these
> > branches?
>
> Well, I can drop NetXen patches in #upstream, apply these to
> #upstream-fixes, and wait for a resend?
Could you do that, please? (drop NetXen patches in #upstream)
We'll resend them against #upstream-fixes.
Thanks.
-Amit
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH 0/5] NetXen: Driver bug fixes
2007-03-12 6:16 ` Amit Kale
@ 2007-03-12 14:31 ` Jeff Garzik
2007-03-13 5:21 ` Amit Kale
0 siblings, 1 reply; 7+ messages in thread
From: Jeff Garzik @ 2007-03-12 14:31 UTC (permalink / raw)
To: Amit Kale; +Cc: Linsys Contractor Mithlesh Thukral, netdev, netxenproj, rob
Amit Kale wrote:
> On Saturday 10 March 2007 16:52, Jeff Garzik wrote:
>> Amit Kale wrote:
>>> On Friday 09 March 2007 22:26, Jeff Garzik wrote:
>>>> Linsys Contractor Mithlesh Thukral wrote:
>>>>> Hi All,
>>>>>
>>>>> I will be sending updates to NetXen: 1G/10G Ethernet driver in
>>>>> subsequent mails. The patches will be with respect to netdev#upstream.
>>>> Are you sure you don't want some of these in #upstream-fixes, queued for
>>>> 2.6.21-rc?
>>> We really want them in both places. If we send them to #upstream-fixes,
>>> they'll break #upstream. Should we send them against both of these
>>> branches?
>> Well, I can drop NetXen patches in #upstream, apply these to
>> #upstream-fixes, and wait for a resend?
>
> Could you do that, please? (drop NetXen patches in #upstream)
>
> We'll resend them against #upstream-fixes.
Will note.
Just to be clear, I presume that you will only be resending the bug
fixes against #upstream-fixes (2.6.21-rc). The multiple PCI function
stuff is way too big and invasive for 2.6.21-rc, which is why I
committed that to #upstream (2.6.22).
Jeff
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH 0/5] NetXen: Driver bug fixes
2007-03-12 14:31 ` Jeff Garzik
@ 2007-03-13 5:21 ` Amit Kale
0 siblings, 0 replies; 7+ messages in thread
From: Amit Kale @ 2007-03-13 5:21 UTC (permalink / raw)
To: Jeff Garzik; +Cc: Linsys Contractor Mithlesh Thukral, netdev, netxenproj, rob
On Monday 12 March 2007 20:01, Jeff Garzik wrote:
> Amit Kale wrote:
> > On Saturday 10 March 2007 16:52, Jeff Garzik wrote:
> >> Amit Kale wrote:
> >>> On Friday 09 March 2007 22:26, Jeff Garzik wrote:
> >>>> Linsys Contractor Mithlesh Thukral wrote:
> >>>>> Hi All,
> >>>>>
> >>>>> I will be sending updates to NetXen: 1G/10G Ethernet driver in
> >>>>> subsequent mails. The patches will be with respect to
> >>>>> netdev#upstream.
> >>>>
> >>>> Are you sure you don't want some of these in #upstream-fixes, queued
> >>>> for 2.6.21-rc?
> >>>
> >>> We really want them in both places. If we send them to #upstream-fixes,
> >>> they'll break #upstream. Should we send them against both of these
> >>> branches?
> >>
> >> Well, I can drop NetXen patches in #upstream, apply these to
> >> #upstream-fixes, and wait for a resend?
> >
> > Could you do that, please? (drop NetXen patches in #upstream)
> >
> > We'll resend them against #upstream-fixes.
>
> Will note.
>
> Just to be clear, I presume that you will only be resending the bug
> fixes against #upstream-fixes (2.6.21-rc). The multiple PCI function
> stuff is way too big and invasive for 2.6.21-rc, which is why I
> committed that to #upstream (2.6.22).
Yes. We'll only send bug fixes against #upstream-fixes right now.
We'll send multiple PCI function patches at a much later date: immediately
after 2.6.21 is released.
Thanks a lot.
-Amit
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2007-03-13 5:21 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-03-09 8:05 [PATCH 0/5] NetXen: Driver bug fixes Linsys Contractor Mithlesh Thukral
2007-03-09 16:56 ` Jeff Garzik
2007-03-10 7:09 ` Amit Kale
2007-03-10 11:22 ` Jeff Garzik
2007-03-12 6:16 ` Amit Kale
2007-03-12 14:31 ` Jeff Garzik
2007-03-13 5:21 ` Amit Kale
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).