linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap fixes and cleanups for v3.8 merge window
Date: Mon, 17 Dec 2012 10:38:52 -0800	[thread overview]
Message-ID: <20121217183852.GX4989@atomide.com> (raw)
In-Reply-To: <20121217183103.GW4989@atomide.com>

* Tony Lindgren <tony@atomide.com> [121217 10:33]:
> * Felipe Balbi <balbi@ti.com> [121217 10:18]:
> > Hi,
> > 
> > On Mon, Dec 17, 2012 at 10:02:01AM -0800, Tony Lindgren wrote:
> > >  drivers/mfd/omap-usb-host.c                        |  3 +-
> > >  drivers/tty/serial/omap-serial.c                   |  3 +-
> > >  drivers/usb/phy/Kconfig                            |  1 +
> > 
> > I did mention I was against adding OMAP dependencies do drivers.
> > Interesting to see to commit going upstream without a reply to my
> > comment :-s
> > 
> > http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap.git;a=commitdiff;h=3e194c88f8b71700822828749187e65853ed8166
> 
> Looks like Linus already applied it. Anyways, I like Dmitry's idea
> of adding an extra COMPILE_COVERAGE flag to enable the build of
> arch specific drivers for driver subsystem maintainers, I'll
> do a patch for that so you can test build all the arch specific
> USB drivers on x86 also.

Oh I see I have it also in my fixes, that should not be there.

I'll fix that and do another pull request. The commit Linus
applied is 770b6cb4.

Regards,

Tony

      reply	other threads:[~2012-12-17 18:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17 18:02 [GIT PULL] omap fixes and cleanups for v3.8 merge window Tony Lindgren
2012-12-17 18:08 ` Felipe Balbi
2012-12-17 18:31   ` Tony Lindgren
2012-12-17 18:38     ` Tony Lindgren [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=20121217183852.GX4989@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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).