public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Hans de Goede <hdegoede@redhat•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
	Mark Gross <mark.gross@intel•com>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux•intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the drivers-x86 tree
Date: Thu, 12 Aug 2021 09:40:21 +0200	[thread overview]
Message-ID: <1cb8dd94-a71b-aa91-3bed-365ce081dfd6@redhat.com> (raw)
In-Reply-To: <20210811081619.3d3434cb@canb.auug.org.au>

Hi,

On 8/11/21 12:16 AM, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   5c62c3d98b87 ("platform/x86: ISST: Fix optimization with use of numa")
> 
> Fixes tag
> 
>   Fixes: aa2ddd242572 ("ISST: Use numa node id for cpu pci dev mapping")
> 
> has these problem(s):
> 
>   - Subject does not match target commit subject
>     Just use
> 	git log -1 --format='Fixes: %h ("%s")'

Thanks, I've fixes this now and then a forced-push of the pdx86 for-next branch.

Question, is there some script which I can run on my own tree to catch
this (and similar issues) myself?  checkpatch does not catch this problem.

Regards,

Hans

next prev parent reply	other threads:[~2021-08-12  7:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 22:16 linux-next: Fixes tag needs some work in the drivers-x86 tree Stephen Rothwell
2021-08-12  7:40 ` Hans de Goede [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-18 21:06 Stephen Rothwell
2024-11-20 14:02 ` Hans de Goede
2022-03-01 21:17 Stephen Rothwell
2022-03-02 11:17 ` Hans de Goede
2021-11-01 21:37 Stephen Rothwell
2021-11-02 10:28 ` Hans de Goede
2021-03-08  6:06 Stephen Rothwell
2021-03-08 10:36 ` Hans de Goede
2020-11-29 17:43 Stephen Rothwell
2020-11-30  7:43 ` Hans de Goede
2020-11-30  7:58   ` Stephen Rothwell
2020-04-23 22:53 Stephen Rothwell
2020-04-24  9:46 ` Andy Shevchenko
2019-06-11 21:43 Stephen Rothwell
2019-04-16 21:33 Stephen Rothwell
2019-02-06 22:57 Stephen Rothwell
     [not found] ` <38152c55-c2c1-c89f-2751-0ef0d40fcba9@linux.intel.com>
2019-02-07 15:55   ` Andy Shevchenko
2019-02-13 15:15     ` Bhardwaj, Rajneesh
2019-02-21  0:40       ` Darren Hart
2019-02-21 13:36         ` Andy Shevchenko

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=1cb8dd94-a71b-aa91-3bed-365ce081dfd6@redhat.com \
    --to=hdegoede@redhat$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mark.gross@intel$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=srinivas.pandruvada@linux$(echo .)intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox