From: Johan Hovold <johan@kernel.org>
To: Ryan Mann <rmann@ndigital.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5] NDI FTDI USB driver support
Date: Thu, 10 Jul 2025 12:34:33 +0200 [thread overview]
Message-ID: <aG-XOXPcT3kFxKQg@hovoldconsulting.com> (raw)
In-Reply-To: <YQXPR01MB498735732651163477C995B9DF49A@YQXPR01MB4987.CANPRD01.PROD.OUTLOOK.COM>
On Wed, Jul 09, 2025 at 01:50:15PM +0000, Ryan Mann wrote:
> From: Ryan Mann (NDI) <rmann@ndigital.com>
>
> NDI (Northern Digital Inc.) is introducing a new product called the
> EMGUIDE GEMINI that will use an FTDI chip for USB serial communications.
> Add the NDI EMGUIDE GEMINI product ID that uses the NDI Vendor ID
> rather than the FTDI Vendor ID, unlike older products.
>
> Signed-off-by: Ryan Mann <rmann@ndigital.com>
> ---
> V1 -> V2: Email-to issues fixed
> V2 -> V3: Email formatting issues fixed, removed future devices
> V3 -> V4: Email formatting issues fixed, removed extra comments
> V4 -> V5: Diff whitespace issues fixed,
> Restored the Aurora SCU device mapping that was removed
> + { USB_DEVICE(NDI_VID, FTDI_NDI_EMGUIDE_GEMINI_PID),
> + .driver_info = (kernel_ulong_t)&ftdi_NDI_device_quirk },
I was going to apply this, but turns out it does not even compile.
Sending completely untested patches like this is really not acceptable.
> +#define FTDI_NDI_VID 0x23F2
Also change your Subject to use the common prefix ("USB: serial:
ftdi_sio: ..." when respinning.
Johan
next prev parent reply other threads:[~2025-07-10 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 13:50 Ryan Mann
2025-07-10 10:34 ` Johan Hovold [this message]
2025-07-10 14:33 ` kernel test robot
2025-07-10 15:12 ` Ryan Mann
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=aG-XOXPcT3kFxKQg@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rmann@ndigital.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
all inboxes | Powered by JetHome®