From: David Miller <davem@davemloft.net>
To: amit.salecha@qlogic.com
Cc: netdev@vger.kernel.org, dhananjay.phadke@qlogic.com
Subject: Re: [PATCH 0/4] netxen: endianness fixes
Date: Thu, 14 Jan 2010 03:08:54 -0800 (PST) [thread overview]
Message-ID: <20100114.030854.52825026.davem@davemloft.net> (raw)
In-Reply-To: <1263465787-28203-1-git-send-email-amit.salecha@qlogic.com>
From: Amit Kumar Salecha <amit.salecha@qlogic.com>
Date: Thu, 14 Jan 2010 02:43:03 -0800
> Series of 4 small patches to fix endianness issues and License header.
> These issues were suggested by Ben Hutchings for qlcnic driver,
> same apply to netxen_nic driver.
> Please apply these patches in net-2.6 tree.
These endianness fixes for netxen are starting to get reduclious.
You mean in all this time, nobody noticed that reading the MAC
address isn't done correctly on big-endian?
Well then I guess all of these small endianness fixes aren't
very critical this late in the RC series.
I want to start slimming down the amount of small driver fixes
that are still being submitted this late. And these endian
bits that show the device is basically unused by anyone (perhaps
other than you) on big endian are a good way to start.
Submit them for net-next-2.6 of course, but I'm tossing this
series for net-2.6, sorry.
next prev parent reply other threads:[~2010-01-14 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 10:43 [PATCH 0/4] netxen: endianness fixes Amit Kumar Salecha
2010-01-14 10:43 ` [PATCH 1/4] netxen: fix endianness read mac address Amit Kumar Salecha
2010-01-14 10:43 ` [PATCH 2/4] netxen: Fix endianness intr coalesce Amit Kumar Salecha
2010-01-14 10:43 ` [PATCH 3/4] netxen: fix license header Amit Kumar Salecha
2010-01-14 10:43 ` [PATCH 4/4] netxen: fix sparse warning Amit Kumar Salecha
2010-01-14 11:08 ` David Miller [this message]
2010-01-14 14:57 ` [PATCH 0/4] netxen: endianness fixes Dhananjay Phadke
2010-01-15 0:54 ` David Miller
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=20100114.030854.52825026.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amit.salecha@qlogic.com \
--cc=dhananjay.phadke@qlogic.com \
--cc=netdev@vger.kernel.org \
/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).