From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
Richard Purdie <rpurdie@rpsys.net>,
Sean MacLennan <smaclennan@pikatech.com>,
Trent Piepho <tpiepho@freescale.com>
Subject: Re: [PATCH 1/4] of_gpio: Return GPIO flags from of_get_gpio()
Date: Tue, 28 Oct 2008 19:56:23 +0300 [thread overview]
Message-ID: <20081028165623.GA6686@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <fa686aa40810280842t36da3998j5f7ad22acf9f582c@mail.gmail.com>
On Tue, Oct 28, 2008 at 09:42:36AM -0600, Grant Likely wrote:
> On Tue, Oct 28, 2008 at 9:16 AM, Anton Vorontsov
> <avorontsov@ru.mvista.com> wrote:
> > On Tue, Oct 28, 2008 at 08:53:11AM -0600, Grant Likely wrote:
> >> That will deal with any merge window
> >> conflicts.
> >
> > This won't deal with build breakage because of API changes, which
> > means I can't submit FHCI driver to Greg, I have to wait for the
> > API changes applied.
>
> Then we coordinate with Greg and make sure the fixup gets put in place
> before the window opens; either by bringing the patch in Ben's tree or
> by getting Greg to pull Ben's tree into -next. This API change should
> not block Greg picking up the FHCI driver. This is not an
> insurmountable problem.
Sounds complicated.
Ok, but if something will go wrong with the FHCI vs. of_get_gpio()
change, I'll just attribute the blame to you. :-))
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2008-10-28 16:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 23:04 OpenFirmware GPIO LED driver Trent Piepho
2008-10-24 23:08 ` [PATCH 1/4] of_gpio: Return GPIO flags from of_get_gpio() Trent Piepho
2008-10-24 23:32 ` Grant Likely
2008-10-28 14:39 ` Anton Vorontsov
2008-10-28 14:53 ` Grant Likely
2008-10-28 15:16 ` Anton Vorontsov
2008-10-28 15:42 ` Grant Likely
2008-10-28 16:56 ` Anton Vorontsov [this message]
2008-10-28 17:40 ` Grant Likely
2008-10-30 2:21 ` [PATCH 1/4] of_gpio: Return GPIO flags from of_get_gpio()A Trent Piepho
2008-10-30 11:15 ` Anton Vorontsov
2008-10-31 2:03 ` [PATCH v2] of_gpio: Return GPIO flags from of_get_gpio() Trent Piepho
2008-11-26 16:20 ` Anton Vorontsov
2008-11-26 21:38 ` Paul Mackerras
2008-11-26 22:31 ` Anton Vorontsov
2008-11-26 22:35 ` Trent Piepho
2008-11-26 22:58 ` Anton Vorontsov
2008-11-26 23:32 ` Paul Mackerras
2008-10-24 23:08 ` [PATCH 2/4] leds: Support OpenFirmware led bindings Trent Piepho
2008-10-24 23:50 ` Grant Likely
2008-10-24 23:09 ` [PATCH 3/4] leds: Add option to have GPIO LEDs start on Trent Piepho
2008-10-24 23:59 ` Grant Likely
2008-10-24 23:09 ` [PATCH 4/4] leds: Let GPIO LEDs keep their current state Trent Piepho
2008-10-25 0:04 ` Grant Likely
2008-11-17 14:50 ` Richard Purdie
2008-11-21 1:05 ` Trent Piepho
2008-11-23 12:31 ` Pavel Machek
2008-12-03 10:04 ` Richard Purdie
2008-12-10 4:33 ` Trent Piepho
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=20081028165623.GA6686@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rpurdie@rpsys.net \
--cc=smaclennan@pikatech.com \
--cc=tpiepho@freescale.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 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).