linux-kernel - Re: [PATCH 3/4] serial: 8250_lpss: Use 16B DMA burst with Elkhart Lake

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <Y2juIETKUZtw9wu6@smile.fi.intel.com>
Date:   Mon, 7 Nov 2022 13:38:08 +0200
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Jiri Slaby <jirislaby@...nel.org>,
        linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org,
        stable@...r.kernel.org, Wentong Wu <wentong.wu@...el.com>,
        Srikanth Thokala <srikanth.thokala@...el.com>,
        Aman Kumar <aman.kumar@...el.com>
Subject: Re: [PATCH 3/4] serial: 8250_lpss: Use 16B DMA burst with Elkhart
 Lake

On Mon, Nov 07, 2022 at 01:07:07PM +0200, Ilpo Järvinen wrote:
> Configure DMA to use 16B burst size with Elkhart Lake. This makes the
> bus use more efficient and works around an issue which occurs with the
> previously used 1B.
> 
> Fixes: 0a9410b981e9 ("serial: 8250_lpss: Enable DMA on Intel Elkhart Lake")
> Cc: <stable@...r.kernel.org> # serial: 8250_lpss: Configure DMA also w/o DMA filter
> Reported-by: Wentong Wu <wentong.wu@...el.com>
> Co-developed-by: Srikanth Thokala <srikanth.thokala@...el.com>
> Signed-off-by: Srikanth Thokala <srikanth.thokala@...el.com>
> Co-developed-by: Aman Kumar <aman.kumar@...el.com>
> Signed-off-by: Aman Kumar <aman.kumar@...el.com>
> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
> 
> ---
> I know the list of Co-dev-bys & Sob seems a bit odd for a oneliner.
> The reason is that I cleaned up this from a more complex patch using
> the earlier change that I authored myself so only this oneliner
> remained in this patch.

If you changed more than 70% of the code, I would suggest to drop the rest of
(Co)authors and if you want to pay a credit, just mention them in the commit
message in a free form.

-- 
With Best Regards,
Andy Shevchenko