From: Greg KH <gregkh@linuxfoundation.org>
To: Stefan Agner <stefan@agner.ch>
Cc: balbi@kernel.org, andrzej.p@samsung.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] fs: configfs: use hexadecimal values and new line
Date: Wed, 1 Feb 2017 09:07:06 +0100 [thread overview]
Message-ID: <20170201080706.GB17968@kroah.com> (raw)
In-Reply-To: <20170201021917.27398-2-stefan@agner.ch>
On Tue, Jan 31, 2017 at 06:19:17PM -0800, Stefan Agner wrote:
> Other unsigned properties return hexadecimal values, follow this
> convention when printing b_vendor_code too. Also add newlines to
> the OS Descriptor support related properties, like other sysfs
> files use.
configfs is not sysfs, so watch out, you might not need/want those new
lines as tools read the values and are not expecting them.
Have you verified that nothing will break with this? How have you
tested it?
thanks,
greg k-h
next prev parent reply other threads:[~2017-02-01 8:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 2:19 [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric Stefan Agner
2017-02-01 2:19 ` [PATCH 2/2] fs: configfs: use hexadecimal values and new line Stefan Agner
2017-02-01 8:07 ` Greg KH [this message]
2017-02-01 9:02 ` Felipe Balbi
2017-02-01 16:51 ` Stefan Agner
2017-02-01 8:06 ` [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric 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
-- strict thread matches above, loose matches on Subject: below --
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
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=20170201080706.GB17968@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrzej.p@samsung.com \
--cc=balbi@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stefan@agner.ch \
/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