From: <Conor.Dooley@microchip.com>
To: <gregkh@linuxfoundation.org>
Cc: <b-liu@ti.com>, <Daire.McNamara@microchip.com>,
<Valentina.FernandezAlanis@microchip.com>,
<linux-kernel@vger.kernel.org>, <linux-usb@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <ben.dooks@codethink.co.uk>,
<heinrich.schuchardt@canonical.com>,
<Nicolas.Ferre@microchip.com>, <Cristian.Birsan@microchip.com>
Subject: Re: [PATCH v2 0/2] Add support for PolarFire SoC's musb controller
Date: Tue, 21 Jun 2022 15:28:12 +0000 [thread overview]
Message-ID: <ebeed0db-eb78-7f77-f4d8-93c7c7caab24@microchip.com> (raw)
In-Reply-To: <6c9001fa-5315-c9f4-b7b9-05248635750d@microchip.com>
On 21/06/2022 16:16, Conor Dooley - M52691 wrote:
>
>
> I can resend from an account that does pass DKIM if you like...
nvm, I see you've applied it.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-06-21 15:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 11:46 [PATCH v2 0/2] Add support for PolarFire SoC's musb controller Conor Dooley
2022-06-13 11:46 ` [PATCH v2 1/2] usb: musb: " Conor Dooley
2022-06-13 11:46 ` [PATCH v2 2/2] MAINTAINERS: add musb to PolarFire SoC entry Conor Dooley
2022-06-13 11:55 ` [PATCH v2 0/2] Add support for PolarFire SoC's musb controller Conor.Dooley
2022-06-21 14:36 ` Greg Kroah-Hartman
2022-06-21 15:16 ` Conor.Dooley
2022-06-21 15:28 ` Conor.Dooley [this message]
2022-06-21 15:41 ` Greg KH
2022-06-21 15:48 ` Conor.Dooley
2022-06-21 17:02 ` Greg KH
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=ebeed0db-eb78-7f77-f4d8-93c7c7caab24@microchip.com \
--to=conor.dooley@microchip.com \
--cc=Cristian.Birsan@microchip.com \
--cc=Daire.McNamara@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Valentina.FernandezAlanis@microchip.com \
--cc=b-liu@ti.com \
--cc=ben.dooks@codethink.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.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