From: Arend van Spriel <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Hante Meuleman <meuleman@broadcom.com>,
Hauke Mehrtens <hauke@hauke-m.de>
Subject: Re: [PATCH RESEND] mips: bcm47xx: allow retrieval of complete nvram contents
Date: Wed, 20 May 2015 16:17:45 +0200 [thread overview]
Message-ID: <555C9789.9010709@broadcom.com> (raw)
In-Reply-To: <CACna6rw3ZgJSLrR=kNKDNgcLHz7-bZjaObv2zuTgmWWeUtLSUw@mail.gmail.com>
On 05/20/15 15:48, Rafał Miłecki wrote:
> On 20 May 2015 at 14:54, Arend van Spriel<arend@broadcom.com> wrote:
>> On 05/20/15 14:31, Rafał Miłecki wrote:
>>>
>>> On 20 May 2015 at 13:50, Arend van Spriel<arend@broadcom.com> wrote:
>>>>
>>>> From: Hante Meuleman<meuleman@broadcom.com>
>>>>
>>>> Host platforms such as routers supported by OpenWRT can
>>>> support NVRAM reading directly from internal NVRAM store.
>>>> The brcmfmac for one requires the complete nvram contents
>>>> to select what needs to be sent to wireless device.
>>>
>>>
>>> First of all, I have to ask you to rebase this patch on top of
>>> upstream-sfr. Mostly because of
>>> MIPS: BCM47XX: Make sure NVRAM buffer ends with \0
>>
>>
>> No idea what upstream-sfr is. I applied the patch on top of the master
>> branch of linux-mips repo [1]. What am I missing here?
>>
>> [1] http://git.linux-mips.org/cgit/ralf/linux.git
>
> Just go a dir higher and you'll find it :)
> http://git.linux-mips.org/cgit/
>
> Its a repo with mips-for-linux-next branch you're looking for.
Thanks. Found it.
Regards,
Arend
prev parent reply other threads:[~2015-05-20 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 11:50 [PATCH RESEND] mips: bcm47xx: allow retrieval of complete nvram contents Arend van Spriel
2015-05-20 11:50 ` Arend van Spriel
2015-05-20 12:31 ` Rafał Miłecki
2015-05-20 12:54 ` Arend van Spriel
2015-05-20 13:48 ` Rafał Miłecki
2015-05-20 14:17 ` Arend van Spriel [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=555C9789.9010709@broadcom.com \
--to=arend@broadcom.com \
--cc=hauke@hauke-m.de \
--cc=linux-mips@linux-mips.org \
--cc=linux-wireless@vger.kernel.org \
--cc=meuleman@broadcom.com \
--cc=ralf@linux-mips.org \
--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.