From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dinghao Liu <dinghao.liu@zju.edu.cn>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: linux-next: Fixes tag needs some work in the pci tree
Date: Wed, 22 Jul 2020 10:33:50 +1000 [thread overview]
Message-ID: <20200722103350.6bfb8da6@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 499 bytes --]
Hi all,
In commit
769785cebe0f ("PCI: rcar: Fix runtime PM imbalance on error")
Fixes tag
Fixes: 0df6150e7ceb ("PCI: rcar: Use runtime PM to control controller
has these problem(s):
- Subject has leading but no trailing parentheses
- Subject has leading but no trailing quotes
Please do not split Fixes tags over more than one line. Loooks like the
lines also were rearranged - the end of the fixes line is 2 lines above
the rest.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-07-22 0:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 0:33 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-15 21:14 linux-next: Fixes tag needs some work in the pci tree Stephen Rothwell
2023-01-16 3:23 ` Alexey V. Vissarionov
2023-01-18 17:06 ` Bjorn Helgaas
2020-11-22 9:55 Stephen Rothwell
2020-11-22 15:13 ` Bjorn Helgaas
2020-03-30 20:38 Stephen Rothwell
2020-03-30 20:53 ` Bjorn Helgaas
2020-03-31 3:14 ` Lukas Wunner
2020-03-31 3:32 ` Lukas Wunner
2020-03-31 15:32 ` Bjorn Helgaas
2019-06-22 13:40 Stephen Rothwell
2019-06-26 10:00 ` Lorenzo Pieralisi
2019-06-26 14:51 ` Bharat Kumar Gogada
2019-02-12 23:03 Stephen Rothwell
2019-02-13 9:55 ` Lorenzo Pieralisi
2019-02-13 14:31 ` Bjorn Helgaas
2019-02-13 20:09 ` Stephen Rothwell
2019-02-13 20:19 ` Bjorn Helgaas
2019-02-13 21:17 ` Stephen Rothwell
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=20200722103350.6bfb8da6@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bhelgaas@google.com \
--cc=dinghao.liu@zju.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.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).