From: Jeff Garzik <jeff@garzik.org>
To: Ron Mercer <ron.mercer@qlogic.com>
Cc: akpm@osdl.org, netdev@vger.kernel.org
Subject: Re: [PATCH] Qlogic qla3xxx driver v2.02.00-k36 for upstream inclusion.
Date: Wed, 19 Jul 2006 16:41:09 -0400 [thread overview]
Message-ID: <44BE98E5.7060207@garzik.org> (raw)
In-Reply-To: <0BB3E5E7462EEA4295BC02D49691DC0705BC91@AVEXCH1.qlogic.org>
Ron Mercer wrote:
>
> Andrew,
>
> Attached is a patch to the qla3xxx driver in your -mm test kernel. This
> patch makes the following changes:
>
> -Removed potential infinite loop in ql_sem_spinlock().
> -Relaxed hardware locking granularity.
> -Fixed irq_request() where shared flag was used in MSI environment.
> -Removed queue containing TX control blocks. This resource has a one to
> one correspondence to each entry in the TX queue.
> -Removed unnecessary tx_lock.
> -Changed version to v2.02.00-k36.
>
> The above changes plus the changes from the k35 patch address Jeff
> Garzik's concerns from his response. His response can be reviewed at
> this URL:
>
> http://marc.theaimsgroup.com/?l=linux-netdev&m=115101855424635&w=2
> <http://marc.theaimsgroup.com/?l=linux-netdev&m=115101855424635&w=2>
>
>
>
> This driver has been through several iterations on the netdev list and
> we feel this driver is ready for inclusion in the upstream kernel.
Send me a patch via private email (for size reasons), include a proper
Signed-off-by line per http://linux.yyz.us/patch-format.html and I will
merge this driver straightaway.
Jeff
next parent reply other threads:[~2006-07-19 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1090CAF73D6FFE4EA45395454C82937B05214A4B@AVEXCH1.qlogic.org>
[not found] ` <0BB3E5E7462EEA4295BC02D49691DC0705BC91@AVEXCH1.qlogic.org>
2006-07-19 20:41 ` Jeff Garzik [this message]
2006-07-20 9:12 ` [PATCH] Qlogic qla3xxx driver v2.02.00-k36 for upstream inclusion Michael Tokarev
2006-07-20 14:32 Ron Mercer
2006-07-20 14:50 ` Andrew Vasquez
2006-07-20 14:59 ` Michael Tokarev
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=44BE98E5.7060207@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=netdev@vger.kernel.org \
--cc=ron.mercer@qlogic.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).