All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Fengguang Wu <lkp@intel.com>, Kalle Valo <kvalo@codeaurora.org>
Cc: Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
	kbuild-all@01.org, linux-wireless@vger.kernel.org,
	David Spinadel <david.spinadel@intel.com>,
	"Ye, Xiaolong" <xiaolong.ye@intel.com>
Subject: Re: [PATCH] mac80211_hwsim: Set global RRM capability
Date: Fri, 26 Feb 2016 10:47:54 +0100	[thread overview]
Message-ID: <1456480074.5284.0.camel@sipsolutions.net> (raw)
In-Reply-To: <20160226081836.GA6470@wfg-t540p.sh.intel.com>

On Fri, 2016-02-26 at 16:18 +0800, Fengguang Wu wrote:
> 
> > I think this build failure is because mac80211_hwsim is an
> > exception to
> > other wireless drivers and is applied via mac80211-next. Should we
> > add
> > an entry for mac80211_hwsim to MAINTAINERS with the correct git
> > tree? I
> > think kbuild test robot follows MAINTAINERS file nowdays (or at
> > least I
> > understood that's the plan).
> 
> That's right. The robot parses MAINTAINERS when judging which tree
> to apply LKML patches to.
> 

Great. I'll add a commit to make mac80211_hwsim just part of the
MAC80211 entry.

johannes

  reply	other threads:[~2016-02-26  9:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25  9:24 [PATCH] mac80211_hwsim: Set global RRM capability Emmanuel Grumbach
2016-02-25 10:01 ` kbuild test robot
2016-02-26  7:17   ` Kalle Valo
2016-02-26  8:18     ` Fengguang Wu
2016-02-26  9:47       ` Johannes Berg [this message]
2016-03-02 12:24 ` Johannes Berg
2016-03-02 12:36   ` Grumbach, Emmanuel
2016-03-03 15:45     ` Johannes Berg
2016-03-04  5:39       ` Grumbach, Emmanuel

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=1456480074.5284.0.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=david.spinadel@intel.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=kbuild-all@01.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=xiaolong.ye@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.