All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	jeff@garzik.org, cramerj@intel.com, john.ronciak@intel.com
Subject: Re: [PATCH]: e1000 endianness bugs
Date: Thu, 16 Mar 2006 07:31:41 +0000	[thread overview]
Message-ID: <20060316073141.GA29074@infradead.org> (raw)
In-Reply-To: <20060315.142628.28661597.davem@davemloft.net>

On Wed, Mar 15, 2006 at 02:26:28PM -0800, David S. Miller wrote:
> 
> 	return -E_NO_BIG_ENDIAN_TESTING;
> 
> [E1000]: Fix 4 missed endianness conversions on RX descriptor fields.

Could the e1000 maintainers please add endianess annotations so that
sparse will catch such things in the future?


  parent reply	other threads:[~2006-03-16  7:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-15 22:26 [PATCH]: e1000 endianness bugs David S. Miller
2006-03-15 23:33 ` Jesse Brandeburg
2006-03-15 23:40   ` David S. Miller
2006-03-16  7:31 ` Christoph Hellwig [this message]
2006-03-17  0:17 ` Jeff Garzik

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=20060316073141.GA29074@infradead.org \
    --to=hch@infradead.org \
    --cc=cramerj@intel.com \
    --cc=davem@davemloft.net \
    --cc=jeff@garzik.org \
    --cc=john.ronciak@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.