From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: lkp@lists.01.org
Subject: Re: [i2c] 95026658c4: WARNING: CPU: 0 PID: 1 at drivers/i2c/i2c-core.c:1930 i2c_register_driver+0x2c/0x79()
Date: Mon, 14 Mar 2016 19:45:19 +0530 [thread overview]
Message-ID: <20160314141519.GA5699@sudip-laptop> (raw)
In-Reply-To: <20160314011419.GA2308@katana>
[-- Attachment #1: Type: text/plain, Size: 597 bytes --]
On Mon, Mar 14, 2016 at 02:14:19AM +0100, Wolfram Sang wrote:
> On Mon, Mar 14, 2016 at 08:47:59AM +0800, kernel test robot wrote:
> > FYI, we noticed the below changes on
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux i2c/for-next
> > commit 95026658c46ea2d94498d0dac1282e28cd47c64a ("i2c: do not use internal data from driver core")
>
> Ouch! So nobody of us ever boot-tested this patch? :(
No. Sorry. It was only compile tested but Fengguang sent me the warning
before you applied the patch but I was travelling and so could not do anything.
regards
sudip
WARNING: multiple messages have this Message-ID (diff)
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: kernel test robot <ying.huang@linux.intel.com>,
lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
Subject: Re: [lkp] [i2c] 95026658c4: WARNING: CPU: 0 PID: 1 at drivers/i2c/i2c-core.c:1930 i2c_register_driver+0x2c/0x79()
Date: Mon, 14 Mar 2016 19:45:19 +0530 [thread overview]
Message-ID: <20160314141519.GA5699@sudip-laptop> (raw)
In-Reply-To: <20160314011419.GA2308@katana>
On Mon, Mar 14, 2016 at 02:14:19AM +0100, Wolfram Sang wrote:
> On Mon, Mar 14, 2016 at 08:47:59AM +0800, kernel test robot wrote:
> > FYI, we noticed the below changes on
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux i2c/for-next
> > commit 95026658c46ea2d94498d0dac1282e28cd47c64a ("i2c: do not use internal data from driver core")
>
> Ouch! So nobody of us ever boot-tested this patch? :(
No. Sorry. It was only compile tested but Fengguang sent me the warning
before you applied the patch but I was travelling and so could not do anything.
regards
sudip
next prev parent reply other threads:[~2016-03-14 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 0:47 [i2c] 95026658c4: WARNING: CPU: 0 PID: 1 at drivers/i2c/i2c-core.c:1930 i2c_register_driver+0x2c/0x79() kernel test robot
2016-03-14 0:47 ` [lkp] " kernel test robot
2016-03-14 1:14 ` Wolfram Sang
2016-03-14 1:14 ` [lkp] " Wolfram Sang
2016-03-14 14:15 ` Sudip Mukherjee [this message]
2016-03-14 14:15 ` Sudip Mukherjee
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=20160314141519.GA5699@sudip-laptop \
--to=sudipm.mukherjee@gmail.com \
--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.