From: Jeff Garzik <jeff@garzik.org>
To: Amit Kale <amitkale@netxen.com>
Cc: Linsys Contractor Mithlesh Thukral <mithlesh@netxen.com>,
netdev@vger.kernel.org, netxenproj@linsyssoft.com,
rob@netxen.com
Subject: Re: [PATCH 0/5] NetXen: Driver bug fixes
Date: Sat, 10 Mar 2007 06:22:04 -0500 [thread overview]
Message-ID: <45F294DC.50300@garzik.org> (raw)
In-Reply-To: <200703101239.16417.amitkale@netxen.com>
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?
next prev parent reply other threads:[~2007-03-10 11:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2007-03-12 6:16 ` Amit Kale
2007-03-12 14:31 ` Jeff Garzik
2007-03-13 5:21 ` Amit Kale
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=45F294DC.50300@garzik.org \
--to=jeff@garzik.org \
--cc=amitkale@netxen.com \
--cc=mithlesh@netxen.com \
--cc=netdev@vger.kernel.org \
--cc=netxenproj@linsyssoft.com \
--cc=rob@netxen.com \
/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;
as well as URLs for NNTP newsgroup(s).