From: Kalle Valo <kvalo@codeaurora.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Priit Laes <plaes@plaes.org>,
arnd@arndb.de, Arend Van Spriel <arend.vanspriel@broadcom.com>,
Jonas Gorski <jonas.gorski@gmail.com>,
"John W . Linville" <linville@tuxdriver.com>,
Arend van Spriel <arend@broadcom.com>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Chen-Yu Tsai <wens@csie.org>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
"linux-arm-kernel\@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
devicetree <devicetree@vger.kernel.org>,
linux-sunxi@googlegroups.com
Subject: Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property
Date: Thu, 30 Jun 2016 12:58:14 +0300 [thread overview]
Message-ID: <87a8i36ls9.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <e94f58fe-f709-94bd-21f6-144c4e038d17@redhat.com> (Hans de Goede's message of "Thu, 30 Jun 2016 11:50:01 +0200")
Hans de Goede <hdegoede@redhat.com> writes:
> Hi,
>
> On 30-06-16 11:02, Kalle Valo wrote:
>> Priit Laes <plaes@plaes.org> writes:
>>
>>>> What is the size of this nvram file? As it's board specific, I wonder
>>>> if we can simply include it inside of the DT verbatim. I remember
>>>> doing that (in the pre-dtb days, on real open firmware) for the
>>>> "spidernet"
>>>> ethernet driver.
>>>
>>> It contains a bit too much info:
>>>
>>> This is what CubieTruck requires:
>>>
>>> http://dl.cubieboard.org/public/Cubieboard/benn/firmware/ap6210/nvram_ap6210.txt
>>
>> In the nvram file I see lots of identifiers:
>>
>> manfid=0x2d0
>> prodid=0x492
>> vendid=0x14e4
>> devid=0x4343
>> boardtype=0x0598
>> boardrev=0x1307
>> boardnum=777
>>
>> Are any of these (or a combination of them) unique for each board type?
>> What if one of these is provided through DT and then the driver could
>> choose the nvram file based on the board id? Just another idea...
>
> That would require updating a table in the driver every time a new
> board comes out, I do not believe that that is a good solution.
You don't necessarily need to have a table in the driver if you embed
the id to the filename, for example something like this:
nvram-0598-1307.txt
nvram-<boardtype>-<boardrev>.txt
--
Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: kvalo@codeaurora.org (Kalle Valo)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name dt property
Date: Thu, 30 Jun 2016 12:58:14 +0300 [thread overview]
Message-ID: <87a8i36ls9.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <e94f58fe-f709-94bd-21f6-144c4e038d17@redhat.com> (Hans de Goede's message of "Thu, 30 Jun 2016 11:50:01 +0200")
Hans de Goede <hdegoede@redhat.com> writes:
> Hi,
>
> On 30-06-16 11:02, Kalle Valo wrote:
>> Priit Laes <plaes@plaes.org> writes:
>>
>>>> What is the size of this nvram file? As it's board specific, I wonder
>>>> if we can simply include it inside of the DT verbatim. I remember
>>>> doing that (in the pre-dtb days, on real open firmware) for the
>>>> "spidernet"
>>>> ethernet driver.
>>>
>>> It contains a bit too much info:
>>>
>>> This is what CubieTruck requires:
>>>
>>> http://dl.cubieboard.org/public/Cubieboard/benn/firmware/ap6210/nvram_ap6210.txt
>>
>> In the nvram file I see lots of identifiers:
>>
>> manfid=0x2d0
>> prodid=0x492
>> vendid=0x14e4
>> devid=0x4343
>> boardtype=0x0598
>> boardrev=0x1307
>> boardnum=777
>>
>> Are any of these (or a combination of them) unique for each board type?
>> What if one of these is provided through DT and then the driver could
>> choose the nvram file based on the board id? Just another idea...
>
> That would require updating a table in the driver every time a new
> board comes out, I do not believe that that is a good solution.
You don't necessarily need to have a table in the driver if you embed
the id to the filename, for example something like this:
nvram-0598-1307.txt
nvram-<boardtype>-<boardrev>.txt
--
Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Priit Laes <plaes-q/aMd4JkU83YtjvyW6yDsg@public.gmane.org>,
arnd-r2nGTMty4D4@public.gmane.org,
Arend Van Spriel
<arend.vanspriel-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
Jonas Gorski
<jonas.gorski-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"John W . Linville"
<linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
Arend van Spriel <arend-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
Maxime Ripard
<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>,
"linux-wireless@vger.kernel.org"
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property
Date: Thu, 30 Jun 2016 12:58:14 +0300 [thread overview]
Message-ID: <87a8i36ls9.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <e94f58fe-f709-94bd-21f6-144c4e038d17-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> (Hans de Goede's message of "Thu, 30 Jun 2016 11:50:01 +0200")
Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> writes:
> Hi,
>
> On 30-06-16 11:02, Kalle Valo wrote:
>> Priit Laes <plaes-q/aMd4JkU83YtjvyW6yDsg@public.gmane.org> writes:
>>
>>>> What is the size of this nvram file? As it's board specific, I wonder
>>>> if we can simply include it inside of the DT verbatim. I remember
>>>> doing that (in the pre-dtb days, on real open firmware) for the
>>>> "spidernet"
>>>> ethernet driver.
>>>
>>> It contains a bit too much info:
>>>
>>> This is what CubieTruck requires:
>>>
>>> http://dl.cubieboard.org/public/Cubieboard/benn/firmware/ap6210/nvram_ap6210.txt
>>
>> In the nvram file I see lots of identifiers:
>>
>> manfid=0x2d0
>> prodid=0x492
>> vendid=0x14e4
>> devid=0x4343
>> boardtype=0x0598
>> boardrev=0x1307
>> boardnum=777
>>
>> Are any of these (or a combination of them) unique for each board type?
>> What if one of these is provided through DT and then the driver could
>> choose the nvram file based on the board id? Just another idea...
>
> That would require updating a table in the driver every time a new
> board comes out, I do not believe that that is a good solution.
You don't necessarily need to have a table in the driver if you embed
the id to the filename, for example something like this:
nvram-0598-1307.txt
nvram-<boardtype>-<boardrev>.txt
--
Kalle Valo
next prev parent reply other threads:[~2016-06-30 10:05 UTC|newest]
Thread overview: 151+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 14:04 [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property Hans de Goede
2016-06-29 14:04 ` Hans de Goede
2016-06-29 14:04 ` Hans de Goede
2016-06-29 14:04 ` [PATCH 2/4] ARM: dts: sun7i-a20-cubietruck: Set brcm,nvram_file_name Hans de Goede
2016-06-29 14:04 ` Hans de Goede
2016-06-29 14:04 ` Hans de Goede
2016-06-29 17:01 ` Kalle Valo
2016-06-29 17:01 ` Kalle Valo
2016-06-29 17:01 ` [PATCH 2/4] ARM: dts: sun7i-a20-cubietruck: Set brcm, nvram_file_name Kalle Valo
2016-06-29 18:01 ` [linux-sunxi] Re: [PATCH 2/4] ARM: dts: sun7i-a20-cubietruck: Set brcm,nvram_file_name Hans de Goede
2016-06-29 18:01 ` Hans de Goede
2016-06-29 18:01 ` Hans de Goede
2016-06-29 14:04 ` [PATCH 3/4] ARM: dts: sun7i-a20-wits-pro-a20-dkt: " Hans de Goede
2016-06-29 14:04 ` Hans de Goede
2016-06-29 14:04 ` [PATCH 3/4] ARM: dts: sun7i-a20-wits-pro-a20-dkt: Set brcm, nvram_file_name Hans de Goede
2016-06-29 14:04 ` [PATCH 4/4] ARM: dts: sun5i-a10s-auxtek-t004: Set brcm,nvram_file_name Hans de Goede
2016-06-29 14:04 ` Hans de Goede
2016-06-29 14:04 ` [PATCH 4/4] ARM: dts: sun5i-a10s-auxtek-t004: Set brcm, nvram_file_name Hans de Goede
2016-06-29 14:42 ` [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property Jonas Gorski
2016-06-29 14:42 ` Jonas Gorski
2016-06-29 14:42 ` Jonas Gorski
2016-06-29 15:16 ` Hans de Goede
2016-06-29 15:16 ` Hans de Goede
2016-06-29 15:16 ` Hans de Goede
2016-06-29 17:00 ` Kalle Valo
2016-06-29 17:00 ` Kalle Valo
2016-06-29 17:00 ` Kalle Valo
2016-06-29 18:01 ` [linux-sunxi] " Hans de Goede
2016-06-29 18:01 ` Hans de Goede
2016-06-29 18:01 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Hans de Goede
2016-06-29 18:51 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arend Van Spriel
2016-06-29 18:51 ` 'Arend Van Spriel' via linux-sunxi
2016-06-29 18:51 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arend Van Spriel
2016-06-29 18:57 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arend Van Spriel
2016-06-29 18:57 ` 'Arend Van Spriel' via linux-sunxi
2016-06-29 18:57 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arend Van Spriel
2016-06-30 8:50 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Kalle Valo
2016-06-30 8:50 ` Kalle Valo
2016-06-30 8:50 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Kalle Valo
2016-06-29 19:33 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arnd Bergmann
2016-06-29 19:33 ` Arnd Bergmann
2016-06-29 19:33 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arnd Bergmann
2016-06-29 19:54 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Priit Laes
2016-06-29 19:54 ` Priit Laes
2016-06-29 19:54 ` [linux-sunxi] " Priit Laes
2016-06-29 20:07 ` Arnd Bergmann
2016-06-29 20:07 ` Arnd Bergmann
2016-06-29 20:07 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arnd Bergmann
2016-06-30 9:02 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Kalle Valo
2016-06-30 9:02 ` Kalle Valo
2016-06-30 9:02 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Kalle Valo
2016-06-30 9:50 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Hans de Goede
2016-06-30 9:50 ` Hans de Goede
2016-06-30 9:50 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Hans de Goede
2016-06-30 9:58 ` Kalle Valo [this message]
2016-06-30 9:58 ` Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Kalle Valo
2016-06-30 9:58 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Kalle Valo
2016-06-30 10:04 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Hans de Goede
2016-06-30 10:04 ` Hans de Goede
2016-06-30 10:04 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Hans de Goede
2016-06-30 10:18 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Jonas Gorski
2016-06-30 10:18 ` Jonas Gorski
2016-06-30 10:18 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Jonas Gorski
2016-06-30 10:25 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Hans de Goede
2016-06-30 10:25 ` Hans de Goede
2016-06-30 10:25 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Hans de Goede
2016-06-30 11:31 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arnd Bergmann
2016-06-30 11:31 ` Arnd Bergmann
2016-06-30 11:31 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arnd Bergmann
2016-06-30 19:23 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arend Van Spriel
2016-06-30 19:23 ` 'Arend Van Spriel' via linux-sunxi
2016-06-30 19:23 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arend Van Spriel
2016-07-01 8:51 ` Arnd Bergmann
2016-07-01 8:51 ` Arnd Bergmann
2016-07-01 8:51 ` [linux-sunxi] " Arnd Bergmann
2016-07-01 8:58 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Jonas Gorski
2016-07-01 8:58 ` Jonas Gorski
2016-07-01 8:58 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Jonas Gorski
2016-07-02 6:59 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Kalle Valo
2016-07-02 6:59 ` Kalle Valo
2016-07-02 6:59 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Kalle Valo
2016-07-02 18:20 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arend Van Spriel
2016-07-02 18:20 ` 'Arend Van Spriel' via linux-sunxi
2016-07-02 18:20 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arend Van Spriel
2016-07-02 21:30 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arnd Bergmann
2016-07-02 21:30 ` Arnd Bergmann
2016-07-02 21:30 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arnd Bergmann
2016-07-04 8:41 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arend Van Spriel
2016-07-04 8:41 ` Arend Van Spriel
2016-07-04 8:41 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arend Van Spriel
2016-07-04 8:55 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arnd Bergmann
2016-07-04 8:55 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arnd Bergmann
2016-07-04 8:55 ` Arnd Bergmann
2016-07-04 9:08 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arend Van Spriel
2016-07-04 9:08 ` 'Arend Van Spriel' via linux-sunxi
2016-07-04 9:08 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arend Van Spriel
2016-07-04 14:54 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arnd Bergmann
2016-07-04 14:54 ` Arnd Bergmann
2016-07-04 14:54 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arnd Bergmann
2016-07-04 18:36 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arend van Spriel
2016-07-04 18:36 ` 'Arend van Spriel' via linux-sunxi
2016-07-04 18:36 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arend van Spriel
2016-07-05 13:43 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arnd Bergmann
2016-07-05 13:43 ` Arnd Bergmann
2016-07-05 13:43 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arnd Bergmann
2016-07-06 8:08 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arend Van Spriel
2016-07-06 8:08 ` 'Arend Van Spriel' via linux-sunxi
2016-07-06 8:08 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arend Van Spriel
2016-07-06 13:42 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arnd Bergmann
2016-07-06 13:42 ` Arnd Bergmann
2016-07-06 13:42 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arnd Bergmann
2016-07-06 19:19 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arend Van Spriel
2016-07-06 19:19 ` 'Arend Van Spriel' via linux-sunxi
2016-07-06 19:19 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arend Van Spriel
2016-07-07 8:46 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arnd Bergmann
2016-07-07 8:46 ` Arnd Bergmann
2016-07-07 8:46 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arnd Bergmann
2016-07-07 9:16 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arend Van Spriel
2016-07-07 9:16 ` 'Arend Van Spriel' via linux-sunxi
2016-07-07 9:16 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arend Van Spriel
2016-07-07 9:24 ` Arnd Bergmann
2016-07-07 9:24 ` Arnd Bergmann
2016-07-07 9:24 ` [linux-sunxi] " Arnd Bergmann
2016-07-17 21:45 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Rob Herring
2016-07-17 21:45 ` Rob Herring
2016-07-17 21:45 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Rob Herring
2016-07-18 7:51 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Arend Van Spriel
2016-07-18 7:51 ` 'Arend Van Spriel' via linux-sunxi
2016-07-18 7:51 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arend Van Spriel
2016-06-30 8:46 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Kalle Valo
2016-06-30 8:46 ` Kalle Valo
2016-06-30 8:46 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Kalle Valo
[not found] ` <87mvm36p4d.fsf-HodKDYzPHsUD5k0oWYwrnHL1okKdlPRT@public.gmane.org>
2016-06-30 9:33 ` Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Julian Calaby
2016-06-30 9:49 ` [linux-sunxi] " Hans de Goede
2016-06-30 9:49 ` Hans de Goede
2016-06-30 9:49 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Hans de Goede
2016-06-30 9:53 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Hans de Goede
2016-06-30 9:53 ` Hans de Goede
2016-06-30 9:53 ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Hans de Goede
2016-07-01 2:08 ` [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Rob Herring
2016-07-01 2:08 ` Rob Herring
2016-07-01 2:08 ` Rob Herring
2016-07-01 8:17 ` Arend Van Spriel
2016-07-01 8:17 ` 'Arend Van Spriel' via linux-sunxi
2016-07-01 8:17 ` Arend Van Spriel
2016-07-01 9:20 ` Arnd Bergmann
2016-07-01 9:20 ` Arnd Bergmann
2016-07-01 9:20 ` Arnd Bergmann
2016-07-04 16:12 ` Rob Herring
2016-07-04 16:12 ` Rob Herring
2016-07-04 16:12 ` Rob Herring
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=87a8i36ls9.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=arend@broadcom.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=jonas.gorski@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sunxi@googlegroups.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=maxime.ripard@free-electrons.com \
--cc=plaes@plaes.org \
--cc=wens@csie.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.