From: Peter Chen <hzpeterchen@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Peter Chen <peter.chen@freescale.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Alan Stern <stern@rowland.harvard.edu>,
Rob Herring <robh@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: [GIT PULL] USB driver patches for 4.6-rc1
Date: Sun, 20 Mar 2016 19:31:47 +0800 [thread overview]
Message-ID: <20160320113147.GB30461@shlinux2.ap.freescale.net> (raw)
In-Reply-To: <CA+55aFxuPbOdB7wO6m396myBx+PWg=NCOwZfzdXvr49HQEPGSA@mail.gmail.com>
On Fri, Mar 18, 2016 at 04:01:51PM -0700, Linus Torvalds wrote:
> On Fri, Mar 18, 2016 at 3:51 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > The commit that ends up being marked bad is odd, but there it is:
> > 69bec7259853 "USB: core: let USB device know device node".
>
> Confirmed. Not only did it bisect to that, reverting it on top of the
> current kernel fixes my machine.
>
> So that commit is somehow buggy. I don't see what it does that would
> break even with OF disabled, but something does.
>
> I'll just revert it. The way it is done seems bogus anyway. It looks
> at of_node when OF is disabled, but generally that isn't even
> initialized as far as I can tell, and we have things like
> dev_of_node() helpers to make sure you don't do that.
>
I am sorry to make things break, Nicolai Stange's found the root cause
for this problem, and his patch fixed it.
USB device structure (both struct usb_hcd and struct usb_device) is
initialized by kzalloc, so the struct device in it is initialized by
zero, and will not cause non-initialized for USB device, but you
are right, a good practice is using dev_of_node for all devices in
case the struct device is not zero-initialized.
--
Best Regards,
Peter Chen
prev parent reply other threads:[~2016-03-20 11:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 0:09 Greg KH
2016-03-18 21:43 ` Linus Torvalds
2016-03-18 21:58 ` Linus Torvalds
2016-03-18 22:12 ` Greg KH
2016-03-18 22:23 ` Greg KH
2016-03-18 22:51 ` Linus Torvalds
2016-03-18 22:58 ` Greg KH
2016-03-18 23:09 ` Linus Torvalds
2016-03-18 23:17 ` Greg KH
2016-03-18 23:01 ` Linus Torvalds
2016-03-20 11:31 ` Peter Chen [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=20160320113147.GB30461@shlinux2.ap.freescale.net \
--to=hzpeterchen@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=peter.chen@freescale.com \
--cc=robh@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.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 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®