linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jason Wessel <jason.wessel@windriver.com>
Subject: Re: linux-next: manual merge of the tip tree with the kgdb tree
Date: Fri, 14 May 2010 10:00:43 -0400	[thread overview]
Message-ID: <20100514140043.GP15159@redhat.com> (raw)
In-Reply-To: <20100514141406.68a6bf6f.sfr@canb.auug.org.au>

On Fri, May 14, 2010 at 02:14:06PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the tip tree got a conflict in
> kernel/Makefile between commit 7d63ecbc5ce463c8ba60e357eafaf47774521f1a
> ("Move kernel/kgdb.c to kernel/debug/debug_core.c") from the kgdb tree
> and commit 58687acba59266735adb8ccd9b5b9aa2c7cd205b ("lockup_detector:
> Combine nmi_watchdog and softlockup detector") from the tip tree.
> 
> Just context changes.  I fixed it up (see below) and can carry the fix
> as necessary.

ACK

for the LOCK_DETECTOR and SOFTLOCKUP parts.

Cheers,
Don

> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au
> 
> diff --cc kernel/Makefile
> index 4313d0e,34d123b..0000000
> --- a/kernel/Makefile
> +++ b/kernel/Makefile
> @@@ -68,17 -68,16 +68,17 @@@ obj-$(CONFIG_USER_NS) += user_namespace
>   obj-$(CONFIG_PID_NS) += pid_namespace.o
>   obj-$(CONFIG_IKCONFIG) += configs.o
>   obj-$(CONFIG_RESOURCE_COUNTERS) += res_counter.o
> - obj-$(CONFIG_STOP_MACHINE) += stop_machine.o
> + obj-$(CONFIG_SMP) += stop_machine.o
>   obj-$(CONFIG_KPROBES_SANITY_TEST) += test_kprobes.o
>  -obj-$(CONFIG_AUDIT) += audit.o auditfilter.o audit_watch.o
>  +obj-$(CONFIG_AUDIT) += audit.o auditfilter.o
>   obj-$(CONFIG_AUDITSYSCALL) += auditsc.o
>  -obj-$(CONFIG_GCOV_KERNEL) += gcov/
>  +obj-$(CONFIG_AUDIT_WATCH) += audit_watch.o
>   obj-$(CONFIG_AUDIT_TREE) += audit_tree.o
>  +obj-$(CONFIG_GCOV_KERNEL) += gcov/
>   obj-$(CONFIG_KPROBES) += kprobes.o
>  -obj-$(CONFIG_KGDB) += kgdb.o
>  +obj-$(CONFIG_KGDB) += debug/
> - obj-$(CONFIG_DETECT_SOFTLOCKUP) += softlockup.o
>   obj-$(CONFIG_DETECT_HUNG_TASK) += hung_task.o
> + obj-$(CONFIG_LOCKUP_DETECTOR) += watchdog.o
>   obj-$(CONFIG_GENERIC_HARDIRQS) += irq/
>   obj-$(CONFIG_SECCOMP) += seccomp.o
>   obj-$(CONFIG_RCU_TORTURE_TEST) += rcutorture.o

  reply	other threads:[~2010-05-14 14:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-14  4:14 linux-next: manual merge of the tip tree with the kgdb tree Stephen Rothwell
2010-05-14 14:00 ` Don Zickus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-02-01  6:29 Stephen Rothwell
2010-02-01 15:46 ` Jason Wessel
2010-02-01 23:25   ` Stephen Rothwell
2010-01-14  5:13 Stephen Rothwell
2010-01-14  9:26 ` Ingo Molnar
2010-01-14 15:01   ` Jason Wessel
2010-01-14 15:20     ` Steven Rostedt
2010-01-14 15:49       ` Jason Wessel
2009-10-28  7:04 Stephen Rothwell

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=20100514140043.GP15159@redhat.com \
    --to=dzickus@redhat.com \
    --cc=hpa@zytor.com \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.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 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).