From: Yaroslav Furman <yaro330@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: yaro330@gmail.com, Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, usb-storage@lists.one-eyed-alien.net,
linux-kernel@vger.kernel.org
Subject:
Date: Mon, 27 Mar 2023 16:54:22 +0300 [thread overview]
Message-ID: <20230327135423.607033-1-Yaroslav.Furman@verifone.com> (raw)
In-Reply-To: <ZA12pMgwA/8CguYd@kroah.com>
Will this patch get ported to LTS trees? It applies cleanly.
Would love to see it in 6.1 and 5.15 trees.
6.1 is what my steam deck is going to start using soon-ish.
next prev parent reply other threads:[~2023-03-27 13:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 12:34 [PATCH] uas: Add US_FL_NO_REPORT_OPCODES for JMicron JMS583Gen 2 Yaroslav Furman
2023-03-11 16:54 ` Alan Stern
2023-03-11 17:12 ` [PATCH v2] " Yaroslav Furman
2023-03-12 6:52 ` Greg Kroah-Hartman
2023-03-12 9:07 ` [PATCH v3] " Yaroslav Furman
2023-03-27 13:54 ` Yaroslav Furman [this message]
2023-03-27 13:54 ` Yaroslav Furman
2023-03-27 16:52 ` Greg Kroah-Hartman
2023-03-27 14:19 ` Greg Kroah-Hartman
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=20230327135423.607033-1-Yaroslav.Furman@verifone.com \
--to=yaro330@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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).