public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: David Cohen <david.a.cohen@linux.intel.com>
Cc: Lu Baolu <baolu.lu@linux.intel.com>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	qiuxu.zhuo@intel.com
Subject: Re: [PATCH v2 1/1] usb: ulpi: ulpi_init should be executed in subsys_initcall
Date: Sun, 24 May 2015 09:25:17 -0700	[thread overview]
Message-ID: <20150524162517.GA2150@kroah.com> (raw)
In-Reply-To: <20150522031127.GB28433@psi-dev26.jf.intel.com>

On Thu, May 21, 2015 at 08:11:27PM -0700, David Cohen wrote:
> On Thu, May 21, 2015 at 08:09:54PM -0700, David Cohen wrote:
> > Hi,
> > 
> > On Fri, May 22, 2015 at 10:07:05AM +0800, Lu Baolu wrote:
> > > Many drivers and modules depend on ULPI bus registeration to
> > > register ULPI interfaces and drivers. It's more appropriate
> > > to register ULPI bus in subsys_initcall instead of module_init.
> > > 
> > > Kernel panic has been reported with some kind of kernel config.
> > 
> > Even though I agree subsys_initcall is better to register ulpi bus, it's
> > still no excuse to have kernel panic. What about ULPI bus being compiled
> > as module?
> > IMHO this is avoiding the proper kernel panic fix which should be
> > failing gracefully (or defer probe) from tusb1210 driver.
> 
> Maybe I need to express myself better :)
> IMHO we should not consider work done with this patch only. It's still
> incomplete.

Then please fix it properly, this is not the correct solution.

greg k-h

      parent reply	other threads:[~2015-05-24 16:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22  2:07 [PATCH v2 1/1] usb: ulpi: ulpi_init should be executed in subsys_initcall Lu Baolu
2015-05-22  3:09 ` David Cohen
2015-05-22  3:11   ` David Cohen
2015-05-22  6:46     ` Lu, Baolu
2015-05-22  7:50       ` Lu, Baolu
2015-05-22 16:12         ` David Cohen
2015-05-22 10:07       ` Heikki Krogerus
2015-05-24 16:25     ` Greg Kroah-Hartman [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=20150524162517.GA2150@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=david.a.cohen@linux.intel.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=qiuxu.zhuo@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