linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com,
	Linus Walleij <linus.walleij@linaro.org>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>,
	"Hauke Mehrtens" <hauke@hauke-m.de>
Subject: Re: [PATCH] firmware/nvram: bcm47xx: support init from IO memory
Date: Wed,  9 Nov 2022 10:27:11 -0800	[thread overview]
Message-ID: <20221109182711.879969-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <20221103082529.359084-1-linus.walleij@linaro.org>

On Thu,  3 Nov 2022 09:25:29 +0100, Linus Walleij <linus.walleij@linaro.org> wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
> 
> Provide NVMEM content to the NVRAM driver from a simple
> memory resource. This is necessary to use NVRAM in a memory-
> mapped flash device. Patch taken from OpenWrts development
> tree.
> 
> This patch makes it possible to use memory-mapped NVRAM
> on the D-Link DWL-8610AP and the D-Link DIR-890L.
> 
> Cc: Hauke Mehrtens <hauke@hauke-m.de>
> Cc: linux-mips@vger.kernel.org
> Cc: Florian Fainelli <f.fainelli@gmail.com>
> Cc: bcm-kernel-feedback-list@broadcom.com
> Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> [Added an export for modules potentially using the init symbol]
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---

Applied to https://github.com/Broadcom/stblinux/commits/drivers/next, thanks!
--
Florian

      reply	other threads:[~2022-11-09 18:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03  8:25 [PATCH] firmware/nvram: bcm47xx: support init from IO memory Linus Walleij
2022-11-09 18:27 ` Florian Fainelli [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=20221109182711.879969-1-f.fainelli@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=hauke@hauke-m.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=rafal@milecki.pl \
    --cc=tsbogend@alpha.franken.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).