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
| ||
|
Message-ID: <74b898b9-7a9b-cdf4-ffeb-35f70bde3378@hartkopp.net> Date: Tue, 16 May 2017 06:16:07 -0700 From: Oliver Hartkopp <socketcan@...tkopp.net> To: Alexandre Belloni <alexandre.belloni@...e-electrons.com> Cc: Marc Kleine-Budde <mkl@...gutronix.de>, Quentin Schulz <quentin.schulz@...e-electrons.com>, wg@...ndegger.com, mario.huettel@....net, linux-can@...r.kernel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, thomas.petazzoni@...e-electrons.com Subject: Re: [PATCH v4 1/4] can: m_can: move Message RAM initialization to function Hi Alexandre, On 05/16/2017 01:00 AM, Alexandre Belloni wrote: > Hi, > > On 15/05/2017 at 20:51:30 -0700, Oliver Hartkopp wrote: >> On 05/15/2017 06:50 AM, Marc Kleine-Budde wrote: >>> Looks good, added to linux-can-next. >> >> Isn't this a fix for linux-can instead? >> >> At least it would make no sense to me to have the upgraded M_CAN driver in >> Linux 4.12 without this fix. >> > > The related suspend mode on the sama5d2 is not present in v4.12 so I > think this can wait v4.13. > Agreed! Thanks for the explanation. Regards, Oliver
Powered by blists - more mailing lists