All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: mingo@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:timers/core] tick/broadcast: Make tick_broadcast_setup_oneshot() static
Date: Fri, 17 Mar 2017 11:25:13 -0700	[thread overview]
Message-ID: <20170317182513.GM10239@codeaurora.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1703171842420.3538@nanos>

On 03/17, Thomas Gleixner wrote:
> On Fri, 17 Mar 2017, tip-bot for Stephen Boyd wrote:
> 
> > Commit-ID:  f5e38e7c86427bd7c01b259a9655cb6a9aba5cb7
> > Gitweb:     http://git.kernel.org/tip/f5e38e7c86427bd7c01b259a9655cb6a9aba5cb7
> > Author:     Stephen Boyd <sboyd@codeaurora.org>
> > AuthorDate: Thu, 16 Mar 2017 18:08:14 -0700
> > Committer:  Thomas Gleixner <tglx@linutronix.de>
> > CommitDate: Fri, 17 Mar 2017 18:24:59 +0100
> > 
> > tick/broadcast: Make tick_broadcast_setup_oneshot() static
> 
> Zapped it due to 0-day failure

Urgh, I forgot to test all possible combinations. Sorry. I'll fix
it and resend.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2017-03-17 18:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-17  1:08 [PATCH 1/2] hrtimer: hrtimer_peek_ahead_timers() is gone Stephen Boyd
2017-03-17  1:08 ` [PATCH 2/2] tick/broadcast: tick_broadcast_setup_oneshot() isn't exported Stephen Boyd
2017-03-17 17:28   ` [tip:timers/core] tick/broadcast: Make tick_broadcast_setup_oneshot() static tip-bot for Stephen Boyd
2017-03-17 17:43     ` Thomas Gleixner
2017-03-17 18:25       ` Stephen Boyd [this message]
2017-03-17 17:27 ` [tip:timers/core] hrtimer: Remove hrtimer_peek_ahead_timers() leftovers tip-bot for Stephen Boyd

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=20170317182513.GM10239@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --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 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.