Linux wireless drivers development
 help / color / mirror / Atom feed
From: Sujith <Sujith.Manoharan@atheros.com>
To: "linville@tuxdriver.com" <linville@tuxdriver.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Jouni Malinen <Jouni.Malinen@Atheros.com>,
	Luis Rodriguez <Luis.Rodriguez@Atheros.com>
Subject: [PATCH 2/4] ath9k: Fix endiannes of EEPROM header
Date: Mon, 16 Feb 2009 14:32:59 +0530	[thread overview]
Message-ID: <18841.11203.428563.728384@gargle.gargle.HOWL> (raw)
In-Reply-To: <18841.7130.956050.285308@gargle.gargle.HOWL>

Sujith Manoharan wrote:
> This patch fixes an endian-related issue when
> reading the EEPROM header.
> 

John,

Please drop this patch, will send a proper fix later.
The other 3 patches in the series can be applied. Thanks.

Sujith

      reply	other threads:[~2009-02-16  9:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16  7:55 [PATCH 2/4] ath9k: Fix endiannes of EEPROM header Sujith
2009-02-16  9:02 ` Sujith [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=18841.11203.428563.728384@gargle.gargle.HOWL \
    --to=sujith.manoharan@atheros.com \
    --cc=Jouni.Malinen@Atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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