From: Matias Mucciolo <mmucciolo@suteba.org.ar>
To: Ian Abbott <abbotti@mev.co.uk>
Cc: H Hartley Sweeten <hsweeten@visionengravers.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH resend] staging: comedi: comedi_fops: coding style fixes
Date: Mon, 12 Sep 2016 13:01:01 -0300 [thread overview]
Message-ID: <1608130.74sP92kvXV@varitech> (raw)
In-Reply-To: <40f52f01-4f57-3f39-42f2-081f4619e656@mev.co.uk>
Hi Ian
yes its a coding style issue(checkpatch.pl WARN)
and reference:
https://lwn.net/Articles/696229/
(sorry about the noise.)
--
Matias Mucciolo
Area de Infraestructura.
Piedras 737 C.A.B.A
SUTEBA
On Monday 12 September 2016 16:52:59 Ian Abbott wrote:
> On 12/09/16 14:18, Matias Mucciolo wrote:
> >
> > From: Matias Mucciolo <mmucciolo@suteba.org.ar>
> >
> > - Fixed coding style in comedi_fops.c Symbolic to octal permission.
> >
> > Signed-off-by: Matias Mucciolo <mmucciolo@suteba.org.ar>
> > ---
> > drivers/staging/comedi/comedi_fops.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/staging/comedi/comedi_fops.c b/drivers/staging/comedi/comedi_fops.c
> > index 1999eed..bf922ea 100644
> > --- a/drivers/staging/comedi/comedi_fops.c
> > +++ b/drivers/staging/comedi/comedi_fops.c
> > @@ -81,20 +81,20 @@ struct comedi_file {
> > (COMEDI_NUM_MINORS - COMEDI_NUM_BOARD_MINORS)
> >
> > static int comedi_num_legacy_minors;
> > -module_param(comedi_num_legacy_minors, int, S_IRUGO);
> > +module_param(comedi_num_legacy_minors, int, 0444);
> > MODULE_PARM_DESC(comedi_num_legacy_minors,
> > "number of comedi minor devices to reserve for non-auto-configured devices (default 0)"
> > );
> >
> > unsigned int comedi_default_buf_size_kb = CONFIG_COMEDI_DEFAULT_BUF_SIZE_KB;
> > -module_param(comedi_default_buf_size_kb, uint, S_IRUGO | S_IWUSR);
> > +module_param(comedi_default_buf_size_kb, uint, 0644);
> > MODULE_PARM_DESC(comedi_default_buf_size_kb,
> > "default asynchronous buffer size in KiB (default "
> > __MODULE_STRING(CONFIG_COMEDI_DEFAULT_BUF_SIZE_KB) ")");
> >
> > unsigned int comedi_default_buf_maxsize_kb
> > = CONFIG_COMEDI_DEFAULT_BUF_MAXSIZE_KB;
> > -module_param(comedi_default_buf_maxsize_kb, uint, S_IRUGO | S_IWUSR);
> > +module_param(comedi_default_buf_maxsize_kb, uint, 0644);
> > MODULE_PARM_DESC(comedi_default_buf_maxsize_kb,
> > "default maximum size of asynchronous buffer in KiB (default "
> > __MODULE_STRING(CONFIG_COMEDI_DEFAULT_BUF_MAXSIZE_KB) ")");
> >
>
> In my review of the earlier patch, I said I was fine with the octal
> constants, but on reflection, I'm not sure it's worth changing them just
> for the hell of it. We'd probably get a patch from someone else later
> to change it back to symbolic constants. Is there an actual coding
> style issue, or is this just a personal preference?
>
> --
> -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
> -=( Web: http://www.mev.co.uk/ )=-
next prev parent reply other threads:[~2016-09-12 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 13:18 [PATCH resend] staging: comedi: comedi_fops: coding style fixes Matias Mucciolo
2016-09-12 15:52 ` Ian Abbott
2016-09-12 16:01 ` Matias Mucciolo [this message]
2016-09-12 18:00 ` Ian Abbott
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=1608130.74sP92kvXV@varitech \
--to=mmucciolo@suteba.org.ar \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=linux-kernel@vger.kernel.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