[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vf6gs1342N16MZHvPmiiv3+xJyMyyJQK677KPZbb_7Vrg@mail.gmail.com>
Date: Thu, 7 Feb 2019 17:55:46 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: "Bhardwaj, Rajneesh" <rajneesh.bhardwaj@...ux.intel.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Darren Hart <dvhart@...radead.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the drivers-x86 tree
On Thu, Feb 7, 2019 at 4:06 AM Bhardwaj, Rajneesh
<rajneesh.bhardwaj@...ux.intel.com> wrote:
> On 07-Feb-19 4:27 AM, Stephen Rothwell wrote:
>
> Hi all,
>
> In commit
>
> 4284dc008f43 ("platform/x86: intel_pmc_core: Fix file permissions for ltr_show")
>
> Fixes tag
>
> Fixes: 63cde0c16c67 ("platform/x86: intel_pmc_core: Show Latency Tolerance info")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Did you mean:
>
> 2eb150558bb7 ("platform/x86: intel_pmc_core: Show Latency Tolerance info")
>
> Yes, upstream commit is 2eb150558bb79ee01c39b64c2868216c0be2904f. For some reason when i do git show on my repo with both these SHA1 i see the same patch.
>
> I will fix this in next version.
Hmm... this came to our published branch, i.e. for-next, would it be
better to update it via rebasing?
Darren, what do you think?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists