From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: "Linux kernel mailing list" <linux-kernel@vger.kernel.org>,
dhowells@redhat.com, rth@twiddle.net
Subject: Re: [PATCH] Centralize the selection for debugging semaphores.
Date: Wed, 31 Jan 2007 15:00:00 +0100 [thread overview]
Message-ID: <6bffcb0e0701310600s192f462aw18c96dce5630fe25@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701310852460.4816@CPE00045a9c397f-CM001225dbafb6>
On 31/01/07, Robert P. J. Day <rpjday@mindspring.com> wrote:
> On Wed, 31 Jan 2007, Michal Piotrowski wrote:
>
> > On 31/01/07, Robert P. J. Day <rpjday@mindspring.com> wrote:
> > >
> > > Centralize the kernel config option for debugging semaphores and
> > > modify the macro for frv to use that config option instead.
> > >
> > > Signed-off-by: Robert P. J. Day <rpjday@mindspring.com>
> > [..]
> > > +config DEBUG_SEMAPHORE
> > > + bool "Semaphore debugging"
> > > + depends on DEBUG_KERNEL
> > > + default n
> > > + help
> > > + If you say Y here then semaphore processing will issue lots of
> > > + verbose debugging messages. If you suspect a semaphore problem or
> > > a
> > > + kernel hacker asks for this option then say Y. Otherwise say N.
> > > +
> > > + At the moment, this is implemented only by alpha and frv.
> >
> > IMHO this option should stay in arch/{alpha,frv}/Kconfig.debug
>
> any particular reason?
Only this
"At the moment, this is implemented only by alpha and frv."
It depends on architecture.
> and note that it's currently *not* in
> arch/frv/Kconfig.debug -- it's hard-coded with a macro name that's not
> the same as the config option, and i don't really see the advantage of
> having each architecture implement precisely the same feature in
> different and incompatible ways. but i'm willing to be convinced
> otherwise.
>
> rday
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
next prev parent reply other threads:[~2007-01-31 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 13:32 Robert P. J. Day
2007-01-31 13:44 ` Michal Piotrowski
2007-01-31 13:54 ` Robert P. J. Day
2007-01-31 14:00 ` Michal Piotrowski [this message]
2007-01-31 14:20 ` Robert P. J. Day
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=6bffcb0e0701310600s192f462aw18c96dce5630fe25@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
--cc=rth@twiddle.net \
/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
all inboxes | Powered by JetHome®