From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] ci/debian: Temporarily not require libmm-dev
Date: Fri, 25 Feb 2022 12:14:14 +0100 [thread overview]
Message-ID: <Yhi6BqmKc1zGMUHj@yuki> (raw)
In-Reply-To: <20220225110152.26098-1-pvorel@suse.cz>
Hi!
> do we even need libmm-dev?
>
> https://packages.debian.org/sid/amd64/libmm-dev/filelist
> ...
> /usr/bin/mm-config
> /usr/include/mm.h
> /usr/lib/libmm.a
> /usr/lib/libmm.so
I do not think so. The only places where I found that we include mm.h
are actually a kernel modules and that include should be satisfied from
kernel-devel package.
So I guess that this has been added as a mistake to begin with.
Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-02-25 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 11:01 [LTP] [PATCH 1/1] ci/debian: Temporarily not require libmm-dev Petr Vorel
2022-02-25 11:14 ` Cyril Hrubis [this message]
2022-02-25 11:18 ` Petr Vorel
2022-02-25 11:22 ` Petr Vorel
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=Yhi6BqmKc1zGMUHj@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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