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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 8ABDBCDB465 for ; Mon, 16 Oct 2023 16:12:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=bvV2JMV7WaJmo7nsLn12+BYaEU+Whqys21536B1xRME=; b=DFRzg3as2YyUh4 UTF+TnX0EhxaFktQgB72WXaJySVJUOjsJdj5pciMD2sT8cRzhRSXNNRlUhAatZFKkC8ziMK8utsFD F8zqHqJNyFr1sUJShcRAQRMXU9UaVUHZ4xZrw/m/oLw//nGpQg1NZKXbiAJ3pqEQKe6cV6cVKQf8v hs+FsqWTQyg0WHVTbx3YISl2EKzeVjZkFHmOmoz/Gu5rnbTBCnwkD8UTGlbQjDK2KZPCVC/HYFTlg 28FPSjFpXA2/R4xpBKzIj/ry58uovZhzuglbmQ190pySZnEP7853nr0STN5gnHz051anbbxK/0RTl sD5Zi2AvtG5w8l4LkJ9g==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qsQCe-00A692-29; Mon, 16 Oct 2023 16:12:24 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qsQCb-00A688-2L for linux-arm-kernel@lists.infradead.org; Mon, 16 Oct 2023 16:12:23 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id C44ED61044; Mon, 16 Oct 2023 16:12:20 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 21664C433CC; Mon, 16 Oct 2023 16:12:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1697472740; bh=UOk9dtIEA+SLfxItNT20g2iHH2uvRS1QFVWkFm9awB0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ddHMmPgPAUtIgmqdMMJEsjIwdwQRoIXq7wSAFAgW5yk11YzFGUD+Oes7KS1+c5cEp wTdwPgo1q34tsG61ez6FbaHoV1M8/SKTMCYEJJfpwHq2SR9nho3sfNdGC4WrPGTFpo 8GTW9ZkTdCJMlYkpeTgESIISHx6okF/KEdxOgaEn7Z4YwuhVPNcidx5lf93YV44oj7 DtIzOdCVN8Y1kBWt3NsFk2GnL7uJdWfmlCPRB2nyxCLVQB6WjHs+uxwctVVZthcrTL i35aEm5+e9kh59nrPbuHEMA5ACMlnCfjY2TBa6k9jqElF+IM/x4p6V4PwcrrBrbLlX ic7lNkRj27LqA== Date: Mon, 16 Oct 2023 18:12:13 +0200 From: Lorenzo Pieralisi To: Bjorn Helgaas Cc: Frank Li , Minghuan Lian , Mingkai Hu , Roy Zang , Krzysztof =?utf-8?Q?Wilczy=C5=84ski?= , Rob Herring , Bjorn Helgaas , "open list:PCI DRIVER FOR FREESCALE LAYERSCAPE" , "open list:PCI DRIVER FOR FREESCALE LAYERSCAPE" , "moderated list:PCI DRIVER FOR FREESCALE LAYERSCAPE" , open list , imx@lists.linux.dev Subject: Re: [PATCH 2/3] PCI: layerscape: add suspend/resume for ls1021a Message-ID: References: <20231016152211.GA1209639@bhelgaas> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20231016152211.GA1209639@bhelgaas> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231016_091221_871715_EA3417B8 X-CRM114-Status: GOOD ( 28.33 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, Oct 16, 2023 at 10:22:11AM -0500, Bjorn Helgaas wrote: > On Mon, Oct 16, 2023 at 10:45:25AM -0400, Frank Li wrote: > > On Tue, Oct 10, 2023 at 06:02:36PM +0200, Lorenzo Pieralisi wrote: > > > On Tue, Oct 10, 2023 at 10:20:12AM -0400, Frank Li wrote: > > > > > Ping > > > > > > Read and follow please (and then ping us): > > > https://lore.kernel.org/linux-pci/20171026223701.GA25649@bhelgaas-glaptop.roam.corp.google.com > > > > Could you please help point which specic one was not follow aboved guide? > > Then I can update my code. I think that's efficial communication method. I > > think I have read it serial times. But not sure which one violate the > > guide? > > > > @Bjorn Helgaas. How do you think so? > > Since Lorenzo didn't point out anything specific in the patch itself, > I think he was probably referring to the subject line and this advice: > > - Follow the existing convention, i.e., run "git log --oneline > " and make yours match in format, capitalization, and > sentence structure. For example, native host bridge driver patch > titles look like this: > > PCI: altera: Fix platform_get_irq() error handling > PCI: vmd: Remove IRQ affinity so we can allocate more IRQs > PCI: mediatek: Add MSI support for MT2712 and MT7622 > PCI: rockchip: Remove IRQ domain if probe fails > > In this case, your subject line was: > > PCI: layerscape: add suspend/resume for ls1021a > > The advice was to run this: > > $ git log --oneline drivers/pci/controller/dwc/pci-layerscape.c > 83c088148c8e PCI: Use PCI_HEADER_TYPE_* instead of literals > 9fda4d09905d PCI: layerscape: Add power management support for ls1028a > 277004d7a4a3 PCI: Remove unnecessary includes > 60b3c27fb9b9 PCI: dwc: Rename struct pcie_port to dw_pcie_rp > d23f0c11aca2 PCI: layerscape: Change to use the DWC common link-up check function > 7007b745a508 PCI: layerscape: Convert to builtin_platform_driver() > 60f5b73fa0f2 PCI: dwc: Remove unnecessary wrappers around dw_pcie_host_init() > b9ac0f9dc8ea PCI: dwc: Move dw_pcie_setup_rc() to DWC common code > f78f02638af5 PCI: dwc: Rework MSI initialization > > Note that these summaries are all complete sentences that start with a > capital letter: > > Use PCI_HEADER_TYPE_* instead of literals > Add power management support for ls1028a > Remove unnecessary includes > ... > > So yours could be this: > > PCI: layerscape: Add suspend/resume for ls1021a > ^ > > This is trivial, obviously. But the uppercase/lowercase distinction > carries information, and it's an unnecessary distraction to notice > that "oh, this is different from the rest; is the difference > important or should I ignore it?" > > Obviously Lorenzo *could* edit all your subject lines on your behalf, > but it makes everybody's life easier if people look at the existing > code and follow the style when making changes. > > E.g., write subject lines that are similar in style to previous ones, > name local variables similarly to other functions, use line lengths > consistent with the rest of the file, etc. After applying a change, > the file should look like a coherent whole; we should not be able to > tell that this hunk was added later by somebody else. This all helps > make the code (and the git history) more readable and maintainable. Thank you very much Bjorn. Frank, now please resend your patches and make sure that you follow these guidelines, they must be clear by now. Lorenzo _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel