From: Greg KH <gregkh@linuxfoundation.org>
To: Pixiae <pxiaegbayn@use.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: Sat, 19 Oct 2024 08:47:23 +0200 [thread overview]
Message-ID: <2024101946-usage-worst-bac3@gregkh> (raw)
In-Reply-To: <830fb71a-d259-4414-ad42-73a858a3bce6@use.startmail.com>
On Fri, Oct 18, 2024 at 10:56:45AM -0600, Pixiae wrote:
> Dear Greg KH,
>
>
> > Why not just use the in-kernel device code instead of creating your own?
>
> Do you mean that, why I don't write a kernel module?
Yes, what's wrong with the existing usbip client code in Linux?
> If that is what you mean, I don't want to have to share the code of my
> device if I ever want to share my device, would be one reason.
Then it's going to be hard, if not impossible, for us to help you,
sorry, as this is a group for Linux kernel issues.
best of luck!
greg k-h
next prev parent reply other threads:[~2024-10-19 6:47 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
2024-10-18 16:56 ` Pixiae
2024-10-19 6:47 ` Greg KH [this message]
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=2024101946-usage-worst-bac3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=pxiaegbayn@use.startmail.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