From: Andy Shevchenko <andy.shevchenko@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Darren Hart <dvhart@infradead•org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Archana Patni <archana.patni@intel•com>
Subject: Re: linux-next: Fixes tag needs some work in the drivers-x86 tree
Date: Fri, 24 Apr 2020 12:46:08 +0300 [thread overview]
Message-ID: <CAHp75VcHHQgt-vfGSnxBbHbRvH+zoXeMXkv8GKJNb-uJR+VJbQ@mail.gmail.com> (raw)
In-Reply-To: <20200424085315.36876e01@canb.auug.org.au>
On Fri, Apr 24, 2020 at 1:53 AM Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Hi all,
>
> In commit
>
> 92f62e696851 ("platform/x86: intel_pmc_core: Change Jasper Lake S0ix debug reg map back to ICL")
>
> Fixes tag
>
> Fixes: 16292bed9c ("platform/x86: intel_pmc_core: Add Atom based Jasper Lake (JSL) platform support")
>
> has these problem(s):
>
> - SHA1 should be at least 12 digits long
> Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
> or later) just making sure it is not set (or set to "auto").
Thanks, fixed now!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-04-24 9:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 22:53 linux-next: Fixes tag needs some work in the drivers-x86 tree Stephen Rothwell
2020-04-24 9:46 ` Andy Shevchenko [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-08-10 22:16 Stephen Rothwell
2021-08-12 7:40 ` 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
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=CAHp75VcHHQgt-vfGSnxBbHbRvH+zoXeMXkv8GKJNb-uJR+VJbQ@mail.gmail.com \
--to=andy.shevchenko@gmail$(echo .)com \
--cc=archana.patni@intel$(echo .)com \
--cc=dvhart@infradead$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--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