From: "Lenar D. Tukhvatullin" <lenar@netroad.ru>
To: linux-mtd@lists.infradead.org
Subject: [PATCH] MTD: compatmac.h - workaround for touch_softlockup_watchdog
Date: Sat, 7 Jan 2006 15:24:05 +0300 [thread overview]
Message-ID: <20060107122405.GB24407@proxy.netroad.ru> (raw)
"Soft lockups detection" feature was added in 2.6.14 kernel.
In early kernels touch_softlockup_watchdog() is absent,
that causes compilation error of nand_base.c and onenand_base.c
Patch below adds workaround for kernels < 2.6.14:
=================================================================================
--- include/linux/mtd/compatmac.h.old Mon Nov 7 14:14:54 2005
+++ include/linux/mtd/compatmac.h Sat Jan 7 04:12:12 2006
@@ -223,6 +223,12 @@
#define class_destroy(cs) class_simple_destroy((struct class_simple *)cs)
#endif
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,14)
+static inline void touch_softlockup_watchdog(void)
+{
+}
+#endif
+
#ifndef list_for_each_entry_safe
/**
* list_for_each_entry_safe - iterate over list of given type safe against removal of list entry
=================================================================================
--
Lenar D. Tukhvatullin,
Ulyanovsk State Technical University
reply other threads:[~2006-01-07 12:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060107122405.GB24407@proxy.netroad.ru \
--to=lenar@netroad.ru \
--cc=linux-mtd@lists.infradead.org \
/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