From: Greg KH <gregkh@linuxfoundation.org>
To: Conor.Dooley@microchip.com
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 17:41:16 +0200 [thread overview]
Message-ID: <YrHmnND30o1Rjmcp@kroah.com> (raw)
In-Reply-To: <6c9001fa-5315-c9f4-b7b9-05248635750d@microchip.com>
On Tue, Jun 21, 2022 at 03:16:49PM +0000, Conor.Dooley@microchip.com wrote:
>
>
> On 21/06/2022 15:36, Greg Kroah-Hartman wrote:
> > On Mon, Jun 13, 2022 at 12:46:41PM +0100, Conor Dooley wrote:
> >> Hey Bin, Greg,
> >> Short series here adding support for USB on Microchip PolarFire SoC FPGAs.
> >> The kconfig dependency for INVENTRA_DMA has become a bit of a mouthful,
> >> is there a better way of dealing with that?
> >> Thanks,
> >> Conor.
> >>
> >> Changes since v1:
> >> - Drop unneeded resource copying as per Rob's changes to the other drivers
> >> - Drop the dts patch
> >>
> >> Conor Dooley (2):
> >> usb: musb: Add support for PolarFire SoC's musb controller
> >> MAINTAINERS: add musb to PolarFire SoC entry
> >>
> >> MAINTAINERS | 1 +
> >> drivers/usb/musb/Kconfig | 13 +-
> >> drivers/usb/musb/Makefile | 1 +
> >> drivers/usb/musb/mpfs.c | 265 ++++++++++++++++++++++++++++++++++++++
> >> 4 files changed, 279 insertions(+), 1 deletion(-)
> >> create mode 100644 drivers/usb/musb/mpfs.c
> >>
> >>
> >> base-commit: f2906aa863381afb0015a9eb7fefad885d4e5a56
> >> --
> >> 2.36.1
> >>
> >
> > Any chance you can get your company to fix up their email settings:
> >
> > Grabbing thread from lore.kernel.org/all/20220613114642.1615292-1-conor.dooley%40microchip.com/t.mbox.gz
> > Analyzing 4 messages in the thread
> > Checking attestation on all messages, may take a moment...
> > ---
> > ✗ [PATCH v2 1/2] usb: musb: Add support for PolarFire SoC's musb controller
> > ✗ [PATCH v2 2/2] MAINTAINERS: add musb to PolarFire SoC entry
> > ---
> > ✗ BADSIG: DKIM/microchip.com
> > ---
> > Total patches: 2
> >
> > If I didn't know better, I would think you were spoofing the address...
>
> Great, thanks. I was honestly hoping you would make this complaint.
> I brought it up with our IT before & nothing has happened yet.
It's amazing that your company emails are even making it to many systems
these days with that broken.
> At least now I have the direct complaint to forward :)
Please do, and tell them that in the future, some of us will probably
start requiring this to pass as I doubt they want just anyone to spoof
patches from your domain :)
thanks,
greg k-h
next prev parent reply other threads:[~2022-06-21 15:42 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
2022-06-21 15:41 ` Greg KH [this message]
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=YrHmnND30o1Rjmcp@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=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=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