Re: [PATCH] crypto: Use padlock.ko only as a module

Hi Scott,

On Sunday 29 April 2007, Simon Arlott wrote:
> Ideally I'd just remove that module completely, all it does is 
> trigger the loading of the other two modules when modules are 
> used - so I'll submit a patch for that instead.

That's much better! 

When you force a feature to be a module on a kernel without 
module support, it will effectivly be disabled.

And if it is so simple to do the same in userspace like you suggest,
than that's much better.

Best Regards

Ingo Oeser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH] crypto: Use padlock.ko only as a module
    • From: Simon Arlott <[email protected]>
  • Re: [PATCH] crypto: Use padlock.ko only as a module
    • From: Randy Dunlap <[email protected]>
  • Re: [PATCH] crypto: Use padlock.ko only as a module
    • From: Simon Arlott <[email protected]>

• Prev by Date: Re: Linux 2.6.21
• Next by Date: Re: Linux 2.6.21
• Previous by thread: Re: [PATCH] crypto: Use padlock.ko only as a module
• Next by thread: [PATCH] i386: introduce voyager smp_ops, fix voyager build
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]