From: eli.billauer@gmail.com
To: gregkh@linuxfoundation.org, arnd@arndb.de
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Eli Billauer <eli.billauer@gmail.com>
Subject: [PATCH v5 0/2] Submission of XillyUSB driver
Date: Wed, 26 May 2021 13:03:09 +0300 [thread overview]
Message-ID: <20210526100311.56327-1-eli.billauer@gmail.com> (raw)
From: Eli Billauer <eli.billauer@gmail.com>
This is a resubmission of the XillyUSB driver, which is the USB
variant of the existing Xillybus driver.
Because these driver share some API related functions, this submission
consists of two patches:
(1) A patch moving away Xillybus' class related functions to a
separate module file.
(2) A patch adding the new XillyUSB driver, based upon this new
separate module.
Thanks,
Eli
Eli Billauer (2):
char: xillybus: Move class-related functions to new xillybus_class.c
char: xillybus: Add driver for XillyUSB (Xillybus variant for USB)
drivers/char/xillybus/Kconfig | 22 +-
drivers/char/xillybus/Makefile | 2 +
drivers/char/xillybus/xillybus.h | 10 +-
drivers/char/xillybus/xillybus_class.c | 263 +++
drivers/char/xillybus/xillybus_class.h | 30 +
drivers/char/xillybus/xillybus_core.c | 181 +-
drivers/char/xillybus/xillyusb.c | 2260 ++++++++++++++++++++++++
7 files changed, 2599 insertions(+), 169 deletions(-)
create mode 100644 drivers/char/xillybus/xillybus_class.c
create mode 100644 drivers/char/xillybus/xillybus_class.h
create mode 100644 drivers/char/xillybus/xillyusb.c
--
2.17.1
next reply other threads:[~2021-05-26 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 10:03 eli.billauer [this message]
2021-05-26 10:03 ` [PATCH v5 1/2] char: xillybus: Move class-related functions to new xillybus_class.c eli.billauer
2021-05-26 10:03 ` [PATCH v5 2/2] char: xillybus: Add driver for XillyUSB (Xillybus variant for USB) eli.billauer
2021-05-27 12:00 ` Greg KH
2021-05-27 12:12 ` Greg KH
2021-05-28 9:08 ` Eli Billauer
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=20210526100311.56327-1-eli.billauer@gmail.com \
--to=eli.billauer@gmail.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--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).