From: Jeff Garzik <jgarzik@pobox.com>
To: ram.vepa@neterion.com
Cc: netdev@vger.kernel.org, support@neterion.com
Subject: Re: [PATCH 2.6.25 1/2]S2io: Fixes to enable multiple transmit fifo support
Date: Mon, 17 Dec 2007 22:04:34 -0500 [thread overview]
Message-ID: <476738C2.1060905@pobox.com> (raw)
In-Reply-To: <1197920149.7518.40.camel@flash>
Ramkrishna Vepa wrote:
> Fixes to enable multiple transmit fifos (upto a maximum of eight).
> - Moved single tx_lock from struct s2io_nic to struct fifo_info.
> - Moved single ufo_in_band_v structure from struct s2io_nic to struct
> fifo_info.
> - Assign the respective interrupt number for the transmitting fifo in the
> transmit descriptor (TXD).
> - Added boundary checks for number of FIFOs enabled and FIFO length.
>
> Signed-off-by: Surjit Reang <surjit.reang@neterion.com>
> Signed-off-by: Sreenivasa Honnur <sreenivasa.honnur@neterion.com>
> Signed-off-by: Ramkrishna Vepa <ram.vepa@neterion.com>
applied 1-2 to #upstream
prev parent reply other threads:[~2007-12-18 3:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 19:35 [PATCH 2.6.25 1/2]S2io: Fixes to enable multiple transmit fifo support Ramkrishna Vepa
2007-12-18 3:04 ` Jeff Garzik [this message]
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=476738C2.1060905@pobox.com \
--to=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=ram.vepa@neterion.com \
--cc=support@neterion.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).