From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: gregkh@suse.de
Cc: felipe.balbi@nokia.com, linux-usb@vger.kernel.org,
khilman@deeprootsystems.com,
davinci-linux-open-source@linux.davincidsp.com,
david-b@pacbell.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] musb: fix DaVinci build again
Date: Wed, 24 Dec 2008 18:04:33 +0300 [thread overview]
Message-ID: <49524F81.4030301@ru.mvista.com> (raw)
In-Reply-To: <4950CFAD.7020403@ru.mvista.com>
Hello, I wrote:
>>>>> The last Kevin Hilman's patch seems to have been broken on its way
>>>>> to Greg's
>>>>> tree and also probably clashed with yet another patch. Fix DaVinci
>>>>> build again.
>>>>> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
>>>>> ---
>>>>> Felipe, I have to ask you again to be more careful with patches...
>>>> 11 days have passed since this has benn sent out and I'm still
>>>> not seeing this 2.6.28 *hot* fix in the MUSB git tree. Greg, could
>>>> you queue this urgently, bypassing the MUSB tree?
>>> I'll be happy if it gets combined with the following patch in your
>>> tree:
>>> http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/usb/usb-musb-build-fixes-for-davinci.patch
>>> fallout of which I'm fixing. Though it would've been better yet if
>>> you just dropped that totally broken patch. I could've send a
>>> replacment then...
>> The patch I liked to above fixes nothing and only adds more
>> breakage. Compare it with the original Kevin's patch:
>> http://marc.info/?l=linux-usb&m=122608723815504
> I'm seeing Felipe returning to the list but still ignoring this thread
> so far.
> For how much longer we'll have to wait for this issue to be resolved?
> 2.6.28 is 2 days away (at most).
> Greg, what's the problem with dropping obviously broken patch?
Greg, looks like that *2.6.28* (acyually even 2.6.27) patch is even in the
wrong sub-series (past-2.6.28) of your tree, so there was no hope on the
timely resolution from the very start... sigh. :-(
WBR, Sergei
prev parent reply other threads:[~2008-12-24 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200812072341.50012.sshtylyov@ru.mvista.com>
[not found] ` <494A7729.6090102@ru.mvista.com>
[not found] ` <494A7809.1040504@ru.mvista.com>
[not found] ` <494E2450.9080601@ru.mvista.com>
2008-12-23 11:46 ` [PATCH] musb: fix DaVinci build again Sergei Shtylyov
2008-12-23 17:38 ` David Brownell
2008-12-23 23:23 ` Sergei Shtylyov
2008-12-24 1:07 ` David Brownell
2008-12-24 2:27 ` Felipe Balbi
2008-12-24 3:52 ` David Brownell
2008-12-25 20:37 ` David Brownell
2008-12-24 15:04 ` Sergei Shtylyov [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=49524F81.4030301@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=david-b@pacbell.net \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=felipe.balbi@nokia.com \
--cc=gregkh@suse.de \
--cc=khilman@deeprootsystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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