linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Luis Correia <luis.f.correia@gmail.com>
Cc: "linux-wireless" <linux-wireless@vger.kernel.org>,
	rt2x00 Users List <users@rt2x00.serialmonkey.com>
Subject: Re: [PATCH] Remove MCU requests for SoC platforms
Date: Thu, 1 Apr 2010 14:51:43 +0200	[thread overview]
Message-ID: <201004011451.44204.IvDoorn@gmail.com> (raw)
In-Reply-To: <t2yefe7343f1004010548tdb2db0a3h9570da736a269352@mail.gmail.com>

Hi,

> @@ -1100,8 +1106,10 @@
>  	/*
>  	 * This device requires firmware and MCU access.
>  	 */

You manually edited your patch didn't you? :P
This doesn't apply since you changed the comment line.

Ivo


  reply	other threads:[~2010-04-01 12:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 12:48 [PATCH] Remove MCU requests for SoC platforms Luis Correia
2010-04-01 12:51 ` Ivo van Doorn [this message]
2010-04-01 12:58   ` [PATCH V2] " Luis Correia
2010-04-01 13:02     ` Ivo van Doorn
2010-04-01 20:16     ` Kalle Valo

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=201004011451.44204.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luis.f.correia@gmail.com \
    --cc=users@rt2x00.serialmonkey.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).