From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [git pull] core/softirq for v2.6.27
Date: Mon, 14 Jul 2008 18:31:41 +0200 [thread overview]
Message-ID: <20080714163141.GA21068@elte.hu> (raw)
In-Reply-To: <20080714092215.0efd7fa3.akpm@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> wrote:
> On Mon, 14 Jul 2008 16:42:43 +0200 Ingo Molnar <mingo@elte.hu> wrote:
> >
>
> It would be nice if these short-form summaries were to include the
> commit IDs. eg:
>
> Carlos R. Mafra (1):
> Remove argument from open_softirq which is always NULL (962cf36)
yeah, but not sure whether git-shortlog can do that and this shortlog is
the Preferred Way of getting pull requests.
I'm using the sha1's myself for non-shortlog formats, like:
earth4:~/tip> git-log-line linus..core/softirq
0f476b6: softirq: remove irqs_disabled warning from local_bh_enable
4620b49: softirq: remove initialization of static per-cpu variable
962cf36: Remove argument from open_softirq which is always NULL
where git-log-line does the obvious single-line shortcut:
git log --no-merges --pretty=format:"%h: %s" $@
> > Carlos R. Mafra (1):
> > Remove argument from open_softirq which is always NULL
> >
> > Johannes Berg (1):
> > softirq: remove irqs_disabled warning from local_bh_enable
>
> This doesn't remove the warning? (Nor should it)
>
> +static inline void _local_bh_enable_ip(unsigned long ip)
> {
> + WARN_ON_ONCE(in_irq() || irqs_disabled());
> - WARN_ON_ONCE(in_irq());
> - WARN_ON_ONCE(irqs_disabled());
>
> It just makes it a bit less useful.
hm, it does more than that - this commit (0f476b6d9) actually caught a
real bug/lockup on one of my testboxes, see this (in v2.6.26) fix:
| commit c5643cab7bf663ae049b11be43de8819683176dd
| Author: Ingo Molnar <mingo@elte.hu>
| Date: Mon Jun 23 10:41:23 2008 +0200
|
| [netdrvr] 3c59x: remove irqs_disabled warning from local_bh_enable
|
| Original Author: Michael Buesch <mb@bu3sch.de>
|
| net, vortex: fix lockup
[ i didnt send it to v2.6.26 because it came relatively late, it touches
a sensitive, #ifdef laden piece of code and it was unknown how many
false positives it would trigger. But it's perfect for v2.6.27. ]
Ingo
next prev parent reply other threads:[~2008-07-14 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 14:42 [git pull] core/softirq for v2.6.27 Ingo Molnar
2008-07-14 16:22 ` Andrew Morton
2008-07-14 16:31 ` Ingo Molnar [this message]
2008-07-14 16:44 ` Andrew Morton
2008-07-14 16:48 ` Ingo Molnar
2008-07-14 17:13 ` Linus Torvalds
2008-07-14 18: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=20080714163141.GA21068@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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