From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rajneesh Bhardwaj <rajneesh.bhardwaj@linux.intel.com>
Subject: linux-next: Fixes tag needs some work in the drivers-x86 tree
Date: Thu, 7 Feb 2019 09:57:03 +1100 [thread overview]
Message-ID: <20190207095703.564e76b2@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 398 bytes --]
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")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-02-06 22:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 22:57 Stephen Rothwell [this message]
[not found] ` <38152c55-c2c1-c89f-2751-0ef0d40fcba9@linux.intel.com>
2019-02-07 15:55 ` linux-next: Fixes tag needs some work in the drivers-x86 tree Andy Shevchenko
2019-02-13 15:15 ` Bhardwaj, Rajneesh
2019-02-21 0:40 ` Darren Hart
2019-02-21 13:36 ` Andy Shevchenko
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
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=20190207095703.564e76b2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andy.shevchenko@gmail.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rajneesh.bhardwaj@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).