linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 3.5] iwlwifi: use correct supported firmware for 6035 and 6000g2
Date: Tue, 05 Jun 2012 20:21:01 +0200	[thread overview]
Message-ID: <1338920461.4514.50.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1338904477.4514.46.camel@jlt3.sipsolutions.net> (sfid-20120605_155441_808766_F14DC0C8)

On Tue, 2012-06-05 at 15:54 +0200, Johannes Berg wrote:
> From: Meenakshi Venkataraman <meenakshi.venkataraman@intel.com>
> 
> My patch
> 
>    iwlwifi: use correct released ucode version

Clearly not my day today, scratch this, I need to resend it.

johannes


  reply	other threads:[~2012-06-05 18:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05 13:54 [PATCH 3.5] iwlwifi: use correct supported firmware for 6035 and 6000g2 Johannes Berg
2012-06-05 18:21 ` Johannes Berg [this message]
2012-06-05 18:24 ` [PATCH 3.5 v2] " Johannes Berg

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=1338920461.4514.50.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --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;
as well as URLs for NNTP newsgroup(s).