linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Thippeswamy Havalige <thippeswamy.havalige@amd.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, krzysztof.kozlowski@linaro.org,
	bhelgaas@google.com, michals@xilinx.com, robh+dt@kernel.org,
	nagaradhesh.yeleswarapu@amd.com, bharat.kumar.gogada@amd.com,
	lorenzo.pieralisi@arm.com
Subject: Re: [PATCH v2 1/3] Move error interrupt bits to a common header.
Date: Fri, 12 May 2023 14:23:08 -0500	[thread overview]
Message-ID: <ZF6SHJ44s4OqPYj4@bhelgaas> (raw)
In-Reply-To: <20230512062725.1208385-2-thippeswamy.havalige@amd.com>

Update subject line to follow convention.  Run "git log --oneline
drivers/pci/controller/pcie-xilinx*" for a sample.  No period at end.

On Fri, May 12, 2023 at 11:57:23AM +0530, Thippeswamy Havalige wrote:
> Moving error interrupt bit macros to a common header file for code
> reusability.

"Move" as in subject.

Bjorn

  parent reply	other threads:[~2023-05-12 19:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12  6:27 [PATCH v2 0/3] Add support for Xilinx XDMA Soft IP as Root Port Thippeswamy Havalige
2023-05-12  6:27 ` [PATCH v2 1/3] Move error interrupt bits to a common header Thippeswamy Havalige
2023-05-12  6:45   ` Michal Simek
2023-05-12 19:23   ` Bjorn Helgaas [this message]
2023-05-12  6:27 ` [PATCH v2 2/3] dt-bindings: PCI: xilinx-xdma: Add YAML schemas for Xilinx XDMA PCIe Root Port Bridge Thippeswamy Havalige
2023-05-12  6:50   ` Michal Simek
2023-05-12 11:26   ` Krzysztof Kozlowski
2023-05-12  6:27 ` [PATCH v2 3/3] PCI: xilinx-xdma: Add Xilinx XDMA Root Port driver Thippeswamy Havalige
2023-05-12  7:04   ` Michal Simek
2023-05-12 17:43   ` Bjorn Helgaas
2023-05-18  4:55     ` Havalige, Thippeswamy
2023-05-12 19:32   ` Bjorn Helgaas
2023-05-18  4:58     ` Havalige, Thippeswamy

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=ZF6SHJ44s4OqPYj4@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bharat.kumar.gogada@amd.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=michals@xilinx.com \
    --cc=nagaradhesh.yeleswarapu@amd.com \
    --cc=robh+dt@kernel.org \
    --cc=thippeswamy.havalige@amd.com \
    /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;
as well as URLs for NNTP newsgroup(s).