From: Randy Dunlap <rdunlap@infradead.org>
To: netdev@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Richard Cochran <richardcochran@gmail.com>,
Jonathan Lemon <jonathan.lemon@gmail.com>
Subject: [PATCH] ptp: ocp: don't allow on S390
Date: Fri, 13 Aug 2021 13:30:26 -0700 [thread overview]
Message-ID: <20210813203026.27687-1-rdunlap@infradead.org> (raw)
Fix kconfig warning on arch/s390/:
WARNING: unmet direct dependencies detected for SERIAL_8250
Depends on [n]: TTY [=y] && HAS_IOMEM [=y] && !S390 [=y]
Selected by [m]:
- PTP_1588_CLOCK_OCP [=m] && PTP_1588_CLOCK [=m] && HAS_IOMEM [=y] && PCI [=y] && SPI [=y] && I2C [=m] && MTD [=m]
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Richard Cochran <richardcochran@gmail.com>
Cc: Jonathan Lemon <jonathan.lemon@gmail.com>
---
There is no 8250 serial on S390. See commit 1598e38c0770.
Is this driver useful even without 8250 serial?
drivers/ptp/Kconfig | 1 +
1 file changed, 1 insertion(+)
--- linux-next-20210813.orig/drivers/ptp/Kconfig
+++ linux-next-20210813/drivers/ptp/Kconfig
@@ -158,6 +158,7 @@ config PTP_1588_CLOCK_OCP
depends on PTP_1588_CLOCK
depends on HAS_IOMEM && PCI
depends on SPI && I2C && MTD
+ depends on !S390
imply SPI_MEM
imply SPI_XILINX
imply MTD_SPI_NOR
next reply other threads:[~2021-08-13 20:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 20:30 Randy Dunlap [this message]
2021-08-16 10:20 ` [PATCH] ptp: ocp: don't allow on S390 patchwork-bot+netdevbpf
2021-08-16 21:09 ` Jonathan Lemon
2021-08-16 21:15 ` Randy Dunlap
2021-08-16 21:41 ` Jonathan Lemon
2021-08-19 22:58 ` Randy Dunlap
2021-08-20 8:02 ` Christian Borntraeger
2021-08-20 9:59 ` Niklas Schnelle
2021-08-20 10:45 ` Arnd Bergmann
2021-08-20 15:31 ` Richard Cochran
2021-08-24 21:48 ` Randy Dunlap
2021-08-25 10:55 ` Arnd Bergmann
2021-08-25 17:08 ` Jonathan Lemon
2021-08-25 17:29 ` Randy Dunlap
2021-08-25 18:05 ` Arnd Bergmann
2021-08-25 20:40 ` Jonathan Lemon
2021-08-25 20:45 ` Randy Dunlap
2021-08-25 21:14 ` Jonathan Lemon
2021-08-25 23:22 ` Randy Dunlap
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=20210813203026.27687-1-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=jonathan.lemon@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.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;
as well as URLs for NNTP newsgroup(s).