From: Stefan Agner <stefan@agner.ch>
To: balbi@kernel.org
Cc: Krzysztof Opasiak <k.opasiak@samsung.com>,
gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric
Date: Thu, 25 May 2017 01:33:51 -0700 [thread overview]
Message-ID: <0a65de386fcfa0841dc88a238b38ec0c@agner.ch> (raw)
In-Reply-To: <f742275e-4a3c-3b54-0fb3-bfc8b9b5989f@samsung.com>
Hi Felipe,
On 2017-04-19 01:53, Krzysztof Opasiak wrote:
> On 04/15/2017 03:35 AM, Stefan Agner wrote:
>> Currently qw_sign requires UTF-8 character to set, but returns UTF-16
>> when read. This isn't obvious when simply using cat since the null
>> characters are not visible, but hexdump unveils the true string:
>>
>> # echo MSFT100 > os_desc/qw_sign
>> # hexdump -C os_desc/qw_sign
>> 00000000 4d 00 53 00 46 00 54 00 31 00 30 00 30 00 |M.S.F.T.1.0.0.|
>>
>> Make qw_sign symmetric by returning an UTF-8 string too. Also follow
>> common convention and add a new line at the end.
>>
>> Signed-off-by: Stefan Agner <stefan@agner.ch>
>> ---
>> Resend as discussed here:
>> https://patchwork.kernel.org/patch/9548869/
>>
>> Sorry, a bit later than we discussed... Hope still not too late?
>>
>> --
>> Stefan
>>
>> drivers/usb/gadget/configfs.c | 8 ++++++--
>> 1 file changed, 6 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/usb/gadget/configfs.c b/drivers/usb/gadget/configfs.c
>> index cbff3b02840d..863ca4ded1be 100644
>> --- a/drivers/usb/gadget/configfs.c
>> +++ b/drivers/usb/gadget/configfs.c
>> @@ -787,9 +787,13 @@ static ssize_t os_desc_b_vendor_code_store(struct config_item *item,
>> static ssize_t os_desc_qw_sign_show(struct config_item *item, char *page)
>> {
>> struct gadget_info *gi = os_desc_item_to_gadget_info(item);
>> + int res;
>>
>> - memcpy(page, gi->qw_sign, OS_STRING_QW_SIGN_LEN);
>> - return OS_STRING_QW_SIGN_LEN;
>> + res = utf16s_to_utf8s((wchar_t *) gi->qw_sign, OS_STRING_QW_SIGN_LEN,
>> + UTF16_LITTLE_ENDIAN, page, PAGE_SIZE - 1);
>> + page[res++] = '\n';
>> +
>> + return res;
>> }
>>
>> static ssize_t os_desc_qw_sign_store(struct config_item *item, const char *page,
>>
>
> Code itself looks good to me and from libusbgx perspective it's also
> fine to add this new line as we can just drop it like we do with other
> newlines in case of gadget/config strings.
>
> Reviewed-by: Krzysztof Opasiak <k.opasiak@samsung.com>
>
Any chance we get this in this merge window?
This still applies fine on v4.12-rc2.
--
Stefan
next prev parent reply other threads:[~2017-05-25 8:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170415013337epcas3p4871e4a671b352fed711acaf38803095f@epcas3p4.samsung.com>
2017-04-15 1:35 ` Stefan Agner
2017-04-15 1:35 ` [PATCH 2/2] fs: configfs: use hexadecimal values and new line Stefan Agner
2017-04-19 8:45 ` Krzysztof Opasiak
2017-04-19 8:53 ` [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric Krzysztof Opasiak
2017-05-25 8:33 ` Stefan Agner [this message]
2017-06-02 8:25 ` Felipe Balbi
2017-02-01 2:19 Stefan Agner
2017-02-01 8:06 ` Greg KH
2017-02-01 16:59 ` Stefan Agner
2017-02-09 18:04 ` Stefan Agner
2017-02-10 11:19 ` Greg KH
2017-02-10 12:30 ` Felipe Balbi
2017-02-10 20:29 ` Stefan Agner
2017-02-13 10:46 ` Felipe Balbi
2017-02-01 8:07 ` Greg KH
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=0a65de386fcfa0841dc88a238b38ec0c@agner.ch \
--to=stefan@agner.ch \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=k.opasiak@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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
all inboxes | Powered by JetHome®