NAK: [SRU][X/raspi2] Support for the RaspberryPi 3 B Plus board

Kleber Souza kleber.souza at canonical.com
Fri Aug 24 10:50:50 UTC 2018


On 08/22/18 11:51, Paolo Pisati wrote:
> On Tue, Aug 21, 2018 at 5:56 PM, Kleber Souza
> <kleber.souza at canonical.com> wrote:
>>>       brcmfmac: Fix double free on exception at module load.
>>>       brcmfmac: only lock and unlock fws if fws is not null
>>>       brcmfmac: Fix warn trace on module unload while in ibss mode
>>>       brcmfmac: fix p2p scan abort null pointer exception
>>>       brcmf: Fix null pointer exception in bcdc_hdrpull
>>
>> These brcmf[mac] patches had the original authorship replaced.
> 
> Weird, i corrected the authorship and pushed again.
> 
>>>
>>> Phil Elwell (9):
>>>       BCM270X_DT: Add Pi 3+ dts files
>>>       lan78xx: Read MAC address from DT if present
>>>       lan78xx: Enable LEDs if no valid EEPROM or OTP
>>>       lan78xx: Read initial EEE status from DT
>>>       lan78xx: Change LEDs to include 10Mb activity
>>>       lan78xx: Read LED states from Device Tree
>>>       lan78xx: Ignore DT MAC address if already valid
>>>       lan78xx: Don't reset the interface on open
>>
>> The above patch doesn't have the s-o-b from the original author.
> 
> Actually, except for "lan78xx: Don't reset the interface on open"
> (that is following the raspberry patch[1] and doesn't have the SOB),
> all the others have the SOB line:
> 
> Signed-off-by: Phil Elwell <phil at raspberrypi.org>
> 
> 1: https://github.com/raspberrypi/linux/commit/4d926e896df045faecdbcf7b861ae339ee34be7d#diff-0781b8dc7b6ca178de61412444629675
> 

The patch provenance comes from mainline in this case with

(backported from commit 47b998653fea4ef69e3e89574956386f262bccca)

And the s-o-b block of this commit is

    Fixes: 92571a1aae40 ("lan78xx: Connect phy early")
    Signed-off-by: Phil Elwell <phil at raspberrypi.org>
    Signed-off-by: David S. Miller <davem at davemloft.net>

when we pull patches from mainline we expect that the block is kept as
is and further info added below it.

I can fix it when applying the patches.


Thanks.




More information about the kernel-team mailing list