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 58977CDB465 for ; Mon, 16 Oct 2023 16:25:46 +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: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:References: List-Owner; bh=lQsnFQrkX6tAAff0igYZhocYnVLlp36I9SWpfo+g+7E=; b=NgyxcQaf0GhJUe YdXAMLJCnZghZQYmUKP/UX+hTYOChvca7Xj56L491a+wOaB2Z5fQv+bFi2akNhFkZzR6P4rPtMJ0r JWXUaSpTnbriVdVHeaKLFKxu2IQcrHHrw7xSGYYpIBVQo1wENC11qBN6laSz9cDPZECj7mvanVmcJ 2gx5oNcd7l3Ky9C+18XCi3atK4rJKHFZCtrihe2yrczaHb+LqFI9qQLeJ/8GENPkGVXEtjjMgwJW7 HBnJhsOC+yrPTqmLs9Kp04OTb2i29J+VL3jq+BLyquC3UqGQtpaJOi5QScm99QkZNpPmrnCwe9LWo lKnuwmzvphpv5hoLdNVQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qsQPB-00A7sI-26; Mon, 16 Oct 2023 16:25:21 +0000 Received: from sin.source.kernel.org ([145.40.73.55]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qsQP8-00A7rq-1U for linux-arm-kernel@lists.infradead.org; Mon, 16 Oct 2023 16:25:20 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id 8DBF3CE1711; Mon, 16 Oct 2023 16:25:16 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5E4E9C433C8; Mon, 16 Oct 2023 16:25:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1697473515; bh=9/hvt23CkWCSd3t6m1C0dNGRoz/pDYrD0zUCEPxSYzc=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=kiSnPKMNWSc95QJN5Az/vICl/XNckWm+QRY8UKi+Q+sgo8Kd1v1mfRpTIZLxZLbUk l5F8vNrg1UbMfoa4oRxpvtjO1rkGvCGVfIhxta/gcuOkdYZ/hE7oXDLHxlok/gn5yI XTPh/f6xrE1xZ/5JuAKxAYsbR+DOPQzzrnr4+VX8dNMbEo3O/OlVESsC9mo2iFmV8Q MciK2/Nq/ach9GVBOF97X9rCnLqxQEYsTczGmFw93BX1W4N1XGLr1gpydUVV7EofJR wAtIZ6+TuoliVQwBK7n0klE/d7D4yWx2gw4Gl8tp57B4ZDVmQRHWMJGRCeHO6pIwnX S8KWc+1PpKGHQ== Date: Mon, 16 Oct 2023 11:25:12 -0500 From: Bjorn Helgaas To: Frank Li Cc: Krzysztof =?utf-8?Q?Wilczy=C5=84ski?= , imx@lists.linux.dev, Rob Herring , "open list:PCI DRIVER FOR FREESCALE LAYERSCAPE" , Lorenzo Pieralisi , open list , Minghuan Lian , "moderated list:PCI DRIVER FOR FREESCALE LAYERSCAPE" , Roy Zang , Bjorn Helgaas , "open list:PCI DRIVER FOR FREESCALE LAYERSCAPE" , Mingkai Hu Subject: Re: [PATCH 2/3] PCI: layerscape: add suspend/resume for ls1021a Message-ID: <20231016162512.GA1212231@bhelgaas> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231016_092518_673901_62C67D27 X-CRM114-Status: GOOD ( 14.91 ) 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 12:11:04PM -0400, Frank Li wrote: > On Mon, Oct 16, 2023 at 10:22:11AM -0500, Bjorn Helgaas wrote: > > 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. > > Understand, but simple mark 'a' and 'A' to me. I will update patches and > take care for next time instead search whole docuemnt to guess which one > violated. I know I make some mistakes at here. But I am working on many > difference kernel subsystems, some require upper case, some require low > case, someone doesn't care. Right, that's why I always suggest following the example of the surrounding code and history. English is the only language I know, but I speculate that this typographical detail probably doesn't make sense in languages that don't have a similar upper/lowercase distinction. Thanks for persevering; we'd be having a lot more trouble if I tried to send emails in your native language ;) Bjorn _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel