From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: David Brownell <dbrownell@users.sourceforge.net>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
Bill Gatliff <bgat@billgatliff.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 3/4] of/gpio: Implement GPIOLIB notifier hooks
Date: Sat, 6 Mar 2010 03:28:23 +0300 [thread overview]
Message-ID: <20100306002823.GA22095@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <fa686aa41003051547u1f499902w1d3efc614a9b20b6@mail.gmail.com>
On Fri, Mar 05, 2010 at 04:47:06PM -0700, Grant Likely wrote:
[...]
> >> I'm not really very comfortable with the whole
> >> approach being taken. And, while I acked the first patch in the
> >> series, that patch isn't needed by anything except patches 2, 3 & 4.
But you didn't answer my replies, ie were sitting silent like for
a month? So you didn't give my any chance to make them comfortable
to you.
Is there any punishment ready for that? ;-) I see one: apply
these patches, and rework this stuff as you like when you have some
time? Or tell me your idea, and I'll do the rework for you, in
2.6.35.
But in the meantime, these patches can be nicely used to support
I2C/SPI GPIO controllers.
> >> Also, the OF stuff is a moving target at the moment with all the
> >> rework is being undertaken. I'd rather let this series sit out for
> >> another merge cycle so that the underlying OF stuff can settle down.
> >
> > OK, please take it up on-list?
>
> Okay. I'm making this reply on list.
>
> Anton, as I've stated before, I'm not thrilled with the approach.
Again, great timing for telling that, I must say. Yes, you said
it once with some minor arguments (doubts and questions), to which
I replied long ago. Then nothing.
> Combine that with the changes being made to drivers/of right now and
> the addition device tree to ARM and other architectures, my preference
> is to let this patch series lie fallow for one more merge cycle so
> that things can settle out in the OF infrastructure code.
How exactly OF rework affects these patches? And why some rework
should be used as an excuse for not adding a hardware support?
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2010-03-06 0:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 20:32 [PATCH v2 0/4] OF GPIO integration for I2C/SPI GPIO chips Anton Vorontsov
2010-02-05 20:32 ` [PATCH 1/4] gpiolib: Introduce chip addition/removal notifier Anton Vorontsov
2010-02-09 17:16 ` Grant Likely
2010-03-05 19:59 ` Andrew Morton
2010-03-05 20:30 ` Anton Vorontsov
2010-02-05 20:32 ` [PATCH 2/4] of/gpio: Add support for two-stage registration for the of_gpio_chips Anton Vorontsov
2010-02-05 20:32 ` [PATCH 3/4] of/gpio: Implement GPIOLIB notifier hooks Anton Vorontsov
2010-02-08 21:02 ` Andrew Morton
2010-02-09 17:08 ` Grant Likely
2010-02-09 19:06 ` Anton Vorontsov
2010-02-09 17:13 ` Grant Likely
2010-02-09 19:16 ` Anton Vorontsov
[not found] ` <20100305120015.a2008f46.akpm@linux-foundation.org>
[not found] ` <fa686aa41003051228w38579483yd4e95bb8eacf40f7@mail.gmail.com>
[not found] ` <20100305123527.d6d68e56.akpm@linux-foundation.org>
2010-03-05 23:47 ` Grant Likely
2010-03-06 0:28 ` Anton Vorontsov [this message]
2010-03-06 3:54 ` Grant Likely
2010-03-06 5:05 ` Anton Vorontsov
2010-03-06 16:43 ` Grant Likely
2010-03-07 1:47 ` Anton Vorontsov
2010-03-07 6:11 ` Grant Likely
2010-03-12 21:07 ` Andrew Morton
2010-03-12 21:38 ` Grant Likely
2010-04-30 17:45 ` Anton Vorontsov
2010-02-05 20:32 ` [PATCH 4/4] powerpc/mcu_mpc8349emitx: Remove OF GPIO handling stuff Anton Vorontsov
-- strict thread matches above, loose matches on Subject: below --
2010-01-25 18:09 [PATCH 0/4] OF GPIO integration for I2C/SPI GPIO chips Anton Vorontsov
2010-01-25 18:11 ` [PATCH 3/4] of/gpio: Implement GPIOLIB notifier hooks Anton Vorontsov
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=20100306002823.GA22095@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=akpm@linux-foundation.org \
--cc=bgat@billgatliff.com \
--cc=dbaryshkov@gmail.com \
--cc=dbrownell@users.sourceforge.net \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).