netdev - Re: [PATCH v2] net: macb: Handle HRESP error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Sat, 27 Jan 2018 10:33:57 +0530
From:   Harini Katakam <harinikatakamlinux@...il.com>
To:     David Miller <davem@...emloft.net>
Cc:     Harini Katakam <harini.katakam@...inx.com>,
        Nicolas Ferre <nicolas.ferre@...el.com>,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        michals@...inx.com, Michal Simek <michal.simek@...inx.com>
Subject: Re: [PATCH v2] net: macb: Handle HRESP error

Hi David,

On Fri, Jan 26, 2018 at 9:25 PM, David Miller <davem@...emloft.net> wrote:
> From: Harini Katakam <harini.katakam@...inx.com>
> Date: Fri, 26 Jan 2018 16:12:11 +0530
>
>> From: Harini Katakam <harini.katakam@...inx.com>
>>
>> Handle HRESP error by doing a SW reset of RX and TX and
>> re-initializing the descriptors, RX and TX queue pointers.
>>
>> Signed-off-by: Harini Katakam <harinik@...inx.com>
>> Signed-off-by: Michal Simek <michal.simek@...inx.com>
>> ---
>> v2:
>> Rebased on top of latest net-next and reinitialized
>> all rx queues.
>
> Your patch was corrupted by your email client, it changed TAB characters
> into sequences of SPACES amongst other things.  We cannot integrate your
> changes until you fix this.

I'll fix this.

>
>> This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
>
> This is also completely inappropriate for a public development list and
> you must eliminate this signature on future postings or we will have to
> ignore them.

Sorry, I usually remove this, missed it this time.
Will resend.

Regards,
Harini