From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 208267] usbip broken with latest kernels?
Date: Tue, 01 Sep 2020 14:52:20 +0000 [thread overview]
Message-ID: <bug-208267-208809-nsSo4ItjxH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208267-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208267
--- Comment #15 from Greg Kroah-Hartman (greg@kroah.com) ---
On Tue, Sep 01, 2020 at 02:18:17PM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208267
>
> --- Comment #14 from DocMAX (forum@docmax.my.to) ---
> things = breaking functionality of well known programs that are even
> integrated
> in the kernel.
Bugs happen, we are human :)
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-09-01 14:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 13:57 [Bug 208267] New: usbip broken with latest kernels? bugzilla-daemon
2020-06-21 14:52 ` [Bug 208267] " bugzilla-daemon
2020-06-21 15:20 ` Greg KH
2020-06-21 15:20 ` bugzilla-daemon
2020-06-21 17:03 ` bugzilla-daemon
2020-06-22 8:04 ` Greg KH
2020-06-22 8:04 ` bugzilla-daemon
2020-06-28 22:48 ` bugzilla-daemon
2020-07-19 21:29 ` bugzilla-daemon
2020-07-20 6:57 ` Greg KH
2020-07-20 6:57 ` bugzilla-daemon
2020-07-20 7:15 ` bugzilla-daemon
2020-07-21 11:38 ` bugzilla-daemon
2020-08-27 20:37 ` bugzilla-daemon
2020-08-28 20:46 ` bugzilla-daemon
2020-09-01 10:41 ` bugzilla-daemon
2020-09-01 14:06 ` Greg KH
2020-09-01 14:06 ` bugzilla-daemon
2020-09-01 14:18 ` bugzilla-daemon
2020-09-01 14:52 ` Greg KH
2020-09-01 14:52 ` bugzilla-daemon [this message]
2020-09-05 12:56 ` bugzilla-daemon
2020-09-06 10:07 ` bugzilla-daemon
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=bug-208267-208809-nsSo4ItjxH@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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).