Thanks. I'm looking into that, but currently my system doesn't support 'git
send-email' and I'm researching why. My apologies for the noob spam,
I still have much to learn and mistakes to make. John has just pointed
me toward 'git am', which I also didn't know about. Thank you.
On 9 May 2016 at 13
On 2016-05-09 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
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 whe
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 m
On 2016-05-09 12:50, Graham Fairweather wrote:
> From: Graham Fairweather
>
> 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
From: Graham Fairweather
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'.
From: Graham Fairweather
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'.
From: Graham Fairweather
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. More info can be found at:
https://forum.openwrt.org/viewtopic.php?id=64621
https://github.com/Xotic750/openwrt/tree/f
From: Graham Fairweather
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. More info can be found at:
https://forum.openwrt.org/viewtopic.php?id=64621
https://github.com/Xotic750/openwrt/tree/f
From: Graham Fairweather
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. More info can be found at:
https://forum.openwrt.org/viewtopic.php?id=64621
https://github.com/Xotic750/openwrt/tree/f
From: Graham Fairweather
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. More info can be found at:
https://forum.openwrt.org/viewtopic.php?id=64621
https://github.com/Xotic750/openwrt/tree/f
11 matches
Mail list logo
