Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Thomas DEBESSE <thomas.debesse+debian@gmail.com>, 598518@bugs.debian.org
Cc: maximilian attems <max@stro.at>,
	linux-ide@vger.kernel.org, Tejun Heo <htejun@gmail.com>
Subject: Re: Bug#598518: linux-image-2.6-686: ata_piix module loaded before ahci module deactivate hotplug support (regression from lenny)
Date: Wed, 6 Oct 2010 19:33:21 +0100	[thread overview]
Message-ID: <20101006183321.GU13095@decadent.org.uk> (raw)
In-Reply-To: <AANLkTimUEpq1V=eSammBk9M0GHVRjZgfSBCjXQ36o95_@mail.gmail.com>

On Wed, Oct 06, 2010 at 07:04:48PM +0200, Thomas DEBESSE wrote:
[...]
> Nothing seems to be interesting here...
> 
> Where can I find modules.order ?
> Or where write it and how ?
 
modules.order is generated during the kernel build process and will be
copied into the initramfs by update-initramfs if present.

However, we currently delete modules.* when creating the image packages,
because we assume all those files are generated by depmod.  Oops.

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
                                                              - Albert Camus

  reply	other threads:[~2010-10-06 18:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100929165034.21331.69639.reportbug@albatros.savanenet>
2010-09-29 22:27 ` Bug#598518: linux-image-2.6-686: ata_piix module loaded before ahci module deactivate hotplug support (regression from lenny) Ben Hutchings
2010-10-04 16:46   ` Tejun Heo
2010-10-04 17:54     ` maximilian attems
2010-10-05  7:45       ` Thomas DEBESSE
2010-10-05  9:05         ` maximilian attems
2010-10-06 17:04           ` Thomas DEBESSE
2010-10-06 18:33             ` Ben Hutchings [this message]
2010-10-20 12:58               ` Thomas DEBESSE
2010-11-15 13:43                 ` Thomas DEBESSE

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=20101006183321.GU13095@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=598518@bugs.debian.org \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=max@stro.at \
    --cc=thomas.debesse+debian@gmail.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