linux-kernel - RE: [PATCH RESEND] bus: fsl-mc: explicitly define the fsl_mc

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:   Thu, 29 Nov 2018 14:09:11 +0000
From:   Ioana Ciornei <ioana.ciornei@....com>
To:     "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
CC:     Laurentiu Tudor <laurentiu.tudor@....com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH RESEND] bus: fsl-mc: explicitly define the fsl_mc_command
 endianness

> > Both the header and the command parameters of the fsl_mc_command are
> > 64-bit little-endian words. Use the appropriate type to explicitly
> > specify their endianness.
> >
> > Signed-off-by: Ioana Ciornei <ioana.ciornei@....com>
> > Reviewed-by: Laurentiu Tudor <laurentiu.tudor@....com>
> > ---
> >  include/linux/fsl/mc.h | 12 ++++++------
> >  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> What tree is this made against?  I can't seem to apply it to any of mine :(
> 

This was generated against a clean 4.20-rc1 but I just checked and I could apply it on both staging-next and driver-core-next.
Am I missing something?

Ioana

> Any hints?
> 
> thanks,
> 
> greg k-h