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 USB Changes for Merge Window
Date: Thu, 23 Dec 2010 12:39:20 -0800	[thread overview]
Message-ID: <20101223203920.GQ7771@atomide.com> (raw)
In-Reply-To: <20101223084734.GA3149@legolas.emea.dhcp.ti.com>

* Felipe Balbi <balbi@ti.com> [101223 00:47]:
> Hi Tony,
> 
> please queue the following two patches for Merge Window.
> 
> The following changes since commit b79540fcbbcf9b379c9197f63c5a883bbe3adfd4:
> 
>    Linux-omap rebuilt: Merged branches from Paul and Kevin and mux changes (2010-12-22 19:13:33 -0800)

This can't be pulled as it would pull in tons of non-mainline
commits from the linux-omap master branch.

Everybody, all the pullable branches must be based on something
in the mainline kernel, like a recent -rc tag. If that won't work,
then some commit needs to be agreed on separately that will go
to mainline, like the omap-for-linus branch.

Further, please wait few days before sending the pull request
in case somebody wants to ack your patches. Sending a pull request
with the patches to be reviewed is kind of pointless.. Sure in this
case these are pretty trivial patches, but still.

Anyways, I'll apply these into a temporary branch and will
merge into omap-for-linus within next few days assuming no
problems.

Regards,

Tony

  parent reply	other threads:[~2010-12-23 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-23  8:47 [GIT PULL] OMAP USB Changes for Merge Window Felipe Balbi
2010-12-23  8:50 ` [PATCH 1/2] arm: omap: craneboard: Add USB EHCI support Felipe Balbi
2010-12-23  8:50   ` [PATCH 2/2] arm: omap: tusb6010: add name for MUSB IRQ Felipe Balbi
2010-12-23 20:39 ` Tony Lindgren [this message]
2010-12-27  9:22   ` [GIT PULL] OMAP USB Changes for Merge Window Felipe Balbi

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=20101223203920.GQ7771@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).