mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Roman Zippel <zippel@linux-m68k.org>
Subject: Re: [PATCH] Kconfig:  Remove DEBUG_RWSEMS
Date: Thu, 8 Feb 2007 14:19:30 -0800	[thread overview]
Message-ID: <20070208141930.a99f91f2.randy.dunlap@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702081701530.4820@localhost.localdomain>

On Thu, 8 Feb 2007 17:06:12 -0500 (EST) Robert P. J. Day wrote:

> 
>   Remove the final vestiges of the kernel config option DEBUG_RWSEMS,
> since it has no value, at least at the moment.
> 
> Signed-off-by: Robert P. J. Day <rpjday@mindspring.com>

Acked-by: Randy Dunlap <randy.dunlap@oracle.com>

no other uses of it.

> ---
> 
>   my apologies for pushing this so high up the food chain, but i want
> to submit another patch that sits *right* next to this one in the
> Kconfig.debug file so i either have to do it in two steps, or submit
> those two changes as a single patch, and i don't like doing that.
> 
>   so if this can go in in short order, well, that would be just ducky.
> if it can't, then just toss it and i'll move on to that second patch.
> 
> 
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index 5c26818..356a5ab 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -181,19 +181,11 @@ config DEBUG_MUTEXES
>  	 This feature allows mutex semantics violations to be detected and
>  	 reported.
> 
> -config DEBUG_RWSEMS
> -	bool "RW-sem debugging: basic checks"
> -	depends on DEBUG_KERNEL
> -	help
> -	 This feature allows read-write semaphore semantics violations to
> -	 be detected and reported.
> -
>  config DEBUG_LOCK_ALLOC
>  	bool "Lock debugging: detect incorrect freeing of live locks"
>  	depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
>  	select DEBUG_SPINLOCK
>  	select DEBUG_MUTEXES
> -	select DEBUG_RWSEMS
>  	select LOCKDEP
>  	help
>  	 This feature will check whether any held lock (spinlock, rwlock,
> @@ -209,7 +201,6 @@ config PROVE_LOCKING
>  	select LOCKDEP
>  	select DEBUG_SPINLOCK
>  	select DEBUG_MUTEXES
> -	select DEBUG_RWSEMS
>  	select DEBUG_LOCK_ALLOC
>  	default n
>  	help
> 
> -- 

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

      reply	other threads:[~2007-02-08 22:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-08 22:06 Robert P. J. Day
2007-02-08 22:19 ` Randy Dunlap [this message]

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=20070208141930.a99f91f2.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.com \
    --cc=torvalds@linux-foundation.org \
    --cc=zippel@linux-m68k.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

all inboxes | Powered by JetHome®