linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: bagasdotme@gmail.com
Cc: bhelgaas@google.com, corbet@lwn.net,
	darren@os.amperecomputing.com, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	patches@amperecomputing.com, shijie@os.amperecomputing.com,
	yangyicong@hisilicon.com, zwang@amperecomputing.com
Subject: Re: [PATCH v3] PCI: update the links for aer-inject git tree
Date: Fri, 5 Aug 2022 23:53:24 +0900	[thread overview]
Message-ID: <7c61db45-8e40-9918-ec7c-69a6deb8f71a@gmail.com> (raw)
In-Reply-To: <6556c478-976c-27f1-ad9b-606fe47f7ce1@gmail.com>

Fri, 5 Aug 2022 20:31:33 +0700, Bagas Sanjaya wrote:
> On 8/5/22 17:52, Huang Shijie wrote:
>> The aer-inject tree has been moved to:
>>     https://git.kernel.org/pub/scm/linux/kernel/git/gong.chen/aer-inject.git
>> Update the links.
>> 
>> Signed-off-by: Huang Shijie <shijie@os.amperecomputing.com>
>> ---
>> v1 --> v2: Modified the commit message and the title.
>> v2 --> v3: Change the commit message again.
>> ---
> 
> The change log could have been before the diffstat below (so it won't be
> displayed on git log when applied).
Are you sure Bagas?  :-)

>> Signed-off-by: Huang Shijie <shijie@os.amperecomputing.com>
>> ---

I guess this "---" should work as the end marker of changelog.

>> v1 --> v2: Modified the commit message and the title.
>> v2 --> v3: Change the commit message again.
>> ---

Another "---" here does no harm.

        Thanks, Akira

> 
>>  Documentation/PCI/pcieaer-howto.rst | 2 +-
>>  drivers/pci/pcie/Kconfig            | 2 +-
>>  drivers/pci/pcie/aer_inject.c       | 2 +-
>>  3 files changed, 3 insertions(+), 3 deletions(-)


  reply	other threads:[~2022-08-05 14:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05 10:52 [PATCH v3] PCI: update the links for aer-inject git tree Huang Shijie
2022-08-05 13:31 ` Bagas Sanjaya
2022-08-05 14:53   ` Akira Yokosawa [this message]
2022-09-27 23:47 ` Bjorn Helgaas
2022-09-28  1:31   ` Shijie Huang

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=7c61db45-8e40-9918-ec7c-69a6deb8f71a@gmail.com \
    --to=akiyks@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=corbet@lwn.net \
    --cc=darren@os.amperecomputing.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=patches@amperecomputing.com \
    --cc=shijie@os.amperecomputing.com \
    --cc=yangyicong@hisilicon.com \
    --cc=zwang@amperecomputing.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).