From: Josh Triplett <josh@joshtriplett.org>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: John Stultz <john.stultz@linaro.org>,
Richard Cochran <richardcochran@gmail.com>,
Yann E MORIN <yann.morin.1998@free.fr>,
Thomas Gleixner <tglx@linutronix.de>,
netdev@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] make POSIX timers optional with some Kconfig help
Date: Thu, 20 Oct 2016 11:51:22 -0700 [thread overview]
Message-ID: <20161020185122.ymwvqiqslf32eife@x> (raw)
In-Reply-To: <1476920573-14384-1-git-send-email-nicolas.pitre@linaro.org>
On Wed, Oct 19, 2016 at 07:42:49PM -0400, Nicolas Pitre wrote:
> Many embedded systems don't need the full POSIX timer support.
> Configuring them out provides a nice kernel image size reduction.
>
> When POSIX timers are configured out, the PTP clock subsystem should be
> left out as well. However a bunch of ethernet drivers currently *select*
> the later in their Kconfig entries. Therefore some more work was needed
> to break that hard dependency from those drivers without preventing their
> usage altogether.
>
> Therefore this series also includes kconfig changes to implement a new
> keyword to express some reverse dependencies like "select" does, named
> "imply", and still allowing for the target config symbol to be disabled
> if the user or a direct dependency says so.
>
> How to deal with the dependencies across three subsystems for potential
> upstream merging needs to be figured out.
This looks good to me, and I like the new "imply" approach.
I'd still like to see a more general solution for reporting the use of
compiled-out syscalls, but I don't think that needs to block this patch
series.
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
prev parent reply other threads:[~2016-10-20 18:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 23:42 [PATCH 0/4] make POSIX timers optional with some Kconfig help Nicolas Pitre
2016-10-19 23:42 ` [PATCH 1/4] kconfig: introduce the "imply" keyword Nicolas Pitre
2016-10-20 6:53 ` Masahiro Yamada
2016-10-20 14:52 ` Edward Cree
2016-10-20 15:38 ` Josh Triplett
2016-10-20 17:04 ` Nicolas Pitre
2016-10-20 17:41 ` Edward Cree
2016-10-20 18:29 ` Nicolas Pitre
2016-10-20 19:09 ` Edward Cree
2016-10-20 20:10 ` Nicolas Pitre
2016-10-21 3:24 ` Nicolas Pitre
2016-10-19 23:42 ` [PATCH 2/4] kconfig: re-generate *.c_shipped files after previous change Nicolas Pitre
2016-10-19 23:42 ` [PATCH 3/4] ptp_clock: allow for it to be optional Nicolas Pitre
2016-10-20 9:50 ` Thomas Gleixner
2016-10-20 17:47 ` Nicolas Pitre
2016-10-20 17:58 ` Thomas Gleixner
2016-10-20 14:06 ` Richard Cochran
2016-10-20 15:38 ` Josh Triplett
2016-10-20 16:44 ` Nicolas Pitre
2016-10-19 23:42 ` [PATCH 4/4] posix-timers: make it configurable Nicolas Pitre
2016-10-20 14:02 ` Richard Cochran
2016-10-20 16:41 ` Nicolas Pitre
2016-10-20 9:46 ` [PATCH 0/4] make POSIX timers optional with some Kconfig help Thomas Gleixner
2016-10-20 18:35 ` Nicolas Pitre
2016-10-20 18:51 ` Josh Triplett [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=20161020185122.ymwvqiqslf32eife@x \
--to=josh@joshtriplett.org \
--cc=john.stultz@linaro.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=richardcochran@gmail.com \
--cc=tglx@linutronix.de \
--cc=yann.morin.1998@free.fr \
/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;
as well as URLs for NNTP newsgroup(s).