From: Alan Stern <stern@rowland.harvard.edu>
To: Macpaul Lin <macpaul.lin@mediatek.com>
Cc: Felipe Balbi <balbi@kernel.org>,
Mediatek WSD Upstream <wsd_upstream@mediatek.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, Jim Lin <jilin@nvidia.com>,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
Macpaul Lin <macpaul.lin@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Siqi Lin <siqilin@google.com>
Subject: Re: [PATCH v2] usb: replace hardcode maximum usb string length by definition
Date: Mon, 15 Jun 2020 10:42:57 -0400 [thread overview]
Message-ID: <20200615144257.GA18707@rowland.harvard.edu> (raw)
In-Reply-To: <1592201855-8218-1-git-send-email-macpaul.lin@mediatek.com>
On Mon, Jun 15, 2020 at 02:17:35PM +0800, Macpaul Lin wrote:
> Replace hardcode maximum usb string length (126 bytes) by definition
> "MAX_USB_STRING_LEN".
>
> Signed-off-by: Macpaul Lin <macpaul.lin@mediatek.com>
> ---
> Changes for v2:
> - Add definition "MAX_USB_STRING_LEN" in ch9.h instead of in usb.h.
> Thanks for Alan's suggestion.
Acked-by: Alan Stern <stern@rowland.harvard.edu>
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2020-06-15 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 5:32 [PATCH] usb: replace hardcoded maximum usb string length by definition Macpaul Lin
2020-06-12 14:02 ` Alan Stern
2020-06-15 6:17 ` [PATCH v2] usb: replace hardcode " Macpaul Lin
2020-06-15 14:42 ` Alan Stern [this message]
2020-06-18 8:20 ` Greg Kroah-Hartman
2020-06-18 9:13 ` [PATCH v3] " Macpaul Lin
2020-06-18 14:02 ` Greg Kroah-Hartman
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=20200615144257.GA18707@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jilin@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=macpaul.lin@gmail.com \
--cc=macpaul.lin@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=siqilin@google.com \
--cc=wsd_upstream@mediatek.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;
as well as URLs for NNTP newsgroup(s).