[OpenWrt-Devel] [PATCHv2 001/001] [brcm63xx] Display the correct detected CPU ID
john at phrozen.org
Mon May 9 07:21:52 EDT 2016
On 09/05/2016 13:19, Graham Fairweather wrote:
> It wasn't my intention to spam the list. I asked for help on the
> forum, I asked for help on IRC and I was told to try things. The
> documents say if unsuccessful then try again. As a noob, it is not the
> easiest process to follow, especially when something doesn't work. How
> would sending the mail to myself, which I did by the way, help me
> knowing what the problem was? Thanks for your patience and your
no worries, we all started doing this at some point. once you have the
patch and send it to yourslef, you can save the email and try it out on
your local tree. if all went well, you should be able to ally the
mail/patch with "git am mypatch.eml"
the easiest way to make sure that sending the patch always works is to
use "git send-email"
> On 9 May 2016 at 12:54, Felix Fietkau <nbd at nbd.name> wrote:
>> On 2016-05-09 12:50, Graham Fairweather wrote:
>>> From: Graham Fairweather <xotic750 at gmail.com>
>>> This patch fixes the logged detected CPU ID when an equivalent is used,
>>> like in the case where we have a bcm6369 and configuration for a
>>> bcm6368 is used.
>>> So, it will display 'Detected Broadcom 0x6369 CPU revision b2' instead of
>>> 'Detected Broadcom 0x6369 CPU revision b2'. More info can be found at:
>>> Signed-off-by: Graham Fairweather <xotic750 at gmail.com>
>> Please stop spamming the list with the same patch over and over again.
>> While you're still trying to figure out how to send patches properly,
>> please send them to yourself instead of the list.
>> - Felix
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
More information about the openwrt-devel