From: Sinan Kaya <okaya@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
"Rafael J. Wysocki" <rjw@rjwysocki•net>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Fixes tags need some work in the pm tree
Date: Tue, 15 Jan 2019 16:10:07 -0500 [thread overview]
Message-ID: <0f64417d-be5e-2939-7fc5-ee5ba26c64a6@kernel.org> (raw)
In-Reply-To: <20190116075540.78cff44e@canb.auug.org.au>
On 1/15/2019 3:55 PM, Stephen Rothwell wrote:
> [I am experimenting with checking the Fixes tags in commits in linux-next.
> Please let me know if you think I am being too strict.]
>
> Hi Rafael,
>
> Commits
>
> 62b33d57c534 ("drivers: thermal: int340x_thermal: Make PCI dependency explicit")
> cd793ab22a93 ("x86/intel/lpss: Make PCI dependency explicit")
> 42ac19e7b81e ("ACPI: EC: Look for ECDT EC after calling acpi_load_tables()")
> 6c29b81b5695 ("platform/x86: apple-gmux: Make PCI dependency explicit")
> 34783dc0182a ("platform/x86: intel_pmc: Make PCI dependency explicit")
> 704658d1d3ae ("platform/x86: intel_ips: make PCI dependency explicit")
> 5df37f3a1aa9 ("vga-switcheroo: make PCI dependency explicit")
> da1df6ee4296 ("ata: pata_acpi: Make PCI dependency explicit")
> ce97a22a596b ("ACPI / LPSS: Make PCI dependency explicit")
>
> Have malformed Fixes tags:
>
> There should be double quotes around the commit subject.
>
Interesting, can you add this to the checkpatch.pl script so that it doesn't
happen again?
next prev parent reply other threads:[~2019-01-15 21:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 20:55 linux-next: Fixes tags need some work in the pm tree Stephen Rothwell
2019-01-15 21:10 ` Sinan Kaya [this message]
2019-01-15 22:44 ` Stephen Rothwell
2019-01-15 22:13 ` Rafael J. Wysocki
2019-01-15 22:43 ` Stephen Rothwell
2019-01-15 23:06 ` Rafael J. Wysocki
2019-01-15 23:43 ` Michael Ellerman
2019-01-16 11:34 ` Rafael J. Wysocki
2019-01-16 0:22 ` Paul Gortmaker
2019-01-16 11:50 ` Rafael J. Wysocki
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=0f64417d-be5e-2939-7fc5-ee5ba26c64a6@kernel.org \
--to=okaya@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rjw@rjwysocki$(echo .)net \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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