All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wim Van Sebroeck <wim@iguana.be>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Philippe De Muyter <phdm@macqel.be>
Subject: Re: linux-next: build failure after merge of the watchdog tree
Date: Mon, 10 Jan 2011 08:27:50 +0100	[thread overview]
Message-ID: <20110110072750.GL3801@infomag.iguana.be> (raw)
In-Reply-To: <20110110141250.78947d61.sfr@canb.auug.org.au>

Hi Stephen,

> After merging the watchdog tree, today's linux-next build (x86_64
> allmodconfig) failed like this:

This driver is for the m68K architecture. I apparently missed checking
the dependancy in Kconfig. I'll fix it today.

Kind regards,
Wim.


  reply	other threads:[~2011-01-10  7:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10  3:12 linux-next: build failure after merge of the watchdog tree Stephen Rothwell
2011-01-10  7:27 ` Wim Van Sebroeck [this message]
2011-01-10 12:27   ` [PATCH] watchdog,m68knommu: allow M548x watchdog compilation only for M548x Philippe De Muyter
2011-11-01  5:37 linux-next: build failure after merge of the watchdog tree Stephen Rothwell
2011-11-01 12:02 ` Mark Brown
2011-11-02 16:43   ` Wim Van Sebroeck
2014-09-26  5:40 Stephen Rothwell
2014-09-26  5:51 ` Guenter Roeck
2014-09-26  6:29   ` Stephen Rothwell
2014-09-26  6:49     ` Guenter Roeck
2014-09-26  5:56 ` Pramod Gurav
2014-09-26  6:12   ` Guenter Roeck
2014-09-26  6:34     ` Stephen Rothwell
2014-09-26  6:47       ` Guenter Roeck
2020-12-14  5:23 Stephen Rothwell
2020-12-14  6:09 ` Guenter Roeck
2020-12-16  2:56   ` Stephen Rothwell
2020-12-16  4:11     ` Guenter Roeck
2020-12-16 15:27     ` Wim Van Sebroeck
2020-12-17  7:04       ` Wim Van Sebroeck
2021-06-21  5:38 Stephen Rothwell
2021-06-21  8:08 ` Wim Van Sebroeck
2021-06-22 15:27 ` Vaittinen, Matti

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=20110110072750.GL3801@infomag.iguana.be \
    --to=wim@iguana.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=phdm@macqel.be \
    --cc=sfr@canb.auug.org.au \
    /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.