public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Huang Ying <ying.huang@intel.com>,
	LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [LKP] [x86/cacheinfo] 0d55ba46bfb: WARNING: CPU: 31 PID: 1 at fs/sysfs/group.c:102 internal_create_group+0x151/0x280()
Date: Thu, 19 Mar 2015 10:55:52 +0100	[thread overview]
Message-ID: <20150319095552.GB11544@pd.tnic> (raw)
In-Reply-To: <550A9799.2080404@arm.com>

On Thu, Mar 19, 2015 at 09:32:09AM +0000, Sudeep Holla wrote:
> IIUC, a modified version(as per the discussion on that thread) of the
> patch[1] posted a while ago fixed this issue. I had assumed Boris had
> pulled, but seem to have missed. Boris, is that right ?

Yes it is. It will land in tip soon.

Thanks guys.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--

      reply	other threads:[~2015-03-19  9:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19  2:28 [LKP] [x86/cacheinfo] 0d55ba46bfb: WARNING: CPU: 31 PID: 1 at fs/sysfs/group.c:102 internal_create_group+0x151/0x280() Huang Ying
2015-03-19  9:32 ` Sudeep Holla
2015-03-19  9:55   ` Borislav Petkov [this message]

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=20150319095552.GB11544@pd.tnic \
    --to=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=sudeep.holla@arm.com \
    --cc=ying.huang@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