From: Shuah Khan <shuah@kernel.org>
To: David Valleau <valleau@chromium.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: briannorris@chromium.org, linux-usb@vger.kernel.org,
Michael Grzeschik <m.grzeschik@pengutronix.de>,
Valentina Manea <valentina.manea.m@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <alexander.levin@microsoft.com>,
shuah <shuah@kernel.org>
Subject: tools: usb: usbip: adding support for older kernel versions
Date: Sat, 16 Mar 2019 17:39:50 -0600 [thread overview]
Message-ID: <44e151af-b6c4-d0af-3ef1-a5632d079915@kernel.org> (raw)
Hi David,
On 3/6/19 2:47 PM, David Valleau wrote:
> The current usbip tool relies on the behavior of the vhci-hcd driver in
> order to work correctly. In instances where a newer version of the tool
> is used with an older version of the kernel, there are incompatibilities
> that can sometimes result in failure.
usbip tool is tied to the kernel version. This is reason why it is
co-located with the usbip driver in the kernel sources. This is not
a typical tool scenario to be able to use new tool on old kernels.
I would like to understand the reasons for wanting to run new tool on
old kernels.
thanks,
-- Shuah
next reply other threads:[~2019-03-16 23:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 23:39 Shuah Khan [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-27 1:16 tools: usb: usbip: adding support for older kernel versions Brian Norris
2019-03-26 1:59 Shuah Khan
2019-03-26 1:29 Brian Norris
2019-03-26 1:28 Brian Norris
2019-03-26 0:55 Greg Kroah-Hartman
2019-03-26 0:49 Brian Norris
2019-03-26 0:13 Greg Kroah-Hartman
2019-03-26 0:04 Shuah Khan
2019-03-25 23:02 Brian Norris
2019-03-25 22:07 Shuah Khan
2019-03-25 17:56 Brian Norris
2019-03-25 15:51 Shuah Khan
2019-03-18 18:23 Brian Norris
2019-03-06 21:47 David Valleau
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=44e151af-b6c4-d0af-3ef1-a5632d079915@kernel.org \
--to=shuah@kernel.org \
--cc=alexander.levin@microsoft.com \
--cc=briannorris@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.grzeschik@pengutronix.de \
--cc=valentina.manea.m@gmail.com \
--cc=valleau@chromium.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).