All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Vaishali Thakkar <vthakkar1994@gmail.com>
Cc: Felipe Balbi <balbi@ti.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: gadget: Convert use of __constant_cpu_to_le16 to cpu_to_le16
Date: Wed, 29 Jul 2015 10:24:04 -0500	[thread overview]
Message-ID: <20150729152404.GC32418@saruman.tx.rr.com> (raw)
In-Reply-To: <CAK-LDbKk-zbc9xwcqhNdFhKzwKS0xyUZ2dUMF=V8Bn=QXi0OBQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 991 bytes --]

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@gmail.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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-07-29 15:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-06  1:32 [PATCH] usb: gadget: Convert use of __constant_cpu_to_le16 to cpu_to_le16 Vaishali Thakkar
2015-07-27  6:14 ` Vaishali Thakkar
2015-07-29 15:24   ` Felipe Balbi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150729152404.GC32418@saruman.tx.rr.com \
    --to=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=vthakkar1994@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.