From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RESEND patch 2.6.28-rc4] isp1301_omap build fixes
Date: Tue, 18 Nov 2008 09:09:49 +0100 [thread overview]
Message-ID: <20081118090949.12654a6a@hyperion.delvare> (raw)
In-Reply-To: <200811172007.11217.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
Hi Dave,
On Mon, 17 Nov 2008 20:07:11 -0800, David Brownell wrote:
> On Monday 17 November 2008, Jean Delvare wrote:
> > I think that this kind of issue would probably be avoided if the
> > isp1301_omap driver lived somewhere under arch/arm/plat-omap. Where it
> > lives now (drivers/i2c/chips) it doesn't get the attention it deserves,
> > or when it does, that's not from the right persons. Could you please
> > work on this? Directory drivers/i2c/chips will be deleted "soon"
> > anyway, so all the drivers it contains will need a new home.
>
> I expect drivers/usb/otg will be a better place for this. There's
> some other code which looks like it'll need to land there "soon".
Fine with me.
> Once you merge these build fixes I'll probably cons up a patch which
> moves this over there. Unless you'd rather handle it, I'll probably
> push that through Greg.
I'm totally OK with it going through Greg.
Thanks,
--
Jean Delvare
prev parent reply other threads:[~2008-11-18 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 20:28 [RESEND patch 2.6.28-rc4] isp1301_omap build fixes David Brownell
[not found] ` <200811141228.35262.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-11-17 20:36 ` Jean Delvare
[not found] ` <20081117213615.57c3d494-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-11-18 4:07 ` David Brownell
[not found] ` <200811172007.11217.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-11-18 8:09 ` Jean Delvare [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=20081118090949.12654a6a@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.