From: Artem Bityutskiy <dedekind1@gmail.com>
To: Tom Isaacson <Tom.Isaacson@navico.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Florian Fainelli <ffainelli@freebox.fr>
Subject: RE: Exposing NAND chip information
Date: Fri, 27 Apr 2012 17:12:25 +0300 [thread overview]
Message-ID: <1335535945.1910.11.camel@koala> (raw)
In-Reply-To: <B36E81988B048A4FA3600EDE585F756BD123D1@EXCH02-AKLNZ.MARINE.NET.INT>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
On Sun, 2012-04-22 at 23:40 +0000, Tom Isaacson wrote:
> The documentation for sysfs (http://lxr.linux.no/linux
> +v3.3.2/Documentation/filesystems/sysfs.txt) says:
> "Attributes should be ASCII text files, preferably with only one value
> per file. It is noted that it may not be efficient to contain only one
> value per file, so it is socially acceptable to express an array of
> values of the same type."
> So if we want to combine we should do it the first way - both IDs in
> one file, both strings in another:
> id - Manufacturer and Chip ID (tab separated)
> name - Manufacturer and Chip name (tab separated)
I think that would not make sense to combine ids and names. I think that
is a general recommendation which should be go through the common sense
filter. E.g., there are many "dev" attributes in "major:minor" format.
Or look at the 'uevent' attributes contents. Or "resource" pci
subsystems' files.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-04-27 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 23:20 Exposing NAND chip information Tom Isaacson
2012-04-16 6:59 ` Florian Fainelli
2012-04-16 23:51 ` Tom Isaacson
2012-04-17 9:39 ` Florian Fainelli
2012-04-22 14:44 ` Artem Bityutskiy
2012-04-22 23:40 ` Tom Isaacson
2012-04-27 14:12 ` Artem Bityutskiy [this message]
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=1335535945.1910.11.camel@koala \
--to=dedekind1@gmail.com \
--cc=Tom.Isaacson@navico.com \
--cc=ffainelli@freebox.fr \
--cc=linux-mtd@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).