From: RICARD Christophe <christophe.ricard@gmail.com>
To: Samuel Ortiz <sameo@linux.intel.com>, mike@altlinux.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 3.17-rc3 module dependency loops
Date: Thu, 04 Sep 2014 20:56:11 +0200 [thread overview]
Message-ID: <5408B5CB.9040906@gmail.com> (raw)
In-Reply-To: <20140904165500.GK2515@imap.altlinux.org>
Hi Michel,
Thank you for your feedback. I actually appology for the mistake.
However, the issue got already reported and a fix proposal was done at
the following location:
https://lists.01.org/pipermail/linux-nfc/2014-September/002918.html
Best Regards
Christophe
Le 04/09/2014 18:55, Michael Shigorin a écrit :
> Hello,
> I've spotted these depmod loops while building 3.17-rc3:
>
> depmod: ERROR: Found 6 modules in dependency cycles!
> depmod: ERROR: Cycle detected: st21nfcb -> ndlc -> nci -> nfc -> st21nfcb
> depmod: ERROR: Cycle detected: nci -> nfc -> nci
>
> Had to disable NFC_NCI, NFC_ST21NFCB.
>
> PS: not subscribed to LKML, CC please.
>
next prev parent reply other threads:[~2014-09-04 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 16:55 PROBLEM: 3.17-rc3 module dependency loops Michael Shigorin
2014-09-04 18:56 ` RICARD Christophe [this message]
2014-09-04 19:20 ` Michael Shigorin
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=5408B5CB.9040906@gmail.com \
--to=christophe.ricard@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@altlinux.org \
--cc=sameo@linux.intel.com \
/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