[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100510123514.GA11804@besouro.research.nokia.com>
Date: Mon, 10 May 2010 15:35:14 +0300
From: Eduardo Valentin <eduardo.valentin@...ia.com>
To: ext Paul Mundt <lethal@...ux-sh.org>
Cc: "Valentin Eduardo (Nokia-D/Helsinki)" <eduardo.valentin@...ia.com>,
LKML <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Linux-OMAP <linux-omap@...r.kernel.org>,
Russell King <linux@....linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
ext Tony Lindgren <tony@...mide.com>,
ext Kevin Hilman <khilman@...prootsystems.com>,
"De-Schrijver Peter (Nokia-D/Helsinki)"
<Peter.De-Schrijver@...ia.com>,
"santosh.shilimkar@...com" <santosh.shilimkar@...com>,
Ambresh <a0393775@...com>,
"Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@...ia.com>
Subject: Re: [PATCHv4 1/4] procfs: Introduce socinfo under /proc
On Mon, May 10, 2010 at 01:13:00PM +0200, ext Paul Mundt wrote:
> On Mon, May 10, 2010 at 01:37:34PM +0300, Eduardo Valentin wrote:
> > + */
> > +#include <linux/fs.h>
> > +#include <linux/init.h>
> > +#include <linux/proc_fs.h>
> > +#include <linux/seq_file.h>
> > +
> > +extern const struct seq_operations socinfo_op;
>
> This doesn't look promising..
Right.. as stated in patch description (maybe not that clear), this was
basically same thing which you see under fs/proc/cpuinfo.c
>
> > +static int socinfo_open(struct inode *inode, struct file *file)
> > +{
> > + return seq_open(file, &socinfo_op);
> > +}
> > +
> If you use single_open() ..
>
> > +static const struct file_operations proc_socinfo_operations = {
> > + .open = socinfo_open,
> > + .read = seq_read,
> > + .llseek = seq_lseek,
> > + .release = seq_release,
> > +};
> > +
> .. and single_release(), then none of the seq_operations are necessary.
Good! will replace than with single_[open,release].
>
> > +static int __init proc_socinfo_init(void)
> > +{
> > + proc_create("socinfo", 0, NULL, &proc_socinfo_operations);
> > + return 0;
> > +}
> > +module_init(proc_socinfo_init);
>
> proc_create() can fail, so some error handling here would be nice.
right. will add it.
>
> On Mon, May 10, 2010 at 01:37:35PM +0300, Eduardo Valentin wrote:
> > +static int c_show(struct seq_file *m, void *v)
> > +{
> > + seq_printf(m, "SoC\t: %s\n", socinfo);
> > +
> > + return 0;
> > +}
> > +
> > +static void *c_start(struct seq_file *m, loff_t *pos)
> > +{
> > + return *pos < 1 ? (void *)1 : NULL;
> > +}
> > +
> > +static void *c_next(struct seq_file *m, void *v, loff_t *pos)
> > +{
> > + ++*pos;
> > + return NULL;
> > +}
> > +
> > +static void c_stop(struct seq_file *m, void *v)
> > +{
> > +}
> > +
> > +const struct seq_operations socinfo_op = {
> > + .start = c_start,
> > + .next = c_next,
> > + .stop = c_stop,
> > + .show = c_show
> > +};
>
> You'll still need the show function, but all of the rest of this is just
> duplicating what single_open() already does. If the socinfo string is
> static you may also want to rework this a bit so you can just stash the
> string in the proc_dir_entry private data. Combine this with something
> like kstrdup() and you'll save yourself a bit of stack while you're at
> it.
yeah. will add those comments as well.
Thanks for reviewing,
--
Eduardo Valentin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists