public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: David Brownell <david-b@pacbell.net>
Cc: gregkh@suse.de, felipe.balbi@nokia.com,
	linux-usb@vger.kernel.org, khilman@deeprootsystems.com,
	davinci-linux-open-source@linux.davincidsp.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] musb: fix DaVinci build again
Date: Wed, 24 Dec 2008 02:23:49 +0300	[thread overview]
Message-ID: <49517305.4000100@ru.mvista.com> (raw)
In-Reply-To: <200812230939.00508.david-b@pacbell.net>

Hello.

David Brownell wrote:

>>    For how much longer we'll have to wait for this issue to be resolved? 
>> 2.6.28 is 2 days away (at most).
>>     
>
> Yeah, I sent a DaVinci build fix patch in plenty of time to
> be merged for *2.6.27* (!!!!) but still the key parts are
> missing, and have not managed to make it into mainline.

  Try breakinjg the patches into smaller pieces next time, so they may 
get thru the maintainer's sieve more easily. :-)

WBR, Sergei



  reply	other threads:[~2008-12-23 23:24 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 [this message]
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

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=49517305.4000100@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