From: Chris Wulff <Chris.Wulff@biamp.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH] usb: gadget: f_fs: add capability for dfu run-time descriptor
Date: Thu, 18 Apr 2024 20:21:44 +0000 [thread overview]
Message-ID: <CO1PR17MB54194DF99B71D28759E46B98E10E2@CO1PR17MB5419.namprd17.prod.outlook.com> (raw)
In-Reply-To: <CO1PR17MB5419DFDED866D65B3715AC31E10E2@CO1PR17MB5419.namprd17.prod.outlook.com>
> I assume I should remove those old sign-offs as I can attest to the suitable history?
I answered my own question. I missed the section on co-developed in
https://www.kernel.org/doc/html/latest/process/submitting-patches.html
I will submit a new patch with the attribution corrected.
prev parent reply other threads:[~2024-04-18 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 20:15 [PATCH] usb: gadget: f_fs: add capability for dfu run-time descriptor Chris Wulff
2024-04-18 14:41 ` Greg KH
2024-04-18 15:18 ` Chris Wulff
2024-04-18 20:21 ` Chris Wulff [this message]
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=CO1PR17MB54194DF99B71D28759E46B98E10E2@CO1PR17MB5419.namprd17.prod.outlook.com \
--to=chris.wulff@biamp.com \
--cc=gregkh@linuxfoundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).