All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Andrew Clausen <andrew.p.clausen@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rfkill: parameters documentation
Date: Tue, 06 Jan 2015 11:10:19 +0100	[thread overview]
Message-ID: <1420539019.1966.7.camel@sipsolutions.net> (raw)
In-Reply-To: <CAAXZBWJD02F81gJkhvLFZcpCzJahr-qsUUgbqheUfrc_BP0CjA@mail.gmail.com> (sfid-20150105_110329_183833_77EE0F7B)

On Mon, 2015-01-05 at 10:03 +0000, Andrew Clausen wrote:
> Hi Johannes,
> 
> On 5 January 2015 at 09:24, Johannes Berg <johannes@sipsolutions.net> wrote:
> > Looks fine to me (though the commit message shouldn't contain the email
> > "boilerplate" of "hi all" etc - should just be
> 
> Ah, sorry for the extra noise.
> 
> > However I'm not sure I should apply this through my tree?
> 
> I think you're right -- it makes sense to put it in your tree, and
> merge it down the track.  (I don't think I've submitted a kernel patch
> since pre-git days, so sorry for the confusion.)

I'll take it.

However, please resend with an adjust commit message, and please diff it
against my mac80211-next tree (it doesn't apply as is)

johannes


  reply	other threads:[~2015-01-06 10:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-02 19:01 [PATCH] rfkill: parameters documentation Andrew Clausen
2015-01-05  9:24 ` Johannes Berg
2015-01-05 10:03   ` Andrew Clausen
2015-01-06 10:10     ` Johannes Berg [this message]
2015-01-09 22:21 ` 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=1420539019.1966.7.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=akpm@linux-foundation.org \
    --cc=andrew.p.clausen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.