All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	Zhu Yi <yi.zhu@intel.com>, Tomas Winkler <tomasw@gmail.com>,
	Tomas Winkler <tomas.winkler@intel.com>,
	Nick Kossifidis <mickflemm@gmail.com>,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	Felix Fietkau <nbd@openwrt.org>
Subject: Re: [PATCH 0/5] mac80211, iwlwifi, ath9k: Fix rate scaling for IEEE80211_TX_CTL_NO_ACK packets
Date: Thu, 30 Apr 2009 15:02:07 -0400	[thread overview]
Message-ID: <20090430190207.GD9323@tuxdriver.com> (raw)
In-Reply-To: <20090430182806.GA9323@tuxdriver.com>

On Thu, Apr 30, 2009 at 02:28:07PM -0400, John W. Linville wrote:
> On Tue, Apr 28, 2009 at 10:53:51PM +0200, G=E1bor Stefanik wrote:
> > Did this get lost? I can't see it in wireless-testing.
>=20
> No, I didn't lose them.  I was waiting to process them until I had
> a little extra time, because nearly every patch you send me requires
> manually intervention before I can apply it.  This is quite painful
> and it increases the time I need for merging patches exponentially.
>=20
> Please, please, please ensure that:
>=20
> 	-- you are using a recent pull of wireless-testing;
>=20
> 	-- you're patches are based directly on wireless-testing and
> 	   not on top of any other patches you have not submitted;
>=20
> 	-- you format your patch and changelog compatibly with what
> 	   is described here:
>=20
> 		http://linux.yyz.us/patch-format.html
>=20
> 	-- you send the patch inline (without MIME) in email if at
> 	   all possible;
>=20
> 	-- if you simply must send a patch as an attachment then do
> 	   so, but...
>=20
> 	-- do _not_ send a patch inline _and_ attached to the same
> 	   email

=46orgot one:

	-- successfully compile a current wireless-testing tree with
	   your patches applied...

>=20
> The above are not strictly directed at you, G=E1bor.

That one is...

John
--=20
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-04-30 19:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 17:35 [PATCH 0/5] mac80211, iwlwifi, ath9k: Fix rate scaling for IEEE80211_TX_CTL_NO_ACK packets Gábor Stefanik
2009-04-23 18:09 ` Jouni Malinen
2009-04-23 18:18   ` Gábor Stefanik
2009-04-24 17:31   ` Felix Fietkau
2009-04-25  7:12     ` Johannes Berg
2009-04-28 20:53 ` Gábor Stefanik
2009-04-30 18:28   ` John W. Linville
2009-04-30 19:02     ` John W. Linville [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=20090430190207.GD9323@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    --cc=mcgrof@gmail.com \
    --cc=mickflemm@gmail.com \
    --cc=nbd@openwrt.org \
    --cc=netrolller.3d@gmail.com \
    --cc=tomas.winkler@intel.com \
    --cc=tomasw@gmail.com \
    --cc=yi.zhu@intel.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 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.