public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Koen Kooi <k.kooi@student.utwente.nl>
Cc: linux-omap List <linux-omap@vger.kernel.org>
Subject: Re: [PATCH][UPDATED] DSPBRIDGE: CLK_Enable and CLK_Disable Code cleanup
Date: Thu, 14 May 2009 11:00:58 -0700	[thread overview]
Message-ID: <20090514180058.GN5593@atomide.com> (raw)
In-Reply-To: <BA44A5A6-F51F-4ED0-88E4-9AD8BB6785A2@student.utwente.nl>

* Koen Kooi <k.kooi@student.utwente.nl> [090425 07:48]:
> Op 25 apr 2009, om 13:42 heeft Felipe Contreras het volgende geschreven:
>
>> While there has been good progress in the bridgedriver, it is still
>> *very* far away from meeting mainline standards and this makes many
>> people uneasy, including me.
>
>
> Is it "good enough" to go into Greg KHs staging tree?

I'd rather keep any code that does non-standard tinkering
of omap registers out of the mainline tree until the basics are
fixed.

Regards,

Tony

      reply	other threads:[~2009-05-14 18:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 12:19 [PATCH] DSPBRIDGE: CLK_Enable and CLK_Disable Code cleanup Ameya Palande
2009-04-17 13:05 ` Kanigeri, Hari
2009-04-17 14:46 ` Artem Bityutskiy
2009-04-17 15:19   ` [PATCH][UPDATED] " Ameya Palande
2009-04-17 15:38     ` Artem Bityutskiy
2009-04-17 16:17       ` [PATCH][Take 2] " Ameya Palande
2009-04-17 15:49     ` [PATCH][UPDATED] " Artem Bityutskiy
2009-04-17 17:45       ` Ramirez Luna, Omar
2009-04-17 19:31         ` Kanigeri, Hari
2009-04-25 11:42         ` Felipe Contreras
2009-04-25 13:07           ` Nishanth Menon
2009-04-25 13:19           ` Ramirez Luna, Omar
2009-04-25 14:47           ` Koen Kooi
2009-05-14 18:00             ` Tony Lindgren [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=20090514180058.GN5593@atomide.com \
    --to=tony@atomide.com \
    --cc=k.kooi@student.utwente.nl \
    --cc=linux-omap@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