linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: next-2008-11-28: bfin vs cpumask fixlet
Date: Mon, 1 Dec 2008 15:17:57 +1030	[thread overview]
Message-ID: <200812011517.57601.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20081128151755.GA27660@x200.localdomain>

On Saturday 29 November 2008 01:47:55 Alexey Dobriyan wrote:
> --- a/arch/blackfin/kernel/time-ts.c
> +++ b/arch/blackfin/kernel/time-ts.c
> @@ -162,7 +162,6 @@ static struct clock_event_device clockevent_bfin = {
>  	.name		= "bfin_core_timer",
>  	.features	= CLOCK_EVT_FEAT_PERIODIC | CLOCK_EVT_FEAT_ONESHOT,
>  	.shift		= 32,
> -	.cpumask	= CPU_MASK_CPU0,

Thanks Alexey, applied.

I grepped harder, and this seems to be the last one.

Cheers,
Rusty.

  reply	other threads:[~2008-12-01  4:48 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-28 10:36 linux-next: Tree for November 28 Stephen Rothwell
2008-11-28 15:17 ` next-2008-11-28: bfin vs cpumask fixlet Alexey Dobriyan
2008-12-01  4:47   ` Rusty Russell [this message]
2008-11-28 17:55 ` linux-next: Tree for November 28 (misc/tc1100) Randy Dunlap
2008-11-28 21:35   ` drivers/x86 (Was: Re: linux-next: Tree for November 28 (misc/tc1100)) Stephen Rothwell
2008-11-28 21:50     ` Len Brown
     [not found]       ` <alpine.LFD.2.00.0811281702570.24773@localhost.localdomain>
2008-11-28 22:09         ` [RFC PATCH] x86: create drivers/x86/ from drivers/misc/ Len Brown
2008-11-28 22:35           ` Sam Ravnborg
2008-11-28 23:16             ` Len Brown
2008-11-29  0:16               ` Henrique de Moraes Holschuh
2008-12-01  4:35                 ` Len Brown
2008-11-29  1:00               ` Randy Dunlap
2008-11-29  7:23               ` Sam Ravnborg
2008-11-29  7:38               ` Sam Ravnborg
2008-12-01  5:00                 ` Len Brown
2008-12-01  5:54                   ` Sam Ravnborg
2008-12-01  6:02                 ` [RFC PATCH v2] create drivers/platform/x86/ " Len Brown
2008-12-01  6:03                   ` [PATCH 1/2] drivers/misc/Makefile, Kconfig: cleanup Len Brown
2008-12-01  7:41                     ` Sam Ravnborg
2008-12-01 19:23                       ` Len Brown
2008-12-01  6:05                   ` [PATCH 2/2] create drivers/platform/x86/ from drivers/misc/ Len Brown
2008-12-01  7:48                   ` [RFC PATCH v2] " Ingo Molnar
2008-12-01 19:12                     ` Len Brown
2008-11-28 23:20             ` [RFC PATCH] x86: create drivers/x86/ " Len Brown
2008-12-01  4:49               ` Randy Dunlap
2008-11-29  9:34     ` drivers/x86 (Was: Re: linux-next: Tree for November 28 (misc/tc1100)) Ingo Molnar
2008-12-01  4:29       ` Len Brown
2008-11-30 23:44 ` next-2008-11-28 : can't mount UDF DVD Laurent Riffard
2008-12-01  0:18   ` Marcin Slusarz
2008-12-01 19:28     ` Laurent Riffard
2008-12-01 23:22       ` [PATCH] udf: fix default mode and dmode options handling Marcin Slusarz
2008-12-02 13:38         ` Jan Kara

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=200812011517.57601.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=adobriyan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).