Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-06-02 Thread Felipe Balbi
Hi, Stefan Agner writes: > 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

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-06-02 Thread Felipe Balbi
Hi, Stefan Agner writes: > 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

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-05-25 Thread Stefan Agner
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

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-05-25 Thread Stefan Agner
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

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-04-19 Thread Krzysztof Opasiak
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

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-04-19 Thread Krzysztof Opasiak
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

[PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-04-14 Thread Stefan Agner
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 4d 00 53 00 46 00

[PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-04-14 Thread Stefan Agner
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 4d 00 53 00 46 00

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-02-13 Thread Felipe Balbi
Hi, Stefan Agner writes: >>> On Thu, Feb 09, 2017 at 10:04:43AM -0800, Stefan Agner wrote: On 2017-02-01 08:59, Stefan Agner wrote: > On 2017-02-01 00:06, Greg KH wrote: >> On Tue, Jan 31, 2017 at 06:19:16PM -0800, Stefan Agner wrote: >>> Currently qw_sign

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-02-13 Thread Felipe Balbi
Hi, Stefan Agner writes: >>> On Thu, Feb 09, 2017 at 10:04:43AM -0800, Stefan Agner wrote: On 2017-02-01 08:59, Stefan Agner wrote: > On 2017-02-01 00:06, Greg KH wrote: >> On Tue, Jan 31, 2017 at 06:19:16PM -0800, Stefan Agner wrote: >>> Currently qw_sign requires UTF-8

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-02-10 Thread Stefan Agner
On 2017-02-10 04:30, Felipe Balbi wrote: > Hi, > > Greg KH writes: >> On Thu, Feb 09, 2017 at 10:04:43AM -0800, Stefan Agner wrote: >>> On 2017-02-01 08:59, Stefan Agner wrote: >>> > On 2017-02-01 00:06, Greg KH wrote: >>> >> On Tue, Jan 31, 2017 at 06:19:16PM -0800,

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-02-10 Thread Stefan Agner
On 2017-02-10 04:30, Felipe Balbi wrote: > Hi, > > Greg KH writes: >> On Thu, Feb 09, 2017 at 10:04:43AM -0800, Stefan Agner wrote: >>> On 2017-02-01 08:59, Stefan Agner wrote: >>> > On 2017-02-01 00:06, Greg KH wrote: >>> >> On Tue, Jan 31, 2017 at 06:19:16PM -0800, Stefan Agner wrote: >>> >>>

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-02-10 Thread Felipe Balbi
Hi, Greg KH writes: > On Thu, Feb 09, 2017 at 10:04:43AM -0800, Stefan Agner wrote: >> On 2017-02-01 08:59, Stefan Agner wrote: >> > On 2017-02-01 00:06, Greg KH wrote: >> >> On Tue, Jan 31, 2017 at 06:19:16PM -0800, Stefan Agner wrote: >> >>> Currently qw_sign

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-02-10 Thread Felipe Balbi
Hi, Greg KH writes: > On Thu, Feb 09, 2017 at 10:04:43AM -0800, Stefan Agner wrote: >> On 2017-02-01 08:59, Stefan Agner wrote: >> > On 2017-02-01 00:06, Greg KH wrote: >> >> On Tue, Jan 31, 2017 at 06:19:16PM -0800, Stefan Agner wrote: >> >>> Currently qw_sign requires UTF-8 character to set,

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-02-10 Thread Greg KH
On Thu, Feb 09, 2017 at 10:04:43AM -0800, Stefan Agner wrote: > On 2017-02-01 08:59, Stefan Agner wrote: > > On 2017-02-01 00:06, Greg KH wrote: > >> On Tue, Jan 31, 2017 at 06:19:16PM -0800, Stefan Agner wrote: > >>> Currently qw_sign requires UTF-8 character to set, but returns UTF-16 > >>> when

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-02-10 Thread Greg KH
On Thu, Feb 09, 2017 at 10:04:43AM -0800, Stefan Agner wrote: > On 2017-02-01 08:59, Stefan Agner wrote: > > On 2017-02-01 00:06, Greg KH wrote: > >> On Tue, Jan 31, 2017 at 06:19:16PM -0800, Stefan Agner wrote: > >>> Currently qw_sign requires UTF-8 character to set, but returns UTF-16 > >>> when

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-02-09 Thread Stefan Agner
On 2017-02-01 08:59, Stefan Agner wrote: > On 2017-02-01 00:06, Greg KH wrote: >> On Tue, Jan 31, 2017 at 06:19:16PM -0800, 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 >>>

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-02-09 Thread Stefan Agner
On 2017-02-01 08:59, Stefan Agner wrote: > On 2017-02-01 00:06, Greg KH wrote: >> On Tue, Jan 31, 2017 at 06:19:16PM -0800, 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 >>>

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-02-01 Thread Stefan Agner
On 2017-02-01 00:06, Greg KH wrote: > On Tue, Jan 31, 2017 at 06:19:16PM -0800, 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

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-02-01 Thread Stefan Agner
On 2017-02-01 00:06, Greg KH wrote: > On Tue, Jan 31, 2017 at 06:19:16PM -0800, 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

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-02-01 Thread Greg KH
On Tue, Jan 31, 2017 at 06:19:16PM -0800, 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 >

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-02-01 Thread Greg KH
On Tue, Jan 31, 2017 at 06:19:16PM -0800, 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 >

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-02-01 Thread Greg KH
On Tue, Jan 31, 2017 at 06:19:16PM -0800, 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 >

Re: [PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-02-01 Thread Greg KH
On Tue, Jan 31, 2017 at 06:19:16PM -0800, 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 >

[PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-01-31 Thread Stefan Agner
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 4d 00 53 00 46 00

[PATCH 1/2] fs: configfs: make qw_sign attribute symmetric

2017-01-31 Thread Stefan Agner
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 4d 00 53 00 46 00