From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 WIP 3/5] i2c-parport: define ports to connect
Date: Tue, 19 May 2015 14:14:30 +0530 [thread overview]
Message-ID: <20150519084430.GA5751@sudip-PC> (raw)
In-Reply-To: <1432021847.24979.15.camel@chaos.site>
On Tue, May 19, 2015 at 09:50:47AM +0200, Jean Delvare wrote:
> Hi Sudip,
>
> Le Wednesday 06 May 2015 à 15:46 +0530, Sudip Mukherjee a écrit :
> > as of now i2c-parport was connecting to all the available parallel
> > ports. Lets limit that to maximum of 4 instances and at the same time
> > define which instance connects to which parallel port
>
> A leading capital and a trailing dot would look better.
sure.
>
> > Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> > ---
<snip>
> > + for (i = 0; i < MAX_DEVICE; i++) {
> > + if (parport[i] == -1)
> > + continue;
> > + if (port->number == parport[i])
> > + break;
> > + }
> > + if (i == MAX_DEVICE) {
> > + pr_err("port mentioned not found\n");
>
> This error message needs to be improved. Someone seeing this in his/her
> logs would have no idea where it comes from and what it means exactly.
> You want to add "i2c-parport: " at the beginning, and say which port
> number was specified.
oops. sorry about it. I saw all the other messages are having
"i2c-parport: " mentioned. I will modify it. And maybe later I will
send you another patch to use pr_fmt. Or here it may be better if I
mention:
pr_err("i2c-parport: You have chosen not to use parport%d.\n",
port->number);
>
> > + return;
> > + }
> >
> > adapter = kzalloc(sizeof(struct i2c_par), GFP_KERNEL);
> > if (adapter == NULL) {
> > @@ -298,5 +313,11 @@ MODULE_AUTHOR("Jean Delvare <jdelvare@suse.de>");
> > MODULE_DESCRIPTION("I2C bus over parallel port");
> > MODULE_LICENSE("GPL");
> >
> > +module_param_array(parport, int, NULL, 0);
> > +MODULE_PARM_DESC(parport, "Atmost 4 instances are allowed.\n"
>
> You should first say what the parameter does, before going into the
> details. Please use __stringify(MAX_DEVICE) instead of hard-coding 4, so
> that it doesn't need to be updated if MAX_DEVICE ever changes.
then what about:
MODULE_PARM_DESC(parport, "Mention number of i2c-parport instances you
want.\n Atmost " __stringify(MAX_DEVICE) " instances are
allowed.\n Mention port numbers you want to use.\n"
" If the port is not to be used mention -1.\n"
" Default is one instance connected to parport0.\n");
>
<snip>
>
> I tested this patch and it works fine.
>
> Tested-by: Jean Delvare <jdelvare@suse.de>
do i add your Tested-by: to the main patch and this patch?
regards
sudip
>
> --
> Jean Delvare
> SUSE L3 Support
>
next prev parent reply other threads:[~2015-05-19 8:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 10:16 [PATCH v5 WIP 1/5] parport: add device-model to parport subsystem Sudip Mukherjee
2015-05-06 10:16 ` [PATCH v5 WIP 2/5] staging: panel: use new parport device model Sudip Mukherjee
2015-05-19 11:18 ` Dan Carpenter
2015-05-20 8:23 ` Jean Delvare
2015-05-06 10:16 ` [PATCH v5 WIP 3/5] i2c-parport: define ports to connect Sudip Mukherjee
2015-05-19 7:50 ` Jean Delvare
2015-05-19 8:44 ` Sudip Mukherjee [this message]
2015-05-19 9:28 ` Jean Delvare
2015-05-19 9:58 ` Sudip Mukherjee
2015-05-19 11:23 ` Dan Carpenter
2015-05-19 12:23 ` Jean Delvare
2015-05-06 10:16 ` [PATCH v5 WIP 4/5] i2c-parport: use new parport device model Sudip Mukherjee
2015-05-20 7:57 ` Jean Delvare
2015-05-20 8:16 ` Sudip Mukherjee
2015-05-06 10:16 ` [PATCH v5 WIP 5/5] paride: " Sudip Mukherjee
2015-05-19 11:32 ` Dan Carpenter
2015-05-19 12:32 ` Sudip Mukherjee
2015-05-20 8:07 ` Jean Delvare
2015-05-20 8:33 ` Sudip Mukherjee
2015-05-19 11:08 ` [PATCH v5 WIP 1/5] parport: add device-model to parport subsystem Dan Carpenter
2015-05-19 13:18 ` Sudip Mukherjee
2015-05-20 7:54 ` Jean Delvare
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=20150519084430.GA5751@sudip-PC \
--to=sudipm.mukherjee@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jdelvare@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.