From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6058BC433EF for ; Tue, 21 Jun 2022 15:42:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1353095AbiFUPmU (ORCPT ); Tue, 21 Jun 2022 11:42:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52488 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1353106AbiFUPlc (ORCPT ); Tue, 21 Jun 2022 11:41:32 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 377EC2C109; Tue, 21 Jun 2022 08:41:22 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id D72E3B819FA; Tue, 21 Jun 2022 15:41:20 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D16E9C3411C; Tue, 21 Jun 2022 15:41:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1655826079; bh=8Ke5wnlYDkO5jPYi69LudjpjdoAfCY+krxfC23GY2ms=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=fwruP7zsGpMFJhfm8Non/bFVTOXtlqHamCiwlE9yJj/tQKuNZGvv2SLft8rd/961w 8ep7HcVCZuZt37AK3G4nJjtt0ftBxBvq3b9lnqr0Akjt4yy5/6vTiMy9vcHSo9z1LR IMtVs4ZaD8T/WmSxEbpcU9rIerz5lEcTTcBAGiyI= Date: Tue, 21 Jun 2022 17:41:16 +0200 From: Greg KH 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 Message-ID: References: <20220613114642.1615292-1-conor.dooley@microchip.com> <6c9001fa-5315-c9f4-b7b9-05248635750d@microchip.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <6c9001fa-5315-c9f4-b7b9-05248635750d@microchip.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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