mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: kernel test robot <ying.huang@linux.intel.com>
Cc: lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
	Sudip Mukherjee <sudip@vectorindia.org>,
	0day robot <fengguang.wu@intel.com>
Subject: Re: [lkp] [ppdev] 138e9d20e6: kernel BUG at drivers/base/driver.c:153!
Date: Sun, 14 Feb 2016 22:00:01 +0530	[thread overview]
Message-ID: <20160214163001.GA19855@sudip-laptop> (raw)
In-Reply-To: <878u2nollw.fsf@yhuang-dev.intel.com>

On Sun, Feb 14, 2016 at 02:24:27PM +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
> 
> https://github.com/0day-ci/linux Sudip-Mukherjee/ppdev-space-prohibited-between-function-name-and-parenthesis/20160212-210833
> commit 138e9d20e69c0d682f584ee1ef0151338eef7499 ("ppdev: use new parport device model")

I am not able to reproduce this as I donot have all your scripts/files.
Can you please check if the below patch solves this in your setup.


diff --git a/drivers/parport/share.c b/drivers/parport/share.c
index 3308427..176b2b6 100644
--- a/drivers/parport/share.c
+++ b/drivers/parport/share.c
@@ -273,6 +273,9 @@ int __parport_register_driver(struct parport_driver *drv, struct module *owner,
 		/* using device model */
 		int ret;
 
+		if (!parport_bus_type.p)
+			return -EAGAIN;
+
 		/* initialize common driver fields */
 		drv->driver.name = drv->name;
 		drv->driver.bus = &parport_bus_type;

--
regards
sudip

      reply	other threads:[~2016-02-14 16:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14  6:24 kernel test robot
2016-02-14 16:30 ` Sudip Mukherjee [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=20160214163001.GA19855@sudip-laptop \
    --to=sudipm.mukherjee@gmail.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=sudip@vectorindia.org \
    --cc=ying.huang@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

all inboxes | Powered by JetHome®