From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Joe Lawrence <Joe.Lawrence-7+ureL1bLXNBDgjK7y7TUQ@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Out of tree drivers missing from initramfs
Date: Fri, 25 Jan 2013 13:08:52 +0100 [thread overview]
Message-ID: <510275D4.7080401@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1301241718240.31163-ceYW5R1vr2hcrvxNGtJwk767FWEIOpWeVpNB7YpNyf8@public.gmane.org>
Am 24.01.2013 23:26, schrieb Joe Lawrence:
> On Wed, 23 Jan 2013, Harald Hoyer wrote:
>
>> Am 22.01.2013 23:04, schrieb Joe Lawrence:
>>
>>> 2 - Do modules underneath /lib/modules/ver/{updates,extras} need to
>>> include their respective directory structure (ie, 'drivers/scsi').
>>
>> yes
>
> Is this a dracut requirement, general convention, etc? I tried to search
> google for a definitive document on updates/extra modules and couldn't
> find much aside from Documentation/kbuild/modules.txt in the kernel tree.
>
> This change is easy enough to make, but I'd like to get it right. :)
>
>> Thanks for reporting this, will fix this bug!
>
> See below for one possible solution. It may be more correct to filter on
> kernel* and updates* and extra*, but as proof of concept, it
> successfully built a initramfs with a driver located at:
>
> /updates/lsb-ft/drivers/scsi/mpt2sas/mpt2sas.ko
>
> Regards,
>
> -- Joe
perfekt. patch merged
prev parent reply other threads:[~2013-01-25 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 22:04 Out of tree drivers missing from initramfs Joe Lawrence
[not found] ` <alpine.DEB.2.02.1301221612280.31163-ceYW5R1vr2hcrvxNGtJwk767FWEIOpWeVpNB7YpNyf8@public.gmane.org>
2013-01-23 14:58 ` Joe Lawrence
2013-01-23 15:19 ` Harald Hoyer
[not found] ` <50FFFF93.2080209-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-01-24 22:26 ` Joe Lawrence
[not found] ` <alpine.DEB.2.02.1301241718240.31163-ceYW5R1vr2hcrvxNGtJwk767FWEIOpWeVpNB7YpNyf8@public.gmane.org>
2013-01-25 12:08 ` Harald Hoyer [this message]
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=510275D4.7080401@redhat.com \
--to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=Joe.Lawrence-7+ureL1bLXNBDgjK7y7TUQ@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.