public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [git pull] kmemcheck updates for -tip
Date: Tue, 1 Jul 2008 22:24:07 +0200	[thread overview]
Message-ID: <20080701202407.GC4896@elte.hu> (raw)
In-Reply-To: <20080701201855.GA22686@damson.getinternet.no>


* Vegard Nossum <vegard.nossum@gmail.com> wrote:

> Hi Ingo,
> 
> Please pull the 'for-tip' branch of
> 
>     git://git.kernel.org/pub/scm/linux/kernel/git/vegard/kmemcheck.git for-tip
> 
> to receive the following changes:
> 
> Vegard Nossum (3):
>       kmemcheck: fix sparse warnings
>       softirq: raise the right softirq
>       kmemcheck: use the proper comment style

pulled into tip/kmemcheck, thanks Vegard!

btw:

> --- a/kernel/softirq.c
> +++ b/kernel/softirq.c
> @@ -399,7 +399,7 @@ void __tasklet_hi_schedule_first(struct tasklet_struct *t)
>  
>  	t->next = __get_cpu_var(tasklet_hi_vec).head;
>  	__get_cpu_var(tasklet_hi_vec).head = t;
> -	__raise_softirq_irqoff(TASKLET_SOFTIRQ);
> +	__raise_softirq_irqoff(HI_SOFTIRQ);
>  }

i think i'll put this one into core/softirqs as well.

	Ingo

  reply	other threads:[~2008-07-01 20:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01 20:18 [git pull] kmemcheck updates for -tip Vegard Nossum
2008-07-01 20:24 ` Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-22 13:57 [GIT PULL] " Vegard Nossum
2009-02-22 16:44 ` Ingo Molnar
2009-02-22 17:00   ` Frederic Weisbecker
2009-02-22 17:05     ` Sitsofe Wheeler
2009-02-22 17:06     ` Vegard Nossum
2009-02-26 14:01 Vegard Nossum
2009-02-26 15:23 ` Ingo Molnar

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=20080701202407.GC4896@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=tglx@linutronix.de \
    --cc=vegard.nossum@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox