All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Wim Van Sebroeck <wim@iguana.be>, Ralf Baechle <ralf@linux-mips.org>
Cc: Valentin Rothberg <valentinrothberg@gmail.com>,
	Guenter Roeck <linux@roeck-us.net>,
	linux-watchdog@vger.kernel.org, linux-mips@linux-mips.org,
	linux-kernel@vger.kernel.org
Subject: watchdog: SOC_MT7621?
Date: Wed, 04 Feb 2015 11:13:29 +0100	[thread overview]
Message-ID: <1423044809.23894.65.camel@x220> (raw)

John Crispin's commit 576c618cf659 ("watchdog: add MT7621 watchdog
support") was included in today's linux-next (ie, next 20150204). I
noticed because a script I use to check linux-next spotted a problem
with it.

That commit adds an (optional) dependency on the Kconfig symbol
SOC_MT7621. But there's no symbol SOC_MT7621 in linux-next yet.

(Note that there currently are two checks for CONFIG_SOC_MT7621 in
arch/mips/ralink/early_printk.c. I mentioned these checks in
https://lkml.org/lkml/2014/10/27/218 and in
https://lkml.org/lkml/2015/1/12/302 . John never replied to these
messages. Since I haven't received replies on other, more serious issues
in over three months I assume John has disappeared.)

Is SOC_MT7621 still being worked on?


Paul Bolle

             reply	other threads:[~2015-02-04 10:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 10:13 Paul Bolle [this message]
2015-02-04 10:19 ` watchdog: SOC_MT7621? John Crispin
2015-02-04 11:04   ` Paul Bolle
2015-02-04 11:10     ` John Crispin
2015-02-04 12:22       ` Paul Bolle
2015-02-04 13:59         ` Guenter Roeck
2015-02-04 14:14           ` John Crispin

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=1423044809.23894.65.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=ralf@linux-mips.org \
    --cc=valentinrothberg@gmail.com \
    --cc=wim@iguana.be \
    /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.