public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dhowells@redhat.com, Herbert Xu <herbert@gondor.hengli.com.au>,
	gregkh@suse.de, linux-kernel@vger.kernel.org,
	linux-crypto@vger.kernel.org
Subject: Re: Initcall ordering problem (TTY vs modprobe vs MD5) and cryptomgr problem
Date: Fri, 06 Aug 2010 03:23:30 +0100	[thread overview]
Message-ID: <11274.1281061410@redhat.com> (raw)
In-Reply-To: <AANLkTi=+-Y2GOZYAZHeaX+op3XB9AY5S85rfJD3jSDvz@mail.gmail.com>

Linus Torvalds <torvalds@linux-foundation.org> wrote:

> People always think that their magical code is so important. I tell
> you up-front that is absolutely is not. Just remove the crap entirely,
> please.

Even if he does remove it, that still leaves the problem that modprobe can be
invoked and fail before tty_init() gets called:-/

I wonder if tty_init() should be moved up, perhaps to immediately after
chrdev_init().

David

  reply	other threads:[~2010-08-06  2:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-06  1:01 Initcall ordering problem (TTY vs modprobe vs MD5) and cryptomgr problem David Howells
2010-08-06  1:17 ` Herbert Xu
2010-08-06  1:40   ` Herbert Xu
2010-08-06  2:01     ` Linus Torvalds
2010-08-06  2:23       ` David Howells [this message]
2010-08-06  2:27         ` Linus Torvalds
2010-08-06  2:35       ` Herbert Xu
2010-08-06  4:20         ` Linus Torvalds
2010-08-06  4:50           ` Kyle Moffett
2010-08-06  8:06             ` Olivier Galibert
2010-08-06  8:39               ` Herbert Xu
2010-08-06 11:13                 ` Evgeniy Polyakov
2010-08-06 15:22               ` Linus Torvalds
2010-08-06  2:27     ` David Howells

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=11274.1281061410@redhat.com \
    --to=dhowells@redhat.com \
    --cc=gregkh@suse.de \
    --cc=herbert@gondor.hengli.com.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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