From: Corey Minyard <minyard@acm.org>
To: lkp@lists.01.org
Subject: Re: [ipmi] BUG: key ffff880fcfc51ed0 not in .data!
Date: Wed, 17 Dec 2014 07:03:56 -0600 [thread overview]
Message-ID: <54917F3C.4090007@acm.org> (raw)
In-Reply-To: <CAADnVQLerROn=H=w0T29wt-wO=SbHaggrso_B7aGCajrAJ3TvA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
On 12/16/2014 07:05 PM, Alexei Starovoitov wrote:
> On Tue, Dec 16, 2014 at 5:08 AM, Corey Minyard <cminyard@mvista.com> wrote:
>> Yes, should be fixed by:
>>
>> commit 693726299ba87a6e267993806bc1320a266e5c5e
>> Author: Corey Minyard <cminyard@mvista.com>
>> Date: Fri Dec 12 19:06:07 2014 -0600
>>
>> ipmi: Finish cleanup of BMC attributes
>>
>> which should be in linux-next now. I was able to reproduce and verify
>> that this fixed it. I've verified that the branch is correct in the
>> repository.
> thanks. cleared the warning for me as well:
> Tested-by: Alexei Starovoitov <ast@plumgrid.com>
>
> Are you planning to send a pull request
> before the merge window is over or for rc2 ?
Yes, I believe I will. I was planning to wait until it was in
linux-next for a little while, but a "Tested-by" from you and Huang Ying
would give me more confidence :).
-corey
WARNING: multiple messages have this Message-ID (diff)
From: Corey Minyard <minyard@acm.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Corey Minyard <cminyard@mvista.com>
Cc: Huang Ying <ying.huang@intel.com>,
LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>,
Huang Ying <ying.huang@intel.com>
Subject: Re: [LKP] [ipmi] BUG: key ffff880fcfc51ed0 not in .data!
Date: Wed, 17 Dec 2014 07:03:56 -0600 [thread overview]
Message-ID: <54917F3C.4090007@acm.org> (raw)
In-Reply-To: <CAADnVQLerROn=H=w0T29wt-wO=SbHaggrso_B7aGCajrAJ3TvA@mail.gmail.com>
On 12/16/2014 07:05 PM, Alexei Starovoitov wrote:
> On Tue, Dec 16, 2014 at 5:08 AM, Corey Minyard <cminyard@mvista.com> wrote:
>> Yes, should be fixed by:
>>
>> commit 693726299ba87a6e267993806bc1320a266e5c5e
>> Author: Corey Minyard <cminyard@mvista.com>
>> Date: Fri Dec 12 19:06:07 2014 -0600
>>
>> ipmi: Finish cleanup of BMC attributes
>>
>> which should be in linux-next now. I was able to reproduce and verify
>> that this fixed it. I've verified that the branch is correct in the
>> repository.
> thanks. cleared the warning for me as well:
> Tested-by: Alexei Starovoitov <ast@plumgrid.com>
>
> Are you planning to send a pull request
> before the merge window is over or for rc2 ?
Yes, I believe I will. I was planning to wait until it was in
linux-next for a little while, but a "Tested-by" from you and Huang Ying
would give me more confidence :).
-corey
next prev parent reply other threads:[~2014-12-17 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 1:05 [ipmi] BUG: key ffff880fcfc51ed0 not in .data! Alexei Starovoitov
2014-12-17 1:05 ` [LKP] " Alexei Starovoitov
2014-12-17 13:03 ` Corey Minyard [this message]
2014-12-17 13:03 ` Corey Minyard
-- strict thread matches above, loose matches on Subject: below --
2014-12-12 3:20 Huang Ying
2014-12-13 4:04 ` Corey Minyard
2014-12-16 2:53 ` Alexei Starovoitov
2014-12-16 13:08 ` Corey Minyard
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=54917F3C.4090007@acm.org \
--to=minyard@acm.org \
--cc=lkp@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.