From: Don Zickus <dzickus@redhat.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: mingo@elte.hu, peterz@infradead.org, gorcunov@gmail.com,
aris@redhat.com, linux-kernel@vger.kernel.org,
randy.dunlap@oracle.com
Subject: Re: [PATCH 2/8] [nmi watchdog] touch_softlockup cleanups and softlockup_tick removal
Date: Wed, 12 May 2010 16:26:28 -0400 [thread overview]
Message-ID: <20100512202628.GK15159@redhat.com> (raw)
In-Reply-To: <20100512200652.GF10028@nowhere>
On Wed, May 12, 2010 at 10:06:54PM +0200, Frederic Weisbecker wrote:
> > diff --git a/kernel/sysctl.c b/kernel/sysctl.c
> > index 1083897..1fec781 100644
> > --- a/kernel/sysctl.c
> > +++ b/kernel/sysctl.c
> > @@ -827,15 +827,6 @@ static struct ctl_table kern_table[] = {
> > .extra1 = &zero,
> > .extra2 = &one,
> > },
> > - {
> > - .procname = "softlockup_thresh",
> > - .data = &softlockup_thresh,
> > - .maxlen = sizeof(int),
> > - .mode = 0644,
> > - .proc_handler = proc_dosoftlockup_thresh,
> > - .extra1 = &neg_one,
> > - .extra2 = &sixty,
> > - },
>
>
>
> I wonder about the ABI breakage.
>
> But I suspect few userspace tools use it though, since this is
> mostly for kernel dev.
There is no breakage, this chunk of code was duplicated later in the file.
I am just removing the duplicated bits to simplify the SOFTLOCKUP Kconfig
stuff.
Cheers,
Don
next prev parent reply other threads:[~2010-05-12 20:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 21:11 [PATCH 0/8] lockup detector changes Don Zickus
2010-05-07 21:11 ` [PATCH 1/8] [watchdog] combine nmi_watchdog and softlockup Don Zickus
2010-05-12 19:55 ` Frederic Weisbecker
2010-05-13 6:51 ` [tip:perf/nmi] lockup_detector: Combine nmi_watchdog and softlockup detector tip-bot for Don Zickus
2010-05-07 21:11 ` [PATCH 2/8] [nmi watchdog] touch_softlockup cleanups and softlockup_tick removal Don Zickus
2010-05-12 20:06 ` Frederic Weisbecker
2010-05-12 20:26 ` Don Zickus [this message]
2010-05-12 20:28 ` Frederic Weisbecker
2010-05-12 20:56 ` Don Zickus
2010-05-12 21:00 ` Frederic Weisbecker
2010-05-12 21:38 ` Cyrill Gorcunov
2010-05-12 21:50 ` Don Zickus
2010-05-13 15:53 ` Cyrill Gorcunov
2010-05-13 16:04 ` Don Zickus
2010-05-13 6:52 ` [tip:perf/nmi] lockup_detector: Touch_softlockup " tip-bot for Don Zickus
2010-05-07 21:11 ` [PATCH 3/8] [watchdog] remove old softlockup code Don Zickus
2010-05-13 6:52 ` [tip:perf/nmi] lockup_detector: Remove " tip-bot for Don Zickus
2010-05-07 21:11 ` [PATCH 4/8] [watchdog] remove nmi_watchdog.c file Don Zickus
2010-05-13 6:52 ` [tip:perf/nmi] lockup_detector: Remove " tip-bot for Don Zickus
2010-05-07 21:11 ` [PATCH 5/8] [x86] watchdog: move trigger_all_cpu_backtrace to its own die_notifier Don Zickus
2010-05-13 6:53 ` [tip:perf/nmi] x86: Move " tip-bot for Don Zickus
2010-05-07 21:11 ` [PATCH 6/8] [x86] watchdog: cleanup hw_nmi.c cruft Don Zickus
2010-05-13 6:53 ` [tip:perf/nmi] x86: Cleanup " tip-bot for Don Zickus
2010-05-07 21:11 ` [PATCH 7/8] [watchdog] resolve softlockup.c conflicts Don Zickus
2010-05-07 21:11 ` [PATCH 8/8] [watchdog] separate touch_nmi_watchdog code path from touch_watchdog Don Zickus
2010-05-13 6:53 ` [tip:perf/nmi] lockup_detector: Separate " tip-bot for Don Zickus
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=20100512202628.GK15159@redhat.com \
--to=dzickus@redhat.com \
--cc=aris@redhat.com \
--cc=fweisbec@gmail.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=randy.dunlap@oracle.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;
as well as URLs for NNTP newsgroup(s).