From: Greg KH <gregkh@linuxfoundation.org>
To: Eli Billauer <eli.billauer@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-usb@vger.kernel.org,
arnd@arndb.de, linux-kernel@vger.kernel.org,
dan.carpenter@oracle.com
Subject: Re: [PATCH v4 1/2] char: xillybus: Move class-related functions to new xillybus_class.c
Date: Mon, 22 Mar 2021 12:11:50 +0100 [thread overview]
Message-ID: <YFh7dlY9cntgoLXD@kroah.com> (raw)
In-Reply-To: <6058792C.90801@gmail.com>
On Mon, Mar 22, 2021 at 01:02:04PM +0200, Eli Billauer wrote:
> On 21/03/21 14:24, Greg KH wrote:
> > > +config XILLYBUS_CLASS
> > > > + tristate
> > > > +
> > > > config XILLYBUS
> > > > tristate "Xillybus generic FPGA interface"
> > > > depends on PCI || OF
> > > > select CRC32
> > > > + select XILLYBUS_CLASS
> > depends on, do not select.
> >
> XILLYBUS and XILLYBUS_PCIE are currently enabled as M in several Linux
> distributions. Making them depend on, rather than select XILLYBUS_CLASS is
> likely to disable the driver in those distributions.
That's not an issue here, depends-on will allow those distros to also
enable this option.
But wait, why is this a separate option at all? Shouldn't the class
code just be part of the "core" XILLYBUS code anyway?
thanks,
greg k-h
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2021-03-22 11:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 9:50 [PATCH v4 0/2] Submission of XillyUSB driver eli.billauer
2021-03-11 9:50 ` [PATCH v4 1/2] char: xillybus: Move class-related functions to new xillybus_class.c eli.billauer
2021-03-21 12:24 ` Greg KH
2021-03-22 11:02 ` Eli Billauer
2021-03-22 11:11 ` Greg KH [this message]
2021-03-23 12:05 ` Eli Billauer
2021-03-28 11:46 ` Greg KH
2021-03-21 12:24 ` Greg KH
2021-03-11 9:50 ` [PATCH v4 2/2] staging: Add driver for XillyUSB (Xillybus variant for USB) eli.billauer
2021-03-21 12:23 ` Greg KH
2021-03-22 11:01 ` Eli Billauer
2021-03-22 11:13 ` Greg KH
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=YFh7dlY9cntgoLXD@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=eli.billauer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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;
as well as URLs for NNTP newsgroup(s).