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
| ||
|
Date: Thu, 30 Mar 2017 14:42:19 +0100 From: Jon Hunter <jonathanh@...dia.com> To: Olliver Schinagl <oliver@...inagl.nl>, Laxman Dewangan <ldewangan@...dia.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, "Jiri Slaby" <jslaby@...e.com>, Stephen Warren <swarren@...dotorg.org>, "Thierry Reding" <thierry.reding@...il.com>, Alexandre Courbot <gnurou@...il.com> CC: <linux-serial@...r.kernel.org>, <linux-tegra@...r.kernel.org>, <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] serial: tegra: Map the iir register to default defines On 29/03/17 19:48, Olliver Schinagl wrote: > The tegra serial IP seems to be following the common layout and the > interrupt ID's match up nicely. Replace the magic values to match the > common serial_reg defines, with the addition of the Tegra unique End of > Data interrupt. > > Signed-off-by: Olliver Schinagl <oliver@...inagl.nl> > --- > Note I do not own any tegra hardware and just noticed it while working on my > somewhat related previous patch, > "serial: Do not treat the IIR register as a bitfield" > > As such, this patch can only be applied after the aforementioned patch or the > iir variable will not have its mask applied yet. Nit-pick. If this is the case, then this should really be part of a patch series so it is obvious to everyone that this should only be applied after the other patch. Cheers Jon -- nvpublic
Powered by blists - more mailing lists