From: Richard Cochran <richardcochran@gmail.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Josh Triplett <josh@joshtriplett.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] make POSIX timers optional
Date: Tue, 20 Sep 2016 22:25:56 +0200 [thread overview]
Message-ID: <20160920202556.GA6713@localhost.localdomain> (raw)
In-Reply-To: <1474401400-18491-1-git-send-email-nicolas.pitre@linaro.org>
On Tue, Sep 20, 2016 at 03:56:38PM -0400, Nicolas Pitre wrote:
> - Add a warning for the case where PTP clock subsystem is modular and a
> driver providing a clock is built-in rather than silently ignoring it.
> Suggested by Jiri Benc.
So I am really not happy with this. Here is a common embedded
workflow, at least for me:
1. take some given Kconfig and get it running on the target.
2. for the given HW, change the modules into built-ins, and forget
module loading
After this series, if I don't pay enough attention to dmesg, then I
have lost functionality that I had in step #1. That sucks, and it has
nothing to do with the tinification option at all. It will bite even
if I have no knowledge of it. That isn't acceptable to me.
Thanks,
Richard
next prev parent reply other threads:[~2016-09-20 20:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 19:56 [PATCH v2 0/2] make POSIX timers optional Nicolas Pitre
2016-09-20 19:56 ` [PATCH 1/2] ptp_clock: allow for it to be optional Nicolas Pitre
2016-09-20 19:56 ` [PATCH 2/2] posix-timers: make it configurable Nicolas Pitre
2016-09-20 20:25 ` Richard Cochran [this message]
2016-09-20 20:45 ` [PATCH v2 0/2] make POSIX timers optional Richard Cochran
2016-09-20 20:58 ` Nicolas Pitre
2016-09-20 21:09 ` Thomas Gleixner
2016-09-20 22:47 ` Nicolas Pitre
2016-09-21 8:38 ` Richard Cochran
2016-09-21 10:27 ` Jiri Benc
2016-09-21 9:09 ` Thomas Gleixner
2016-09-21 10:20 ` Jiri Benc
2016-09-20 20:52 ` Nicolas Pitre
2016-09-22 6:09 ` David Miller
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=20160920202556.GA6713@localhost.localdomain \
--to=richardcochran@gmail.com \
--cc=john.stultz@linaro.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).