All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Thierry Reding
	<thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>,
	Prashant Gaikwad
	<pgaikwad-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	ARM kernel mailing list
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Conflicts between Tegra PWM tree and common clock patches
Date: Mon, 02 Jul 2012 11:35:04 -0600	[thread overview]
Message-ID: <4FF1DBC8.2000406@wwwdotorg.org> (raw)

Thierry,

The following commits in your PWM tree conflict with some Tegra clock
driver re-structuring that's part of the common clock conversion on Tegra.

df6da47 ARM: tegra: Provide clock for only one PWM controller
65e7385 ARM: tegra: Fix PWM clock programming

To alleviate this, could we either:

a) Remove those two commits from your tree and into the Tegra tree. I
think this won't cause any runtime issues, since Tegra PWM is a feature
we aren't using yet, so it's OK if the branch it's made to work in is
not the PWM branch.

b) If your branch is stable, I can merge it into the Tegra tree in order
to resolve the conflicts there. However, for this to work, you need to
100% guarantee that the branch won't be rebased between now and when you
send Linus a pull request for 3.6.

Note that I'm out on Wednesday this week for 4th July holiday, and then
leaving on vacation for 2 weeks on July 8th, so we need to resolve this
quickly if we are to merge the Tegra common clock conversion before I
leave. Also, once we do (a) or (b) above, Prashant needs to rebase his
patches on the result, and he's in India, so there's a big time-zone
delay there too.

Sorry, when I ack'd the Tegra clock patches for the PWM tree, I don't
believe the common clock conversion was on the horizon.

Thanks!

WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: Conflicts between Tegra PWM tree and common clock patches
Date: Mon, 02 Jul 2012 11:35:04 -0600	[thread overview]
Message-ID: <4FF1DBC8.2000406@wwwdotorg.org> (raw)

Thierry,

The following commits in your PWM tree conflict with some Tegra clock
driver re-structuring that's part of the common clock conversion on Tegra.

df6da47 ARM: tegra: Provide clock for only one PWM controller
65e7385 ARM: tegra: Fix PWM clock programming

To alleviate this, could we either:

a) Remove those two commits from your tree and into the Tegra tree. I
think this won't cause any runtime issues, since Tegra PWM is a feature
we aren't using yet, so it's OK if the branch it's made to work in is
not the PWM branch.

b) If your branch is stable, I can merge it into the Tegra tree in order
to resolve the conflicts there. However, for this to work, you need to
100% guarantee that the branch won't be rebased between now and when you
send Linus a pull request for 3.6.

Note that I'm out on Wednesday this week for 4th July holiday, and then
leaving on vacation for 2 weeks on July 8th, so we need to resolve this
quickly if we are to merge the Tegra common clock conversion before I
leave. Also, once we do (a) or (b) above, Prashant needs to rebase his
patches on the result, and he's in India, so there's a big time-zone
delay there too.

Sorry, when I ack'd the Tegra clock patches for the PWM tree, I don't
believe the common clock conversion was on the horizon.

Thanks!

             reply	other threads:[~2012-07-02 17:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-02 17:35 Stephen Warren [this message]
2012-07-02 17:35 ` Conflicts between Tegra PWM tree and common clock patches Stephen Warren
     [not found] ` <4FF1DBC8.2000406-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-07-02 19:24   ` Thierry Reding
2012-07-02 19:24     ` Thierry Reding
     [not found]     ` <20120702192454.GA1299-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
2012-07-02 19:38       ` Stephen Warren
2012-07-02 19:38         ` Stephen Warren

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=4FF1DBC8.2000406@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pgaikwad-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@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.