From: Valentine Barshak <vbarshak@ru.mvista.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linuxppc-dev@ozlabs.org, sr@denx.de, linux-mtd@lists.infradead.org
Subject: Re: [PATCH 0/3] Add device-tree aware NDFC driver
Date: Tue, 30 Oct 2007 17:13:08 +0300 [thread overview]
Message-ID: <47273BF4.80001@ru.mvista.com> (raw)
In-Reply-To: <alpine.LFD.0.9999.0710300235580.3186@localhost.localdomain>
Thomas Gleixner wrote:
> On Mon, 29 Oct 2007, Valentine Barshak wrote:
>
>> This adds a device-tree aware PowerPC 44x NanD Flash Controller driver
>> The code is based on the original NDFC driver by Thomas Gleixner, but
>> since it's been changed much and has initialization/clean-up completely
>> reworked it's been put into a separate ndfc_of.c file. This version
>> supports both separate mtd devices on each chip attached to NDFC banks and
>> single mtd device spread across identical chips (not using mtdconcat) as well.
>> The choice is selected with device tree settings. This has been tested
>> on PowerPC 440EPx Sequoia board.
>> Any comments are greatly appreciated.
>
> Did I express myself not clear enough in my first reply or is this
> just a repeated epiphany in my inbox ?
>
> You got plenty of comments to your patches, but you decided to ignore
> them silently.
>
> Darn, fix it the right way once and forever and please don't try to
> tell me another heartrending "why I did it my way" story.
>
> This all can be done with a nice series of incremental patches
> including a fixup to the existing users.
>
> We have enough dump and run shit in the kernel already.
>
> No thanks,
>
> tglx
You know, you're really too tense Thomas. I'm not sure of the reason why
you're being a complete nerve, but I'm feeling sorry for you.
I'm not saying my approach is the best, but I was hoping for a discussion.
I've reworked the patches according to the comments to the previous
version and used my arguments to explain why I don't see much reason to
mess with the code we currently have and added a separate _of version.
I'm sure you'd find some time to do it yourself "the right way once and
forever" with a "nice series of incremental patches" to fix what we
currently have (call it a "dump" or anything you like) and even maybe
add new device tree support.
I'm sorry if for some reason I've made you feel bad.
This is the last time I disturb you with my e-mail, so please, forget it.
Thank you very much for your comments anyway.
It's been nice talking to you,
Valentine.
next prev parent reply other threads:[~2007-10-30 14:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 20:17 [PATCH 0/3] Add device-tree aware NDFC driver Valentine Barshak
2007-10-29 20:21 ` [PATCH 1/3] PowerPC: Add device-tree aware PowerPC 44x " Valentine Barshak
2007-10-29 20:22 ` [PATCH 2/3] PowerPC: 44x NanD Flash Controller (NDFC) bindings Valentine Barshak
2007-10-29 20:23 ` [PATCH 3/3] PowerPC: NDFC entry for 440EPx Sequoia DTS Valentine Barshak
2007-10-30 1:49 ` [PATCH 0/3] Add device-tree aware NDFC driver Thomas Gleixner
2007-10-30 14:13 ` Valentine Barshak [this message]
2007-10-30 15:33 ` Jörn Engel
2007-11-04 20:48 ` Thomas Gleixner
2007-11-06 14:21 ` Valentine Barshak
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=47273BF4.80001@ru.mvista.com \
--to=vbarshak@ru.mvista.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@denx.de \
--cc=tglx@linutronix.de \
/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