All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Timothy Pearson <tpearson@raptorengineering.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	linux-pci <linux-pci@vger.kernel.org>,
	mahesh <mahesh@linux.ibm.com>, Oliver <oohall@gmail.com>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>,
	Shawn Anastasio <sanastasio@raptorengineering.com>
Subject: Re: [PATCH v10] PCI: Add pcie_link_is_active() function
Date: Thu, 19 Jun 2025 15:55:37 +0200	[thread overview]
Message-ID: <aFQW2aDZa9DhxBPG@wunner.de> (raw)
In-Reply-To: <988492931.1308196.1750174918075.JavaMail.zimbra@raptorengineeringinc.com>

[cc += Krishna, Shawn]

On Tue, Jun 17, 2025 at 10:41:58AM -0500, Timothy Pearson wrote:
> Add pcie_link_is_active() function to check if the physical PCIe link is
> active, replacing duplicate code in multiple locations.
> 
> Signed-off-by: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
> Signed-off-by: Shawn Anastasio <sanastasio@raptorengineering.com>
> Signed-off-by: Timothy Pearson <tpearson@raptorengineering.com>

I note that there's a Signed-off-by tag for Krishna here,
but Krishna isn't cc'ed.  In future revisions please cc
everyone you're tagging.

Also, if the vast majority of the patch has originally
been authored by Krishna, please give credit to Krishna
by including a From: header at the top of the message body
(as you've done in v9).

Thanks,

Lukas

  parent reply	other threads:[~2025-06-19 13:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17 15:41 [PATCH v10] PCI: Add pcie_link_is_active() function Timothy Pearson
2025-06-17 16:04 ` Bjorn Helgaas
2025-06-17 16:10   ` Timothy Pearson
2025-06-17 18:59     ` Bjorn Helgaas
2025-06-17 19:19       ` Timothy Pearson
2025-06-17 20:02         ` Bjorn Helgaas
2025-06-17 16:16 ` Timothy Pearson
2025-06-19 13:55 ` Lukas Wunner [this message]
2025-08-26  7:04 ` Krishna Chaitanya Chundru
2025-08-26 12:48   ` Timothy Pearson

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=aFQW2aDZa9DhxBPG@wunner.de \
    --to=lukas@wunner.de \
    --cc=helgaas@kernel.org \
    --cc=krishna.chundru@oss.qualcomm.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=maddy@linux.ibm.com \
    --cc=mahesh@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=oohall@gmail.com \
    --cc=sanastasio@raptorengineering.com \
    --cc=tpearson@raptorengineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.