From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Ross Zwisler <zwisler@gmail.com>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>,
kernel test robot <fengguang.wu@intel.com>, LKP <lkp@01.org>,
LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
wfg@linux.intel.com
Subject: Re: [ppdev] e7223f1860: kernel BUG at drivers/base/driver.c:153!
Date: Thu, 3 Mar 2016 11:21:33 +0530 [thread overview]
Message-ID: <20160303055133.GA4152@sudip-pc> (raw)
In-Reply-To: <CAOxpaSVZRafSHiyDUUZ59uAydsw_kEv-JF=J9uDX0D7j_Lg1yQ@mail.gmail.com>
On Wed, Mar 02, 2016 at 02:24:22PM -0700, Ross Zwisler wrote:
> On Mon, Feb 15, 2016 at 4:50 AM, Sudip Mukherjee
> <sudipm.mukherjee@gmail.com> wrote:
> > On Mon, Feb 15, 2016 at 04:20:45PM +0800, kernel test robot wrote:
> >> Greetings,
> >>
> >> 0day kernel testing robot got the below dmesg and the first bad commit is
> >>
> >> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git char-misc-testing
> >>
> >> commit e7223f18603374d235d8bb0398532323e5f318b9
> >> Author: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
> >> AuthorDate: Fri Feb 12 18:33:45 2016 +0530
> >> Commit: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >> CommitDate: Sun Feb 14 17:43:50 2016 -0800
> >>
<snip>
>
> I've been hitting this error on my KVM system as well, and bisected to
> the same commit.
>
> The patch you have here solved the issue for me.
I will submit the patch today. I am sorry for the delay, i got held up
in some other things. Since you have tested this can I add your
Tested-by: to the patch?
regards
sudip
next prev parent reply other threads:[~2016-03-03 5:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 8:20 [ppdev] e7223f1860: kernel BUG at drivers/base/driver.c:153! kernel test robot
2016-02-15 11:50 ` Sudip Mukherjee
2016-03-02 21:24 ` Ross Zwisler
2016-03-03 5:51 ` Sudip Mukherjee [this message]
2016-03-03 15:36 ` Ross Zwisler
2016-03-24 14:41 ` Petr Mladek
2016-03-25 16:12 ` Linus Torvalds
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=20160303055133.GA4152@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ross.zwisler@linux.intel.com \
--cc=wfg@linux.intel.com \
--cc=zwisler@gmail.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