From: Christian Dietrich <christian.dietrich@informatik.uni-erlangen.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Reinhard Tartler <Reinhard.Tartler@informatik.uni-erlangen.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
vamos@i4.informatik.uni-erlangen.de, Julia Lawall <julia@diku.dk>
Subject: Re: [ANNOUNCE] undertaker 1.0
Date: Mon, 31 Jan 2011 14:00:24 +0100 [thread overview]
Message-ID: <86sjw9jkif.fsf@peer.zerties.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1101282126210.31804@localhost6.localdomain6> (Thomas Gleixner's message of "Fri, 28 Jan 2011 21:41:18 +0100 (CET)")
Thomas Gleixner <tglx@linutronix.de> writes:
> The one in manage.c is not:
>
> 921 #ifdef CONFIG_IRQ_RELEASE_METHOD
>
> CONFIG_IRQ_RELEASE_METHOD is set by arch/um. Ditto for include/linux/irq.h
This problem was the result of an implementation bug. We didn't create a
feature model for um. This is now fixed in our master branch and will be
in the next minor release.
> It'd be nice if the web interface would have a knob to jump to the
> next red section. Scrolling through is annoying.
I generated a new code browser for -rc2[1]. There you can press 'n' to jump
to the next defect. I've only tested the javascript code with chromium,
but it should work anywhere else too.
[1] http://www4.informatik.uni-erlangen.de/Research/VAMOS/linux-trees/v2.6.38-rc2/
--
(λ x . x x) (λ x . x x) -- See how beautiful the lambda is
No documentation is better than bad documentation
next prev parent reply other threads:[~2011-01-31 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 11:56 [ANNOUNCE] undertaker 1.0 Reinhard Tartler
2011-01-28 20:41 ` Thomas Gleixner
2011-01-31 13:00 ` Christian Dietrich [this message]
2011-01-31 13:23 ` Thomas Gleixner
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=86sjw9jkif.fsf@peer.zerties.org \
--to=christian.dietrich@informatik.uni-erlangen.de \
--cc=Reinhard.Tartler@informatik.uni-erlangen.de \
--cc=julia@diku.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vamos@i4.informatik.uni-erlangen.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.