From: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RESEND patch 2.6.28-rc4] isp1301_omap build fixes
Date: Mon, 17 Nov 2008 20:07:11 -0800 [thread overview]
Message-ID: <200811172007.11217.david-b@pacbell.net> (raw)
In-Reply-To: <20081117213615.57c3d494-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
On Monday 17 November 2008, Jean Delvare wrote:
> Sorry about that, I thought this patch would go through the omap tree.
> But I've picked it and applied it now and will send it to Linus in the
> next i2c batch.
Thanks ... it wouldn't go through the OMAP tree unless it were in
the arch/arm/*omap* directories, as a rule. And that's for low
level board support; drivers belong somewhere in drivers/* code.
> 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".
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.
- Dave
next prev parent reply other threads:[~2008-11-18 4:07 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 [this message]
[not found] ` <200811172007.11217.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-11-18 8:09 ` Jean Delvare
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=200811172007.11217.david-b@pacbell.net \
--to=david-b-ybekhbn/0ldr7s880joybq@public.gmane.org \
--cc=dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@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.