From: Jason Cooper <jason@lakedaemon.net>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Andrew Lunn <andrew@lunn.ch>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
John Stultz <john.stultz@linaro.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [GIT PULL] clockevents/clocksource: Add Marvell Orion SoC timer
Date: Sun, 7 Jul 2013 20:04:01 -0400 [thread overview]
Message-ID: <20130708000401.GC11908@titan.lakedaemon.net> (raw)
In-Reply-To: <51D99B1B.7050106@linaro.org>
On Sun, Jul 07, 2013 at 06:45:15PM +0200, Daniel Lezcano wrote:
> On 07/07/2013 05:30 PM, Thomas Gleixner wrote:
> > On Sun, 7 Jul 2013, Jason Cooper wrote:
> >> Sure, but to be clear, Daniel, please drop this patch from your tree. I
> >> have no desire to create an out-of-tree dependency if we can avoid it.
> >> It has a habit of going horribly wrong [1].
> >>
> >> I'll cherry-pick
> >>
> >> 0c1dcfd clocksource: Add Marvell Orion SoC timer
> >
> > Don't do that. Do a git fetch on that branch and then git merge
> > 0c1dcfd. The patches before that Marvel commit are already in Linus
> > tree. That way it does not matter who sends first or not.
> >
> > We don't force others to drop stuff and cherry picking is a nuisance
> > as well as you end up with two different commits doing the same thing.
> >
> > Also for the next merge window: Can we please let everything under
> > drivers/clocksoure go through Daniels and my trees?
> >
> > I'm starting to be grumpy about anyone thinking that this directory is
> > a public dump ground with no rules.
>
> Yes I agree. I will meet John this week and we will sort out this and
> define a clear set of rules to prevent that to happen again.
Oh god no! The rules we have are fine. "Defer to the appropriate
maintainer first." Which I did (that's why the patch is in your tree
;-) ). A mistake happened, and we're working together to find the best
solution.
The last thing we need is more bureaucratic crap.
thx,
Jason.
next prev parent reply other threads:[~2013-07-08 0:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 19:59 Daniel Lezcano
2013-07-07 11:44 ` Sebastian Hesselbarth
2013-07-07 13:10 ` Thomas Gleixner
2013-07-07 14:46 ` Jason Cooper
2013-07-07 15:30 ` Thomas Gleixner
2013-07-07 16:45 ` Daniel Lezcano
2013-07-08 0:04 ` Jason Cooper [this message]
2013-07-07 23:58 ` Jason Cooper
2013-07-08 8:45 ` Thomas Gleixner
2013-07-08 15:28 ` managing out-of-tree deps for arm-soc in a single window was: " Jason Cooper
2013-07-16 15:55 ` Daniel Lezcano
2013-07-24 19:49 ` Jason Cooper
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=20130708000401.GC11908@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=andrew@lunn.ch \
--cc=daniel.lezcano@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®