From: Greg KH <greg@kroah.com>
To: Michal Simek <monstr@monstr.eu>
Cc: Pavel Machek <pavel@denx.de>, Alan Tull <atull@altera.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Jason Cooper <jason@lakedaemon.net>,
Michal Simek <michal.simek@xilinx.com>,
linux-kernel@vger.kernel.org, Dinh Nguyen <dinguyen@altera.com>,
Philip Balister <philip@balister.org>,
Alessandro Rubini <rubini@gnudd.com>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
Andrew Morton <akpm@linux-foundation.org>,
Cesar Eduardo Barros <cesarb@cesarb.net>,
Joe Perches <joe@perches.com>,
"David S. Miller" <davem@davemloft.net>,
Stephen Warren <swarren@nvidia.com>,
Arnd Bergmann <arnd@arndb.de>,
David Brown <davidb@codeaurora.org>,
Dom Cobley <popcornmix@gmail.com>
Subject: Re: /sys rules Re: [RFC PATCH] fpga: Introduce new fpga subsystem
Date: Thu, 19 Sep 2013 07:18:50 -0700 [thread overview]
Message-ID: <20130919141850.GA21568@kroah.com> (raw)
In-Reply-To: <523B05E6.90605@monstr.eu>
On Thu, Sep 19, 2013 at 04:10:46PM +0200, Michal Simek wrote:
> On 09/19/2013 04:06 PM, Greg KH wrote:
> > On Thu, Sep 19, 2013 at 02:52:37PM +0200, Pavel Machek wrote:
> >> On Thu 2013-09-19 13:22:00, Michal Simek wrote:
> >>> On 09/19/2013 01:17 PM, Pavel Machek wrote:
> >>
> >>>>> Status is just there and for my zynq devcfg driver I do export some status
> >>>>> bits.
> >>>>>
> >>>>> root@petalinux:~# cat /sys/class/fpga/fpga0/status
> >>>>> partial_bitstream_status: 0
> >>>>> prog_done_status: 1
> >>>>> dbg_lock_status: 0
> >>>>> seu_lock_status: 0
> >>>>> aes_en_lock_status: 0
> >>>>> aes_status: 0
> >>>>> seu_status: 0
> >>>>> spniden_status: 1
> >>>>> spiden_status: 1
> >>>>> niden_status: 1
> >>>>> dbgen_status: 1
> >>>>> dap_en_status: 7
> >>>>
> >>>> This is single file? If so, it needs to be changed. Greg is rather
> >>>> clear about that.
> >>>
> >>> Don't you have a link to these rules? I have seen any paragraph from Greg
> >>> about it but I forget where was it.
> >>
> >> "one value per file" and "there must be documentation in
> >> Documentation/ for each file" are the rules, iirc.
> >>
> >> There's Documentation/sysfs-rules.txt, but it does not seem too
> >> relevant.
> >
> > Documentation/filesystems/sysfs.txt says it. It probably should be
> > added to sysfs-rules.txt as well, but the odds that anyone ever reads
> > the documentation is so low I doubt it's even worth it.
> >
> > Also, all sysfs files have to be documented in Documentation/ABI/ which
> > this patch does not do :(
> >
> > And yes, multiple values in a single sysfs file is not allowed at all.
> >
>
> ok. I will read that. This is output from my fpga end driver - nothing
> what I have sent for review.
> Can you please look at origin patch and tell me what you think about it?
When I return from LinuxCon/Plumbers and catch up on my pending patch
queue, I will. It seems that others have already provided good code
review, so I suggest sending out a new version with their changes
integrated and not wait for me.
thanks,
greg k-h
next prev parent reply other threads:[~2013-09-19 14:18 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 15:56 [RFC PATCH 0/1] FPGA subsystem core Michal Simek
2013-09-18 15:56 ` [RFC PATCH] fpga: Introduce new fpga subsystem Michal Simek
2013-09-18 16:11 ` Joe Perches
2013-09-19 10:01 ` Michal Simek
2013-09-19 16:26 ` Alan Tull
2013-09-18 19:02 ` Dinh Nguyen
2013-09-19 11:53 ` Michal Simek
2013-09-18 19:15 ` Jason Cooper
2013-09-18 20:32 ` Jason Gunthorpe
2013-09-18 21:17 ` Alan Tull
2013-09-19 10:08 ` Pavel Machek
2013-09-19 11:02 ` Michal Simek
2013-09-20 20:55 ` Alan Tull
2013-09-24 15:55 ` Alan Tull
2013-09-24 15:58 ` Michal Simek
2013-09-24 16:22 ` Alan Tull
2013-09-24 22:18 ` Greg Kroah-Hartman
2013-09-25 13:55 ` Yves Vandervennet
2013-09-25 14:51 ` Michal Simek
2013-09-25 18:50 ` Alan Tull
2013-09-24 22:54 ` H. Peter Anvin
2013-09-25 10:41 ` Michal Simek
2013-09-25 12:00 ` Pavel Machek
2013-09-25 14:27 ` Philip Balister
2013-09-25 14:43 ` Michal Simek
2013-09-25 19:21 ` Alan Tull
2013-09-19 10:55 ` Michal Simek
2013-09-19 11:17 ` Pavel Machek
2013-09-19 11:22 ` Michal Simek
2013-09-19 12:52 ` /sys rules " Pavel Machek
2013-09-19 14:06 ` Greg KH
2013-09-19 14:10 ` Michal Simek
2013-09-19 14:18 ` Greg KH [this message]
2013-09-19 15:14 ` Alan Tull
2013-09-19 14:20 ` Jason Cooper
2013-09-19 14:37 ` Greg KH
2013-09-19 22:48 ` Pavel Machek
[not found] ` <CADuitaA3PLaOgmqXzfMdMDaXg7G6bT-DufjcuhtWfvaoWRj__Q@mail.gmail.com>
2013-09-19 15:14 ` Michal Simek
2013-09-19 15:18 ` Yves Vandervennet
2013-09-19 17:28 ` Jason Gunthorpe
2013-09-23 13:10 ` Michal Simek
2013-09-23 17:10 ` Jason Gunthorpe
2013-09-25 10:48 ` Michal Simek
2013-09-23 13:02 ` Michal Simek
2013-09-19 10:03 ` Pavel Machek
2013-09-19 10:45 ` Michal Simek
2013-09-27 13:31 ` Michal Simek
2013-09-30 17:12 ` Jason Gunthorpe
2013-10-01 15:59 ` Michal Simek
2013-09-18 23:45 ` Ryan Mallon
2013-09-19 11:37 ` Michal Simek
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=20130919141850.GA21568@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=atull@altera.com \
--cc=cesarb@cesarb.net \
--cc=davem@davemloft.net \
--cc=davidb@codeaurora.org \
--cc=dinguyen@altera.com \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=pavel@denx.de \
--cc=philip@balister.org \
--cc=popcornmix@gmail.com \
--cc=rubini@gnudd.com \
--cc=swarren@nvidia.com \
/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
Powered by JetHome