From: Greg KH <gregkh@linuxfoundation.org>
To: Angel D Raygoza <9bea5cde-4b55-4b34-b91a-37dbd16ce68e@startmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: Usb IP Failing to connect depending of program being runned even when the connection talks are identical
Date: Fri, 18 Oct 2024 07:53:51 +0200 [thread overview]
Message-ID: <2024101824-shakable-portfolio-9cfb@gregkh> (raw)
In-Reply-To: <50f9a086-d873-44d2-bdda-a8e00dd2421e@startmail.com>
On Thu, Oct 17, 2024 at 03:05:43PM -0600, Angel D Raygoza wrote:
> Dear USB Linux Mailing List.
>
> I have been trying to write a USB IP Virtual Device as your protocol
> (https://docs.kernel.org/usb/usbip_protocol.html).
Why not just use the in-kernel device code instead of creating your own?
Is there something wrong with that implementation?
thanks,
greg k-h
next prev parent reply other threads:[~2024-10-18 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 21:05 Usb IP Failing to connect depending of program being runned even when the connection talks are identical Angel D Raygoza
2024-10-18 5:53 ` Greg KH [this message]
2024-10-18 16:56 ` Pixiae
2024-10-19 6:47 ` Greg KH
2024-10-19 14:38 ` Alan Stern
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=2024101824-shakable-portfolio-9cfb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=9bea5cde-4b55-4b34-b91a-37dbd16ce68e@startmail.com \
--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