All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Michal Marek <mmarek@suse.cz>,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	linux-sh <linux-sh@vger.kernel.org>
Subject: Re: [PATCH] sh: fix kconfig warning
Date: Tue, 24 Aug 2010 15:33:28 +0900	[thread overview]
Message-ID: <20100824063327.GA7384@linux-sh.org> (raw)
In-Reply-To: <1282579872-16609-1-git-send-email-lacombar@gmail.com>

On Mon, Aug 23, 2010 at 12:11:12PM -0400, Arnaud Lacombe wrote:
> warning: (SUPERH32) selects HAVE_HW_BREAKPOINT which has unmet direct dependencies (PERF_EVENTS)
> 
> This warning was causing Kconfig to segfault.
> 
> Signed-off-by: Arnaud Lacombe <lacombar@gmail.com>

This was already fixed by Sam, thanks anyways.

WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Michal Marek <mmarek@suse.cz>,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	linux-sh <linux-sh@vger.kernel.org>
Subject: Re: [PATCH] sh: fix kconfig warning
Date: Tue, 24 Aug 2010 06:33:28 +0000	[thread overview]
Message-ID: <20100824063327.GA7384@linux-sh.org> (raw)
In-Reply-To: <1282579872-16609-1-git-send-email-lacombar@gmail.com>

On Mon, Aug 23, 2010 at 12:11:12PM -0400, Arnaud Lacombe wrote:
> warning: (SUPERH32) selects HAVE_HW_BREAKPOINT which has unmet direct dependencies (PERF_EVENTS)
> 
> This warning was causing Kconfig to segfault.
> 
> Signed-off-by: Arnaud Lacombe <lacombar@gmail.com>

This was already fixed by Sam, thanks anyways.

  reply	other threads:[~2010-08-24  6:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23 16:11 [PATCH] sh: fix kconfig warning Arnaud Lacombe
2010-08-23 16:11 ` Arnaud Lacombe
2010-08-24  6:33 ` Paul Mundt [this message]
2010-08-24  6:33   ` Paul Mundt

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=20100824063327.GA7384@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=lacombar@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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.