Linux Hotplug development
 help / color / mirror / Atom feed
From: Allin Cottrell <cottrell@wfu.edu>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev: disable mtd_probe?
Date: Mon, 18 Jul 2011 21:37:50 +0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1107181733120.2541@myrtle> (raw)
In-Reply-To: <alpine.LNX.2.00.1107181640050.10649@waverley.Belkin>

On Mon, 18 Jul 2011, Kay Sievers wrote:

> On Mon, Jul 18, 2011 at 22:45, Allin Cottrell <cottrell@wfu.edu> wrote:
>> Since the new mechanism for enabling/disabling selected components of the
>> udev "extras" was introduced it hasn't been possible to disable mtd_probe,
>> so far as I can see.
>>
>> Could we please have that option, unless there are compelling reasons to the
>> contrary? The MTD stuff drags in a bunch of
>> dependencies.
>
> No problem with the patch or the option [...]

Good, thanks.

> but: Dependencies? A bunch? I don't see any. Not even the rules 
> are doing anything, if no mtd devices are present.

Maybe I'm misunderstanding something, but I thought I had to install 
the mtd-utils and/or configure MTD support into the kernel. 
Certainly, the mtd_probe build bombs out on my system with mtd.h not 
found. And if the mtd-utils are needed, they drag in attr and 
libacl.

--
Allin Cottrell
Department of Economics
Wake Forest University

  parent reply	other threads:[~2011-07-18 21:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 20:45 udev: disable mtd_probe? Allin Cottrell
2011-07-18 21:10 ` Kay Sievers
2011-07-18 21:17 ` Gabor Z. Papp
2011-07-18 21:19 ` Kay Sievers
2011-07-18 21:22 ` Gabor Z. Papp
2011-07-18 21:37 ` Allin Cottrell [this message]
2011-07-18 21:40 ` Kay Sievers
2011-07-18 21:44 ` Kay Sievers
2011-07-18 21:49 ` Kay Sievers
2011-07-19 16:06 ` Allin Cottrell
2011-07-19 20:06 ` Kay Sievers

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=alpine.DEB.2.00.1107181733120.2541@myrtle \
    --to=cottrell@wfu.edu \
    --cc=linux-hotplug@vger.kernel.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