From: "Bhardwaj, Rajneesh" <rajneesh.bhardwaj@linux•intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Darren Hart <dvhart@infradead•org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the drivers-x86 tree
Date: Wed, 13 Feb 2019 20:45:56 +0530 [thread overview]
Message-ID: <e0c40627-f1a2-254f-14b0-b9df0d62dd34@linux.intel.com> (raw)
In-Reply-To: <CAHp75Vf6gs1342N16MZHvPmiiv3+xJyMyyJQK677KPZbb_7Vrg@mail.gmail.com>
On 07-Feb-19 9:25 PM, Andy Shevchenko wrote:
> On Thu, Feb 7, 2019 at 4:06 AM Bhardwaj, Rajneesh
> <rajneesh.bhardwaj@linux•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?
Hi Andy, I have corrected this in v2 anyway and i sent to upstream
today, just in case you prefer it over rebasing.
https://patchwork.kernel.org/patch/10810123/
>
next prev parent reply other threads:[~2019-02-13 15:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 22:57 linux-next: Fixes tag needs some work in the drivers-x86 tree 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 [this message]
2019-02-21 0:40 ` Darren Hart
2019-02-21 13:36 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2019-04-16 21:33 Stephen Rothwell
2019-06-11 21:43 Stephen Rothwell
2020-04-23 22:53 Stephen Rothwell
2020-04-24 9:46 ` Andy Shevchenko
2020-11-29 17:43 Stephen Rothwell
2020-11-30 7:43 ` Hans de Goede
2020-11-30 7:58 ` Stephen Rothwell
2021-03-08 6:06 Stephen Rothwell
2021-03-08 10:36 ` Hans de Goede
2021-08-10 22:16 Stephen Rothwell
2021-08-12 7:40 ` Hans de Goede
2021-11-01 21:37 Stephen Rothwell
2021-11-02 10:28 ` Hans de Goede
2022-03-01 21:17 Stephen Rothwell
2022-03-02 11:17 ` Hans de Goede
2024-11-18 21:06 Stephen Rothwell
2024-11-20 14:02 ` Hans de Goede
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=e0c40627-f1a2-254f-14b0-b9df0d62dd34@linux.intel.com \
--to=rajneesh.bhardwaj@linux$(echo .)intel.com \
--cc=andy.shevchenko@gmail$(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