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:	Wed, 29 Jul 2015 10:24:04 -0500
From:	Felipe Balbi <balbi@...com>
To:	Vaishali Thakkar <vthakkar1994@...il.com>
CC:	Felipe Balbi <balbi@...com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	<linux-usb@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] usb: gadget: Convert use of __constant_cpu_to_le16 to
 cpu_to_le16

On Mon, Jul 27, 2015 at 11:44:08AM +0530, Vaishali Thakkar wrote:
> On Sat, Jun 6, 2015 at 7:02 AM, Vaishali Thakkar <vthakkar1994@...il.com> wrote:
> > In big endian cases, macro cpu_to_le16 unfolds to __swab16 which
> > provides special case for constants. In little endian cases,
> > __constant_cpu_to_le16 and cpu_to_le16 expand directly to the
> > same expression. So, replace __constant_cpu_to_le16 with
> > cpu_to_le16 with the goal of getting rid of the definition of
> > __constant_cpu_to_le16 completely.
> >
> > The semantic patch that performs this transformation is as follows:
> >
> > @@expression x;@@
> >
> > - __constant_cpu_to_le16(x)
> > + cpu_to_le16(x)
> 
> Hello
> 
> This is just a friendly reminder. As this patch was sent before almost 50 days
> with the aim of removing constant_<foo> definitions completely
> and not yet applied, is it missed?? Do I need to resend this patch?

you should have received my automated email now.

-- 
balbi

Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ