From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] arm: omap: move OMAP USB platform data to <linux/platform_data/omap-usb.h>
Date: Fri, 19 Oct 2012 08:56:12 -0700 [thread overview]
Message-ID: <20121019155612.GA4730@atomide.com> (raw)
In-Reply-To: <20121019065500.GD12235@arwen.pp.htv.fi>
* Felipe Balbi <balbi@ti.com> [121019 00:01]:
> On Thu, Oct 18, 2012 at 06:49:17PM -0700, Tony Lindgren wrote:
> >
> > Yes. Figured it out, it fails to apply with quilt, but applies
> > with git.
>
> probably because of file rename.
Yeh so it seems.
> > But it does not compile with all configs though, and does
> > not remove plat/usb.h. Thanks anyways. I'll post a proper
> > series shortly with your patch fixed up.
>
> ok... I'll check it out. I kept the non-static functions in plat/usb.h
> because they didn't belong on platform_data/usb-omap.h. What should be
> done with those, then ? move to mach/ ?
I made a clean-up patch that creates local usb.h file for those
that applies before your patch.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm: omap: move OMAP USB platform data to <linux/platform_data/omap-usb.h>
Date: Fri, 19 Oct 2012 08:56:12 -0700 [thread overview]
Message-ID: <20121019155612.GA4730@atomide.com> (raw)
In-Reply-To: <20121019065500.GD12235@arwen.pp.htv.fi>
* Felipe Balbi <balbi@ti.com> [121019 00:01]:
> On Thu, Oct 18, 2012 at 06:49:17PM -0700, Tony Lindgren wrote:
> >
> > Yes. Figured it out, it fails to apply with quilt, but applies
> > with git.
>
> probably because of file rename.
Yeh so it seems.
> > But it does not compile with all configs though, and does
> > not remove plat/usb.h. Thanks anyways. I'll post a proper
> > series shortly with your patch fixed up.
>
> ok... I'll check it out. I kept the non-static functions in plat/usb.h
> because they didn't belong on platform_data/usb-omap.h. What should be
> done with those, then ? move to mach/ ?
I made a clean-up patch that creates local usb.h file for those
that applies before your patch.
Regards,
Tony
next prev parent reply other threads:[~2012-10-19 15:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 23:00 Updated status of the removal of plat headers Tony Lindgren
2012-10-17 0:24 ` Paul Walmsley
2012-10-17 15:43 ` [PATCH] arm: omap: move OMAP USB platform data to <linux/platform_data/omap-usb.h> Felipe Balbi
2012-10-17 15:43 ` Felipe Balbi
2012-10-17 15:45 ` Felipe Balbi
2012-10-17 15:45 ` Felipe Balbi
2012-10-17 15:47 ` [PATCH v2] " Felipe Balbi
2012-10-17 15:47 ` Felipe Balbi
2012-10-17 20:34 ` Tony Lindgren
2012-10-17 20:34 ` Tony Lindgren
2012-10-18 5:49 ` Felipe Balbi
2012-10-18 5:49 ` Felipe Balbi
2012-10-19 1:49 ` Tony Lindgren
2012-10-19 1:49 ` Tony Lindgren
2012-10-19 6:55 ` Felipe Balbi
2012-10-19 6:55 ` Felipe Balbi
2012-10-19 15:56 ` Tony Lindgren [this message]
2012-10-19 15:56 ` Tony Lindgren
2012-10-17 21:51 ` Updated status of the removal of plat headers Jon Hunter
2012-10-17 22:02 ` Tony Lindgren
2012-10-19 17:43 ` Omar Ramirez Luna
2012-10-19 18:25 ` Tony Lindgren
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=20121019155612.GA4730@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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.