All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dennis Schridde <devurandom-hi6Y0CQ0nG0@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Fwd: Re: [PATCH] Use modinfo to gather module dependencies
Date: Mon, 27 Feb 2012 12:33:29 +0100	[thread overview]
Message-ID: <3303131.vLqtaXUY2V@samson> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 0 bytes --]



[-- Attachment #1.2: Dennis Schridde <devurandom-hi6Y0CQ0nG0@public.gmane.org>: Re: [PATCH] Use modinfo to gather module dependencies --]
[-- Type: message/rfc822, Size: 1912 bytes --]

[-- Attachment #1.2.1.1: Type: text/plain, Size: 657 bytes --]

Hi Harald!

Am Samstag, 25. Februar 2012, 22:18:48 schrieben Sie:
> Am 25.02.2012 22:09 schrieb "Dennis Schridde" <devurandom-hi6Y0CQ0nG0@public.gmane.org>:
> > 
> > Hence I wrote attached patch, switching from modprobe to modinfo, which
> 
> also
> 
> > seem to be the tool intended for the job. This method appears to work
> 
> reliable
> 
> > in kmod-5, but I have not tested with module-init-tools.
> 
> Just update kmod... modprobe --show-depends was fixed
Thanks for the info.

I would like know your reasons for using modprobe instead of modinfo to gather 
information about modules, since it appears to be the wrong tool to me.

Kind regards,
Dennis

[-- Attachment #1.2.1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

                 reply	other threads:[~2012-02-27 11:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3303131.vLqtaXUY2V@samson \
    --to=devurandom-hi6y0cq0ng0@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.