From: Mithlesh Thukral <mithlesh@netxen.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: netdev@vger.kernel.org, amitkale@netxen.com,
netxenproj@linsyssoft.com, rob@netxen.com
Subject: Re: [PATCH 0/7] NetXen: Make driver use multiple PCI functions
Date: Wed, 25 Apr 2007 11:24:00 +0530 [thread overview]
Message-ID: <200704251124.00640.mithlesh@netxen.com> (raw)
In-Reply-To: <462E45DE.5030702@garzik.org>
On Tuesday 24 April 2007 23:31, Jeff Garzik wrote:
> Mithlesh Thukral wrote:
> > hi All,
> >
> > Thanks Stephen for your suggestion. I am resending the 7 patches
> > after incorporating the suggestion.
> > These patches are with respect to netdev#upstream and we wish their
> > inclusion in 2.6.22 kernel.
> >
> > Out of these the first 2 patches were already accepted into the netdev
> > tree, but we have requested them to be dropped. So we are resending those
> > 2. Please see the following thread for more details :
> > http://www.spinics.net/lists/netdev/msg26805.html
>
> So what does that mean?
>
> If the patches were accepted, then you must send further patches
> cumulative to what is currently in the tree. If it is already accepted,
> you cannot "drop" a patch.
My apologies for the confusion created by my email.
We wish inclusion of these 7 patches in the netdev tree. All these patches are
cumulative with what is currently present in the tree.
Thanks,
Mithlesh Thukral
>
> Jeff
next prev parent reply other threads:[~2007-04-25 6:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 14:51 [PATCH 0/7] NetXen: Make driver use multiple PCI functions Mithlesh Thukral
2007-04-24 18:01 ` Jeff Garzik
2007-04-25 5:54 ` Mithlesh Thukral [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-19 14:49 Linsys Contractor Mithlesh Thukral
2007-04-13 15:34 Linsys Contractor Mithlesh Thukral
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=200704251124.00640.mithlesh@netxen.com \
--to=mithlesh@netxen.com \
--cc=amitkale@netxen.com \
--cc=jeff@garzik.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.