From: Felipe Balbi <balbi@kernel.org>
To: "Schmid, Carsten" <Carsten_Schmid@mentor.com>
Cc: "Greg KH (gregkh@linuxfoundation.org)"
<gregkh@linuxfoundation.org>,
USB list <linux-usb@vger.kernel.org>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH for 4.14] xhci: add xhci_get_virt_ep() helper
Date: Mon, 26 Jul 2021 15:26:59 +0300 [thread overview]
Message-ID: <871r7luup8.fsf@kernel.org> (raw)
In-Reply-To: <bfeab6efc5b84cf38aa1c5436d9ce18b@SVR-IES-MBX-03.mgc.mentorg.com>
Hi,
Schmid, Carsten <Carsten_Schmid@mentor.com> writes:
>>> May I attach the patches as a file, generated with "git format-patch" meanwhile?
>>> I fear that I'm not allowed to use "git send-mail".
>>
>> For backports for the stable tree, yes, I can handle attachments just fine, you are not the only company with that problem :)
>>
> please find the patches attached.
> 0001-xhci-add-xhci_get_virt_sp-helper.patch.4 for 4.14 and 4.19
> 0001-xhci-add-xhci_get_virt_sp-helper.patch.5 for 5.4 and 5.10
>
> Applied and compiled, not tested.
> Added Cc: stable@vger.kernel.org in both patches.
Unfortunately, attachments will not do. You need to send the patches
themselves as the email. The easiest way is to configure (and rely) on
`git send-email', then it will do the right thing for you.
--
balbi
next prev parent reply other threads:[~2021-07-26 12:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 9:11 [PATCH for 4.14] xhci: add xhci_get_virt_ep() helper Schmid, Carsten
2021-07-26 9:19 ` Greg KH (gregkh@linuxfoundation.org)
2021-07-26 9:32 ` Schmid, Carsten
2021-07-26 10:05 ` Greg KH (gregkh@linuxfoundation.org)
2021-07-26 10:13 ` Schmid, Carsten
2021-07-26 10:16 ` Greg KH (gregkh@linuxfoundation.org)
2021-07-26 12:22 ` Schmid, Carsten
2021-07-26 12:26 ` Felipe Balbi [this message]
2021-07-26 12:51 ` Greg KH (gregkh@linuxfoundation.org)
2021-07-26 12:59 ` Greg KH (gregkh@linuxfoundation.org)
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=871r7luup8.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=Carsten_Schmid@mentor.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.