[U-Boot] [PATCH 00/10] This patch set represent Marvell mvpp2 driver fixes

[Stefan Roese]

Hi Joe,

On 09.08.2017 17:24, Joe Hershberger wrote:
> On Wed, Aug 9, 2017 at 12:56 AM, Stefan Roese <sr at denx.de> wrote:
>> Hi Joe,
>>
>> On 08.08.2017 17:57, Joe Hershberger wrote:
>>>
>>> Hi Stefan (and Stefan),
>>>
>>> On Tue, Aug 8, 2017 at 7:05 AM, Stefan Roese <sr at denx.de> wrote:
>>>>
>>>> Hi Joe,
>>>>
>>>> On 11.07.2017 10:04, Stefan Roese wrote:
>>>>>
>>>>>
>>>>> On 21.06.2017 10:31, stefanc at malvell.com wrote:
>>>
>>>
>>> Huh? Sent from a typo email address?
>>
>>
>> Where is the problem with the Stefan Chulski's email address?
>> Sorry, I can't spot it.
> 
> Just above and in the reply-to of the messages: stefanc at ma>l<vell.com

Ah, thanks.

>>> That's pretty tedious. I
>>> recommend fixing your git config. And if that's fine, I recommend
>>> using patman so this won't happen again.
>>>
>>>>>>
>>>>>> From: Stefan Chulski <stefanc at marvell.com>
>>>>>>
>>>>>> Issues were found during internal QA phase.
>>>>>>
>>>>>> Stefan Chulski (10):
>>>>>>      net: mvpp2x: Add GPIO configuration support
>>>>>>      net: mvpp2x: fix phy connected to wrong mdio issue
>>>>>>      net: mvpp2x: Enable GoP packet padding in TX
>>>>>>      net: mvpp2x: fix BM configuration overrun issue
>>>>>>      net: mvpp2x: decrease size of AGGR_TXQ and CPU_DESC_CHUNK
>>>>>>      net: mvpp2x: remove MBUS configurations from MvPP22 driver
>>>>>>      net: mvpp2x: Remove IRQ configuration from u-boot
>>>>>>      net: mvpp2x: Set BM pool high address
>>>>>>      net: mvpp2x: remove TX drain from transmit routine
>>>>>>      net: mvpp2x: Set BM poll size once during priv probe
>>>>>>
>>>>>>     drivers/net/mvpp2.c | 189
>>>>>> ++++++++++++++++++++++++++--------------------------
>>>>>>     1 file changed, 94 insertions(+), 95 deletions(-)
>>>>>
>>>>>
>>>>>
>>>>> Joe, do you have any comments on these mvpp2 patches?
>>>>
>>>>
>>>>
>>>> Gently ping on these patches again. Joe, do you have any comments
>>>> on these? Do you want to take these patches via your tree? Or
>>>> should I push them if you don't have any objections?
>>>
>>>
>>> Reviewing now. I generally use patchwork to remember what I have to
>>> do. I guess if I didn't rely on that I would set up better work queue
>>> email filters. Sorry for the delay.
>>>
>>> I figured since the series is assigned to you in PW, that you wanted
>>> it through your tree. I'm fine either way.
>>
>>
>> I assume that Tom assigned them to me (I didn't do it at least).
>> But I can definitely pull these patches via the Marvell tree, once
>> all open issues are resolved and all patches have your Acked-by
>> tag.
> 
> Sounds good!

Great. I'm build testing right now and will send the pull request, once
this has finished without any issues.

Thanks,
Stefan