From: gpramod@codeaurora.org
To: rtatiya@codeaurora.org
Cc: "Greg KH" <gregkh@linuxfoundation.org>,
rtatiya@codeaurora.org, sarah.a.sharp@linux.intel.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] usb: Enable LPM for USB 2.01+ full-speed devices
Date: Wed, 8 Apr 2015 13:24:20 -0000 [thread overview]
Message-ID: <7c5bbcf93fe0aff20481f3884024d603.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <6101704ff4dc2e95b67146ed26d01c9f.squirrel@www.codeaurora.org>
>> On Wed, Mar 25, 2015 at 12:23:19PM +0530, rtatiya@codeaurora.org wrote:
>>> From: Rupesh Tatiya <rtatiya@codeaurora.org>
>>>
>>> USB 2.01+ full-speed devices can have extended descriptor as well
>>> and can support LPM.
>>>
>>> Change-Id: Ic055d51c02651810d3eb7141bab20a090fe8453b
>>
>> We can't take patches with this in it, as it makes no sense in a kernel
>> changelog :(
>>
>>
>
> Sorry this is my first time (I read as much as I can before sending patch
> but not enough I guess). Should I remove "From" line or rephrase commit
> message?
Rupesh, Just remove below line from commit message:
>>> Change-Id: Ic055d51c02651810d3eb7141bab20a090fe8453b
>
> Thanks,
> Rupesh
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
-
Pramod
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-04-08 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 6:53 [PATCH] usb: Enable LPM for USB 2.01+ full-speed devices rtatiya
2015-03-25 6:58 ` Greg KH
2015-04-08 11:27 ` rtatiya
2015-04-08 11:37 ` Greg KH
2015-04-08 13:24 ` gpramod [this message]
2015-04-14 11:06 ` [PATCH v2] " Rupesh Tatiya
2015-03-25 8:41 ` [PATCH] " Oliver Neukum
2015-04-08 11:24 ` rtatiya
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=7c5bbcf93fe0aff20481f3884024d603.squirrel@www.codeaurora.org \
--to=gpramod@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rtatiya@codeaurora.org \
--cc=sarah.a.sharp@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox