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 6EBA7C43334 for ; Fri, 8 Jul 2022 08:01:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237466AbiGHIBf (ORCPT ); Fri, 8 Jul 2022 04:01:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36006 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237491AbiGHIBb (ORCPT ); Fri, 8 Jul 2022 04:01:31 -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 6A0717E01F; Fri, 8 Jul 2022 01:01:30 -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 A80C7B824C3; Fri, 8 Jul 2022 08:01:28 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5F63DC341C8; Fri, 8 Jul 2022 08:01:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1657267287; bh=A/e4amBcKWeEZysL+s9cf7FK4eenhjcZ/1xT4QWPuqI=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=T4zwtyGcDb0Ny/O6g2O72Ub/1M4Rr7wdb6dY8isykavoXUliaMnhW03+lDuxCFDA7 8NAlBOAfFoPjev5Sk/nM4EWh/dLSOkvNrBPjYA2blrJbiGky2yJdIbECI0Alz4ZL9o lxYQBS70343LhpueOZdptjUbQ9vecBfCLddat5dN3TLmhh2ZtGuiRenygQ7IFaqYEZ /TCoMTEsP6KzhH70bp6An2DWGL37oefWXwW36Y8gXMyvLuo54tjX3Mmplnu9LdMkbf cRvG6h1MlkJunsXS4yW+9o5XOHwSl4wetbb71/7A+OBeMw8BGP7S566TuEsNM0Yqe9 CTVpoINKGU7zw== Received: from [213.208.244.172] (helo=wait-a-minute.misterjones.org) by disco-boy.misterjones.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1o9ivV-0065vk-1t; Fri, 08 Jul 2022 09:01:25 +0100 Date: Fri, 08 Jul 2022 09:01:23 +0100 Message-ID: <87tu7skp7w.wl-maz@kernel.org> From: Marc Zyngier To: Frank Li Cc: tglx@linutronix.de, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org, s.hauer@pengutronix.de, kw@linux.com, bhelgaas@google.com, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org, peng.fan@nxp.com, aisheng.dong@nxp.com, jdmason@kudzu.us, kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com, kishon@ti.com, lorenzo.pieralisi@arm.com, ntb@lists.linux.dev Subject: Re: [PATCH 1/3] irqchip: imx mu worked as msi controller In-Reply-To: <20220707210238.917477-1-Frank.Li@nxp.com> References: <20220707210238.917477-1-Frank.Li@nxp.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/27.1 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-SA-Exim-Connect-IP: 213.208.244.172 X-SA-Exim-Rcpt-To: Frank.Li@nxp.com, tglx@linutronix.de, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org, s.hauer@pengutronix.de, kw@linux.com, bhelgaas@google.com, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org, peng.fan@nxp.com, aisheng.dong@nxp.com, jdmason@kudzu.us, kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com, kishon@ti.com, lorenzo.pieralisi@arm.com, ntb@lists.linux.dev X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Thu, 07 Jul 2022 22:02:36 +0100, Frank Li wrote: > > MU support generate irq by write data to a register. > This patch make mu worked as msi controller. > So MU can do doorbell by using standard msi api. > > Signed-off-by: Frank Li Where is the cover letter for this? How am I supposed to guess what this series is about? The rule is simple: you send a series with two patches or more, you include a cover letter describing your changes, what they provide, and how they interact with each other. Here, all I see is a bunch of seemingly unrelated changes. I could spend the next 2 hours trying to reverse engineer it, but it is probably a lot quicker for you to write an actual cover letter and send it for everyone's benefit. Thanks, M. -- Without deviation from the norm, progress is not possible.