From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Ben Hutchings <ben.hutchings@codethink.co.uk>,
Wolfram Sang <wsa@the-dreams.de>
Cc: CT kernel <linux-kernel@lists.codethink.co.uk>,
linux-i2c@vger.kernel.org
Subject: Re: [Linux-kernel] [PATCH] i2c: mux: demux-pinctrl: Fix reading the "master" attribute
Date: Wed, 30 Mar 2016 17:42:31 +0100 [thread overview]
Message-ID: <56FC01F7.1060503@codethink.co.uk> (raw)
In-Reply-To: <1459355236.27975.5.camel@codethink.co.uk>
On 30/03/16 17:27, Ben Hutchings wrote:
> sysfs attributes should use the same format for reads and writes,
> rather than pretty-printing on read.
>
> Fixes: 50a5ba876908 ("i2c: mux: demux-pinctrl: add driver")
> Signed-off-by: Ben Hutchings <ben.hutchings@codethink.co.uk>
should that be moved to a debugfs entry or a read-only sysfs?
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2016-03-30 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 16:27 [PATCH] i2c: mux: demux-pinctrl: Fix reading the "master" attribute Ben Hutchings
2016-03-30 16:42 ` Ben Dooks [this message]
2016-03-30 16:45 ` [Linux-kernel] " Ben Hutchings
2016-03-30 20:56 ` Wolfram Sang
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=56FC01F7.1060503@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=ben.hutchings@codethink.co.uk \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=wsa@the-dreams.de \
/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).