[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210919093114.35987-1-krzysztof.kozlowski@canonical.com>
Date: Sun, 19 Sep 2021 11:31:11 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To: Russell King <linux@...linux.org.uk>,
Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: Marek Szyprowski <m.szyprowski@...sung.com>,
Sylwester Nawrocki <snawrocki@...nel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
Tomasz Figa <tomasz.figa@...il.com>,
Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
Alim Akhtar <alim.akhtar@...sung.com>,
Chanwoo Choi <cw00.choi@...sung.com>,
Pankaj Dubey <pankaj.dubey@...sung.com>
Subject: [PATCH v2 0/3] soc: samsung: exynos-chipid: be a module!
Hi,
Changes since v1
================
1. Drop patch 1/2 - exporting soc_device_to_device
2. Add new patches: 1/3 and 3/3.
Question
========
A question - what is the convention for naming modules: underscores '_' or
hyphens '-'?
The C-unit file already uses a hyphen "exynos-chipid.c", so I could
create a module named:
1. exynos_chipid
2. soc-exynos-chipid
3. exynos-chip-id
The Linux device name is "exynos-chipid".
Best regards,
Krzysztof
Krzysztof Kozlowski (3):
soc: samsung: exynos-chipid: avoid soc_device_to_device()
soc: samsung: exynos-chipid: convert to a module
soc: samsung: exynos-chipid: do not enforce built-in
arch/arm/mach-exynos/Kconfig | 1 -
drivers/soc/samsung/Kconfig | 4 +++-
drivers/soc/samsung/Makefile | 3 ++-
drivers/soc/samsung/exynos-chipid.c | 14 +++++++++++---
drivers/soc/samsung/exynos5422-asv.c | 1 +
5 files changed, 17 insertions(+), 6 deletions(-)
--
2.30.2
Powered by blists - more mailing lists