From: Jiri Kosina <jikos@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: hiddev: use IS_ENABLED() for USB_HIDDEV
Date: Fri, 24 Jun 2016 11:01:52 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1606241101000.6874@cbobk.fhfr.pm> (raw)
In-Reply-To: <5023053.7F6zTHqVIR@wuerfel>
On Fri, 24 Jun 2016, Arnd Bergmann wrote:
> On Friday, June 24, 2016 10:28:50 AM CEST Jiri Kosina wrote:
> > From: Jiri Kosina <jkosina@suse.cz>
> >
> > Use IS_ENABLED() for checking USB_HIDDEV to make sure compilation works
> > for all possible config combinations.
> >
> > Signed-off-by: Jiri Kosina <jkosina@suse.cz>
> > ---
> > include/linux/hiddev.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/include/linux/hiddev.h b/include/linux/hiddev.h
> > index a5dd814..b6f48d6 100644
> > --- a/include/linux/hiddev.h
> > +++ b/include/linux/hiddev.h
> > @@ -37,7 +37,7 @@ struct hid_usage;
> > struct hid_field;
> > struct hid_report;
> >
> > -#ifdef CONFIG_USB_HIDDEV
> > +#if IS_ENABLED(CONFIG_USB_HIDDEV)
> > int hiddev_connect(struct hid_device *hid, unsigned int force);
> > void hiddev_disconnect(struct hid_device *);
> > void hiddev_hid_event(struct hid_device *hid, struct hid_field *field,
> >
> >
>
> CONFIG_USB_HIDDEV is a 'bool' option, so the two look completely
> equivalent.
>
> If we wanted to make USB_HIDDEV a loadable module by itself,
> we'd also need to export those functions and change both the Kconfig
> and Makefile files to ensure that you can't have USB_HIDDEV=m
> in combination with USB_HID=y.
>
> What problem are you trying to fix specifically?
This mail was by my mistake generated from my private git tree; sorry for
the noise, feel free to ignore it.
--
Jiri Kosina
SUSE Labs
prev parent reply other threads:[~2016-06-24 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 8:28 Jiri Kosina
2016-06-24 9:02 ` Arnd Bergmann
2016-06-24 9:01 ` Jiri Kosina [this message]
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=alpine.LNX.2.00.1606241101000.6874@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-input@vger.kernel.org \
--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
all inboxes | Powered by JetHome®