All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Lucas De Marchi <lucas.de.marchi@gmail.com>
Cc: "Matwey V. Kornilov" <matwey.kornilov@gmail.com>,
	Gustavo Sverzut Barbieri <barbieri@gmail.com>,
	linux-modules <linux-modules@vger.kernel.org>
Subject: Re: [PATCH] Fix recursion loop in mod_count_all_dependencies()
Date: Mon, 05 May 2014 19:41:33 +0930	[thread overview]
Message-ID: <87ppjsbkmi.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CAKi4VAL4+nErBqO+z-LJCYxuMqEHmsv0272ju6xQQ2W9ra3+wg@mail.gmail.com>

Lucas De Marchi <lucas.de.marchi@gmail.com> writes:
> On Sun, May 4, 2014 at 10:45 PM, Rusty Russell <rusty@rustcorp.com.au> wrote:
>> Note that in the case where two modules could satisfy a dependencies,
>> it may not be a real loop?
>
> What do you mean here? How could that be the case for *depmod*?

Sorry, it's a theoretical case; no one does anything this crazy:

 A provides symbol S1.
 B provides symbol S1, needs S2.
 C needs S1, provides S2.
 D provides S2.

Cheers,
Rusty.

  reply	other threads:[~2014-05-05 10:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-11 19:31 [PATCH] Fix recursion loop in mod_count_all_dependencies() matwey.kornilov
2014-04-25  3:46 ` Lucas De Marchi
2014-04-27 15:30   ` Gustavo Sverzut Barbieri
2014-04-27 19:44     ` Matwey V. Kornilov
2014-05-02 14:13       ` Lucas De Marchi
2014-05-02 14:29         ` Matwey V. Kornilov
2014-05-05  1:45         ` Rusty Russell
2014-05-05  4:29           ` Lucas De Marchi
2014-05-05 10:11             ` Rusty Russell [this message]
2014-05-05 10:16               ` Matwey V. Kornilov
2014-05-05 12:44                 ` Lucas De Marchi
2014-05-05 12:37               ` Lucas De Marchi
     [not found]     ` <CAKi4VA+R6TBbgVv1yAjKi0cU=Q+X8zFDQQ0e3hNiQ5meDhsiEg@mail.gmail.com>
2014-04-27 20:04       ` Lucas De Marchi

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=87ppjsbkmi.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=barbieri@gmail.com \
    --cc=linux-modules@vger.kernel.org \
    --cc=lucas.de.marchi@gmail.com \
    --cc=matwey.kornilov@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 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.