From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: jikos@kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hid:Add warning message if sysfs group is not created for passed kobject in the function, mt_probe
Date: Fri, 5 Feb 2016 08:48:04 +0100 [thread overview]
Message-ID: <20160205074804.GF12345@mail.corp.redhat.com> (raw)
In-Reply-To: <1454601160-21966-1-git-send-email-xerofoify@gmail.com>
Hi Nick,
On Feb 04 2016 or thereabouts, Nicholas Krause wrote:
> This adds a warning message stating that the sysfs group was not
> able to be created for the passed hid_device structure pointer
> with dev_warn.
>
> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> ---
> drivers/hid/hid-multitouch.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/hid/hid-multitouch.c b/drivers/hid/hid-multitouch.c
> index 296d499..b2b2451 100644
> --- a/drivers/hid/hid-multitouch.c
> +++ b/drivers/hid/hid-multitouch.c
> @@ -1133,6 +1133,8 @@ static int mt_probe(struct hid_device *hdev, const struct hid_device_id *id)
> return ret;
>
> ret = sysfs_create_group(&hdev->dev.kobj, &mt_attribute_group);
> + if (ret)
> + dev_warn(&hdev->dev, "Cannot allocate sysfs group for %s\n", hdev->name);
Just nitpicking here. Checkpatch.pl complains about a line over 80
characters here. Could you (or maybe just Jiri) fix that?
Otherwise:
Reviewed-by: Benjamin Tissoires <benajmin.tissoires@redhat.com>
Cheers,
Benjamin
>
> mt_set_maxcontacts(hdev);
> mt_set_input_mode(hdev);
> --
> 2.5.0
>
next parent reply other threads:[~2016-02-05 7:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1454601160-21966-1-git-send-email-xerofoify@gmail.com>
2016-02-05 7:48 ` Benjamin Tissoires [this message]
2016-02-05 13:37 ` [PATCH] hid:Add warning message if sysfs group is not created for passed kobject in the function, mt_probe Jiri Kosina
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=20160205074804.GF12345@mail.corp.redhat.com \
--to=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xerofoify@gmail.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;
as well as URLs for NNTP newsgroup(s).