From: Richard Cochran <richardcochran@gmail.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: 王擎 <wangqing@vivo.com>, "Jakub Kicinski" <kuba@kernel.org>,
"Grygorii Strashko" <grygorii.strashko@ti.com>,
"David S. Miller" <davem@davemloft.net>,
"Samuel Zou" <zou_wei@huawei.com>,
"Kurt Kanzenbach" <kurt@linutronix.de>,
"Ivan Khoronzhuk" <ivan.khoronzhuk@linaro.org>,
Networking <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Re: [PATCH V4 net-bugfixs] net/ethernet: Update ret when ptp_clock is ERROR
Date: Sat, 14 Nov 2020 07:14:10 -0800 [thread overview]
Message-ID: <20201114151410.GA24250@hoboy.vegasvil.org> (raw)
In-Reply-To: <CAK8P3a3V98x3s7DvHtutiz97Q=5QjfS6Xn4kH2r2iamY3dzwkw@mail.gmail.com>
On Fri, Nov 13, 2020 at 05:21:43PM +0100, Arnd Bergmann wrote:
> I've prototyped a patch that I think makes this more sensible
> again: https://pastebin.com/AQ5nWS9e
I like the behavior described in the text.
Instead of this ...
- if a built-in driver calls PTP interface functions but fails
to select HAVE_PTP_1588_CLOCK or depend on PTP_1588_CLOCK,
and PTP support is a loadable module, we get a link error
instead of having an unusable clock.
how about simply deleting the #else clause of
--- a/include/linux/ptp_clock_kernel.h
+++ b/include/linux/ptp_clock_kernel.h
@@ -173,7 +173,7 @@ struct ptp_clock_event {
};
};
-#if IS_REACHABLE(CONFIG_PTP_1588_CLOCK)
+#if IS_ENABLED(CONFIG_PTP_1588_CLOCK)
so that invalid configurations throw a compile time error instead?
Thanks,
Richard
next prev parent reply other threads:[~2020-11-14 15:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 9:24 Wang Qing
2020-11-11 12:32 ` Richard Cochran
2020-11-11 13:24 ` Grygorii Strashko
2020-11-11 13:55 ` Richard Cochran
2020-11-11 16:00 ` Jakub Kicinski
2020-11-12 1:15 ` 王擎
2020-11-12 1:32 ` Jakub Kicinski
2020-11-12 2:48 ` 王擎
2020-11-12 4:23 ` Jakub Kicinski
2020-11-12 8:25 ` Arnd Bergmann
2020-11-12 10:05 ` Grygorii Strashko
2020-11-12 18:14 ` Richard Cochran
2020-11-12 18:19 ` Richard Cochran
2020-11-12 21:21 ` Arnd Bergmann
2020-11-12 23:27 ` Richard Cochran
2020-11-13 16:21 ` Arnd Bergmann
2020-11-14 15:14 ` Richard Cochran [this message]
2020-11-14 21:16 ` Arnd Bergmann
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=20201114151410.GA24250@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=arnd@kernel.org \
--cc=davem@davemloft.net \
--cc=grygorii.strashko@ti.com \
--cc=ivan.khoronzhuk@linaro.org \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wangqing@vivo.com \
--cc=zou_wei@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®