[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACna6rzZufOWrztGE+W=RnsewVa4izxyuimgVx=FkE4weiZ1-A@mail.gmail.com>
Date: Mon, 27 Feb 2017 23:54:38 +0100
From: Rafał Miłecki <zajec5@...il.com>
To: Alban <albeu@...e.fr>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Boris Brezillon <boris.brezillon@...e-electrons.com>,
Richard Weinberger <richard@....at>,
Marek Vasut <marek.vasut@...il.com>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Cyrille Pitchen <cyrille.pitchen@...el.com>,
Brian Norris <computersforpeace@...il.com>,
David Woodhouse <dwmw2@...radead.org>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>
Subject: Re: [PATCH 3/3] ath9k: ahb: Add OF support
On 27 February 2017 at 23:48, Alban <albeu@...e.fr> wrote:
> On Mon, 27 Feb 2017 22:13:21 +0100
> Rafał Miłecki <zajec5@...il.com> wrote:
>
>> Why you didn't cc linux-wireless?!?!
>
> I first wanted to be sure that the devdata part was generally
> acceptable, this patch was just included as an example of a user.
> But it sound like that part will have to move to nvmem first.
> I'll come back with a new patch once MTD support for nvmem is
> done.
OK, I just realized this was supposed to be RFC (for some reason this
patch didn't include RFC tag). At least this is was I assume to by
looking at the:
[RFC 0/3] drivers: Add an API to read device specific config data
Good luck!
Powered by blists - more mailing lists