From: Pavel Machek <pavel@ucw.cz>
To: Felipe Balbi <balbi@ti.com>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
"Linux USB Mailing List" <linux-usb@vger.kernel.org>,
"Aaro Koskinen" <aaro.koskinen@iki.fi>,
"Sebastian Reichel" <sre@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] usb: gadget: function: phonet: balance usb_ep_disable calls
Date: Fri, 20 Feb 2015 22:15:52 +0100 [thread overview]
Message-ID: <20150220211552.GB28995@amd> (raw)
In-Reply-To: <20150220143906.GA1707@saruman.tx.rr.com>
On Fri 2015-02-20 08:39:06, Felipe Balbi wrote:
> On Fri, Feb 20, 2015 at 09:27:51AM +0100, Pavel Machek wrote:
> > > > > > > > In current state I review all 3 patches as:
> > > > > > > >
> > > > > > > > Rejected-by: Pali Rohár <pali.rohar@gmail.com>
> > > > > > > > [It breaks booting Nokia N900 device]
> > > > > > >
> > > > > > > next step, figure why it's broken. Working just fine here
> > > > > > > on AM335x which has the same musb IP.
> > > > > >
> > > > > > Why is broken? That is easy. You send 3 patches which broke
> > > > > > it.
> > > > >
> > > > > Actually when I reverted only that patch which adds line:
> > > > >
> > > > > pm_runtime_irq_safe(musb->controller)
> > > > >
> > > > > then early boot crash disappeared.
> > > > >
> > > > > But other two patches did not fixed support for external .ko
> > > > > gadget modules. State is same -- crash after modprobe.
> > > >
> > > > Here is crash from qemu when musb is compiled into kernel:
> > > >
> > > > [ 0.641662] Unable to handle kernel NULL pointer dereference at virtual address 00000000
> > > > [ 0.642211] pgd = c0004000
> > ...
> > > > [ 0.672882] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
> > > > [ 0.672882]
> > > >
> > > > Reason why it crashes is because when function
> > > > omap2430_runtime_resume() is called pointer to functions
> > > > musb_readl and musb_writel are both NULL. And so NULL pointer
> > > > dereference.
> > >
> > > https://git.kernel.org/cgit/linux/kernel/git/balbi/usb.git/commit/?h=testing/next&id=1861a2c60351a390272b3395f4d88480cdfd9e58
> > >
> >
> > So you commit a fix to your internal branch without telling Pali, who
> > is actively debugging same problem at the same time, and then you just
> > send him url without at least saying "sorry"?
>
> grow up... why do I have to say sorry for fixing a problem ? Why do I
> have to let you know I committed something to my branch ? It's the
Because that's polite thing to do when you break someone elses system?
I see politeness is not your great strength.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-02-20 21:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1422918921-5472-1-git-send-email-balbi@ti.com>
[not found] ` <201502031717.28789@pali>
[not found] ` <20150203191859.GA6508@saruman.tx.rr.com>
2015-02-03 19:27 ` [PATCH 1/3] usb: gadget: function: phonet: balance usb_ep_disable calls Pali Rohár
2015-02-03 19:35 ` Felipe Balbi
2015-02-03 19:51 ` Felipe Balbi
2015-02-03 20:03 ` Pali Rohár
2015-02-03 19:57 ` Pali Rohár
2015-02-03 20:02 ` Felipe Balbi
2015-02-05 12:38 ` Pali Rohár
2015-02-20 0:09 ` Pali Rohár
2015-02-20 3:06 ` Felipe Balbi
2015-02-20 8:27 ` Pavel Machek
2015-02-20 14:39 ` Felipe Balbi
2015-02-20 21:15 ` Pavel Machek [this message]
2015-02-21 7:14 ` Felipe Balbi
2015-02-21 7:18 ` Felipe Balbi
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=20150220211552.GB28995@amd \
--to=pavel@ucw.cz \
--cc=aaro.koskinen@iki.fi \
--cc=balbi@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=sre@kernel.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