All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Madhusudhan Chikkature" <madhu.cr@ti.com>
Cc: felipe.balbi@nokia.com, Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
	tony@atomide.com, linux-omap@vger.kernel.org
Subject: Re: [PATCH]OMAP HDQ driver ioremap changes
Date: Tue, 23 Sep 2008 10:07:23 +0530	[thread overview]
Message-ID: <00b801c91d36$156fd5a0$LocalHost@wipultra1303> (raw)
In-Reply-To: 20080922143741.GV24627@gandalf.research.nokia.com


----- Original Message ----- 
From: "Felipe Balbi" <felipe.balbi@nokia.com>
To: "ext Madhusudhan Chikkature" <madhu.cr@ti.com>
Cc: <felipe.balbi@nokia.com>; "Evgeniy Polyakov" <johnpol@2ka.mipt.ru>; <tony@atomide.com>; <linux-omap@vger.kernel.org>
Sent: Monday, September 22, 2008 8:07 PM
Subject: Re: [PATCH]OMAP HDQ driver ioremap changes


> On Mon, Sep 22, 2008 at 07:01:57PM +0530, ext Madhusudhan Chikkature wrote:
>> 
>> ----- Original Message ----- 
>> From: "Felipe Balbi" <felipe.balbi@nokia.com>
>> To: "ext Madhusudhan Chikkature" <madhu.cr@ti.com>
>> Cc: "Evgeniy Polyakov" <johnpol@2ka.mipt.ru>; <tony@atomide.com>; <linux-omap@vger.kernel.org>
>> Sent: Monday, September 22, 2008 6:57 PM
>> Subject: Re: [PATCH]OMAP HDQ driver ioremap changes
>> 
>> 
>> > On Mon, Sep 22, 2008 at 06:43:10PM +0530, ext Madhusudhan Chikkature wrote:
>> >> Hi Evgeniy Polyakov,
>> >> 
>> >> Thanks for the comments. I will incorporate them and send the patch again. My comments inlined.
>> > 
>> > How about fixing it and later sending to mainline for integration ?
>> 
>> Yes. I will do that.
> 
> Really, that driver is a mess. Get the attached patch, break it into
> proper smaller patches, see if it's really working since I just compile
> tested, change the semaphore to mutex (in a separate patch), fix
> comments to kernel-doc style, then you send a nice series fixing the
> driver before sending the final driver to mainline.
> 
> It's time to start doing things properly. It's really annoying have to
> keep cleaning stuff after it's in-tree.

Balbi,
Please note that the driver patches were submitted to L-o as RFC initially and all the comments provided by the community are fixed before it is pushed by Tony. 

There would be a time gap between the day the patches are submitted and before Tony pushes the patches to the tree. Any valid comments provided then would get promptly fixed. This would definetely avoid cleaning stuff which is already in tree to whatever extent it is possible.

Regards,
Madhu
> 
> -- 
> balbi
>

  parent reply	other threads:[~2008-09-23  4:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22 10:15 [PATCH]OMAP HDQ driver ioremap changes Madhusudhan Chikkature
2008-09-22 13:06 ` Evgeniy Polyakov
2008-09-22 13:13   ` Madhusudhan Chikkature
2008-09-22 13:27     ` Felipe Balbi
2008-09-22 13:31       ` Madhusudhan Chikkature
2008-09-22 13:38         ` Felipe Balbi
2008-09-22 14:37         ` Felipe Balbi
2008-09-22 20:14           ` Evgeniy Polyakov
2008-09-23  2:24             ` Felipe Balbi
2008-09-23  4:52               ` Madhusudhan Chikkature
2008-09-23  6:52                 ` Evgeniy Polyakov
2008-09-23  4:37           ` Madhusudhan Chikkature [this message]
2008-09-23 10:57             ` 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='00b801c91d36$156fd5a0$LocalHost@wipultra1303' \
    --to=madhu.cr@ti.com \
    --cc=felipe.balbi@nokia.com \
    --cc=johnpol@2ka.mipt.ru \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.