All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>,
	Hauke Mehrtens <hauke@hauke-m.de>,
	"Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: <backports@vger.kernel.org>
Subject: Re: [PATCH] patches: fix path in name_assign_type patch
Date: Mon, 7 Dec 2015 10:06:10 +0100	[thread overview]
Message-ID: <56654C02.8010005@broadcom.com> (raw)
In-Reply-To: <1449478931.4040.1.camel@sipsolutions.net>

On 12/07/2015 10:02 AM, Johannes Berg wrote:
> On Mon, 2015-12-07 at 10:00 +0100, Arend van Spriel wrote:
>>
>>>> drivers/net/wireless/broadcom/
>
>> drivers/net/wireless/broadcom/Kconfig
>> drivers/net/wireless/broadcom/Makefile
>> drivers/net/wireless/broadcom/b43
>> drivers/net/wireless/broadcom/b43legacy
>> drivers/net/wireless/broadcom/brcm80211
>>
>> Or (as Hauke suggests):
>>
>> drivers/net/wireless/broadcom/
>>
>> To restrict the copy-list the first option would be preferred.
>>
>
> Oh, you meant for the copy-list?
>
> I thought upstream backports just shipped a single copy-list line
> "ddrivers/net/wireless/"?

Nope. It is:

# 802.11
drivers/net/wireless/Kconfig
drivers/net/wireless/Makefile

It looks for subfolders and modifies the Kconfig and Makefile for the 
ones missing (comment out).

Regards,
Arend

> johannes
>

--
To unsubscribe from this list: send the line "unsubscribe backports" in

  reply	other threads:[~2015-12-07  9:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 11:53 [PATCH] patches: fix path in name_assign_type patch Arend van Spriel
2015-12-05 20:14 ` Hauke Mehrtens
2015-12-06 14:37   ` Johannes Berg
2015-12-07  9:00     ` Arend van Spriel
2015-12-07  9:02       ` Johannes Berg
2015-12-07  9:06         ` Arend van Spriel [this message]
2015-12-09 22:57           ` Hauke Mehrtens
2015-12-09 23:08             ` Johannes Berg
2015-12-07  8:55   ` Arend van Spriel

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=56654C02.8010005@broadcom.com \
    --to=arend@broadcom.com \
    --cc=backports@vger.kernel.org \
    --cc=hauke@hauke-m.de \
    --cc=johannes@sipsolutions.net \
    --cc=mcgrof@kernel.org \
    /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.