From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: "next" branch update
Date: Fri, 12 Jun 2009 23:59:27 +1000 [thread overview]
Message-ID: <1244815167.7172.166.camel@pasglop> (raw)
In-Reply-To: <ed82fe3e0906120654m22f38569jea21dfaf9449c34c@mail.gmail.com>
On Fri, 2009-06-12 at 08:54 -0500, Timur Tabi wrote:
> On Fri, Jun 12, 2009 at 2:29 AM, Benjamin
> Herrenschmidt<benh@kernel.crashing.org> wrote:
> > I pushed the following commits, along with merging Linus tree in today.
>
> Is there a reason you keep ignoring my patch?
Other than I hate you ? just kidding :-)
> [PATCH 1/2 v9] powerpc: introduce macro spin_event_timeout()
>
> There is PowerPC code in the ALSA tree that depends on my patch, so
> that code will break if you don't push my patch upstream.
I know, and you may have noticed I haven't sent a pull request to Linus
yet... I was planning on scrubbing patchwork once more today and got
sidetracked with fixing the breakage that went into mainline already
while I was not looking :-)
I haven't closed powerpc-next, I know I'm late, but don't worry, your
patch is on my todo list.
Cheers,
Ben.
next prev parent reply other threads:[~2009-06-12 14:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 7:29 "next" branch update Benjamin Herrenschmidt
2009-06-12 13:54 ` Timur Tabi
2009-06-12 13:59 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-28 4:14 Benjamin Herrenschmidt
2009-07-28 7:54 ` Martyn Welch
2009-06-10 3:14 Benjamin Herrenschmidt
2009-06-10 4:13 ` Grant Likely
2009-06-10 6:07 ` Timur Tabi
2009-06-11 17:05 ` Josh Boyer
2009-06-02 3:03 Benjamin Herrenschmidt
2009-06-02 3:26 ` Grant Likely
2009-06-02 3:44 ` Benjamin Herrenschmidt
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=1244815167.7172.166.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@freescale.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.