All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Péter Ujfalusi" <peter.ujfalusi@ti.com>
Cc: "Girdwood, Liam" <lrg@ti.com>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Samuel Ortiz <sameo@linux.intel.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL] TWL6040 MFD and followups
Date: Thu, 7 Jul 2011 11:29:47 -0700	[thread overview]
Message-ID: <20110707182947.GM5783@atomide.com> (raw)
In-Reply-To: <5898202.Q4JP1WeJj2@barack>

* Péter Ujfalusi <peter.ujfalusi@ti.com> [110707 04:43]:
> Hello Tony,
> 
> As it has been discussed I'm sending this pull request, which includes the
> following series (all patch acked-by the corresponding maintainer):
> 1. v6 of MFD/ASoC/Input: TWL4030/TWL60X0 changes (18 patch)
> 2. v3 of MFD/input/ASoC: twl6040: irq registration changes (5 patch)
> 3. v1 of ASoC/MFD: twl6040: PLL handling changes (6 patch)
> 4. ASoC: twl6040: Add back support for legacy mode (single patch)
> 
> The first series starts with a cleanup in the mach-omap2 directory
> (twl-common.c file created), and that is the reason we agreed that you
> are going to take this pull request.
> The rest of the changes are well contained, and should not cause merge
> conflict for 3.1. We have not sent patches for these components, so the
> changes to these are coming from one source.
> 
> As you have requested I have created the series on top of your
> devel-cleanup branch.

Thanks. Can you please add one more branch for cleanup only for me to
pull at your commit b252b0efb605b92a2f5d118e294d088d89cfd286
(OMAP3: Move common regulator configuration to twl-common)?

That way I can first pull that into cleanup and send that to Arnd.
Then we can do a separate twl-asoc branch so the cleanup stays
separate from new code.

I don't think there's a way for me to do a pull that ends at certain
commit with git.. Or at least I don't know how to do that short of
git reset --hard of some branch at that commit.

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-07-07 18:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07 11:48 [GIT PULL] TWL6040 MFD and followups Péter Ujfalusi
2011-07-07 18:29 ` Tony Lindgren [this message]
2011-07-07 18:46   ` Péter Ujfalusi
2011-07-07 19:20     ` Tony Lindgren
2011-07-07 19:36   ` 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=20110707182947.GM5783@atomide.com \
    --to=tony@atomide.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=sameo@linux.intel.com \
    /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.