From: Kevin Hilman <khilman@baylibre.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] binman: Put our local modules ahead of system modules
Date: Fri, 23 Jun 2017 11:55:58 -0700 [thread overview]
Message-ID: <7hzicy8rep.fsf@baylibre.com> (raw)
In-Reply-To: <20170621032849.41383-1-sjg@chromium.org> (Simon Glass's message of "Tue, 20 Jun 2017 21:28:49 -0600")
Simon Glass <sjg@chromium.org> writes:
> If a system module is named the same as one of those used by binman we
> currently pick the system module. Adjust the ordering so that our modules
> are chosen instead.
>
> The module conflict reported was 'tools' from jira-python. I cannot access
> that package to test it.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> Reported-by: Kevin Hilman <khilman@baylibre.com>
While I removed the pip package that was causing me problems, this looks
basically like the workaround I had done locally.
Acked-by: Kevin Hilman <khilman@baylibre.com>
Thanks for fixing it up,
Kevin
next prev parent reply other threads:[~2017-06-23 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 3:28 [U-Boot] [PATCH] binman: Put our local modules ahead of system modules Simon Glass
2017-06-23 18:55 ` Kevin Hilman [this message]
2017-07-06 14:48 ` sjg at google.com
2017-07-06 14:51 ` sjg at google.com
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=7hzicy8rep.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=u-boot@lists.denx.de \
/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