All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@adurom.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	"Rafał Miłecki" <zajec5@gmail.com>,
	linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org
Subject: Re: [PATCH] b43: HT-PHY: init: add missing small-tables writes
Date: Wed, 24 Aug 2011 20:56:52 +0300	[thread overview]
Message-ID: <87pqjuofq3.fsf@purkki.adurom.net> (raw)
In-Reply-To: <1314118360.21805.126.camel@shinybook.infradead.org> (David Woodhouse's message of "Tue\, 23 Aug 2011 17\:52\:38 +0100")

David Woodhouse <dwmw2@infradead.org> writes:

> On Tue, 2011-08-23 at 09:49 -0400, John W. Linville wrote:
>> Please, _please_, _PLEASE_ stop doing this.  I process a lot of
>> patches, and sometimes I will miss these directives.
>
> Best just to publish a git tree which John can pull in to
> wireless-testing.git, much as trees get pulled to linux-next.
>
> That way it'll *always* have the patches you want, in the order you
> want.

That's true, but setting up git tree for wireless is not trivial and
not for the faint of heart. Especially due to differences between
wireless-next and wireless-testing. Sending a patch series is a lot
easier and causes less tears.

-- 
Kalle Valo

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@adurom.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	"Rafał Miłecki" <zajec5@gmail.com>,
	linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org
Subject: [PATCH] b43: HT-PHY: init: add missing small-tables writes
Date: Wed, 24 Aug 2011 20:56:52 +0300	[thread overview]
Message-ID: <87pqjuofq3.fsf@purkki.adurom.net> (raw)
In-Reply-To: <1314118360.21805.126.camel@shinybook.infradead.org> (David Woodhouse's message of "Tue\, 23 Aug 2011 17\:52\:38 +0100")

David Woodhouse <dwmw2@infradead.org> writes:

> On Tue, 2011-08-23 at 09:49 -0400, John W. Linville wrote:
>> Please, _please_, _PLEASE_ stop doing this.  I process a lot of
>> patches, and sometimes I will miss these directives.
>
> Best just to publish a git tree which John can pull in to
> wireless-testing.git, much as trees get pulled to linux-next.
>
> That way it'll *always* have the patches you want, in the order you
> want.

That's true, but setting up git tree for wireless is not trivial and
not for the faint of heart. Especially due to differences between
wireless-next and wireless-testing. Sending a patch series is a lot
easier and causes less tears.

-- 
Kalle Valo

  reply	other threads:[~2011-08-24 17:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-13 15:54 [PATCH] b43: HT-PHY: init: add missing small-tables writes Rafał Miłecki
2011-08-13 15:54 ` Rafał Miłecki
2011-08-23 12:45 ` Rafał Miłecki
2011-08-23 12:45   ` Rafał Miłecki
2011-08-23 13:49   ` John W. Linville
2011-08-23 13:49     ` John W. Linville
2011-08-23 15:09     ` Rafał Miłecki
2011-08-23 15:09       ` Rafał Miłecki
2011-08-23 16:52     ` David Woodhouse
2011-08-23 16:52       ` David Woodhouse
2011-08-24 17:56       ` Kalle Valo [this message]
2011-08-24 17:56         ` Kalle Valo
2011-08-24 19:57         ` David Woodhouse
2011-08-24 19:57           ` David Woodhouse

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=87pqjuofq3.fsf@purkki.adurom.net \
    --to=kvalo@adurom.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=zajec5@gmail.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.