From: Roger Quadros <rogerq@kernel.org>
To: krzk@kernel.org
Cc: miquel.raynal@bootlin.com, tony@atomide.com, vigneshr@ti.com,
kishon@ti.com, nm@ti.com, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org, Roger Quadros <rogerq@kernel.org>
Subject: [PATCH v3 0/2] memory: omap-gpmc: Allow module build
Date: Mon, 11 Apr 2022 12:55:14 +0300 [thread overview]
Message-ID: <20220411095516.24754-1-rogerq@kernel.org> (raw)
Hi,
These patches allow OMAP_GPMC config to be visible in menuconfig
and buildable as a module.
Changelog:
v3:
- Remove not required MODULE_ALIAS
- Mention in commit message why we need to remove of_match_node() call
v2:
- Allow building as a module
Roger Quadros (2):
memory: omap-gpmc: Make OMAP_GPMC config visible and selectable
memory: omap-gpmc: Allow building as a module
drivers/memory/Kconfig | 4 ++--
drivers/memory/omap-gpmc.c | 43 ++++++++++++++++++++------------------
2 files changed, 25 insertions(+), 22 deletions(-)
--
2.17.1
next reply other threads:[~2022-04-11 9:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 9:55 Roger Quadros [this message]
2022-04-11 9:55 ` [PATCH v3 1/2] memory: omap-gpmc: Make OMAP_GPMC config visible and selectable Roger Quadros
2022-04-11 10:06 ` Miquel Raynal
2022-04-11 9:55 ` [PATCH v3 2/2] memory: omap-gpmc: Allow building as a module Roger Quadros
2022-04-13 9:43 ` [PATCH v3 0/2] memory: omap-gpmc: Allow module build Krzysztof Kozlowski
2022-04-13 9:50 ` Krzysztof Kozlowski
2022-04-13 10:20 ` Krzysztof Kozlowski
2022-04-13 10:42 ` Roger Quadros
2022-04-13 11:01 ` Roger Quadros
2022-04-13 11:05 ` Krzysztof Kozlowski
2022-04-13 11:33 ` Roger Quadros
2022-04-13 11:47 ` Krzysztof Kozlowski
2022-04-13 11:56 ` Roger Quadros
2022-04-13 12:31 ` Krzysztof Kozlowski
2022-04-13 12:56 ` Roger Quadros
2022-04-13 13:00 ` Krzysztof Kozlowski
2022-04-13 13:04 ` Krzysztof Kozlowski
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=20220411095516.24754-1-rogerq@kernel.org \
--to=rogerq@kernel.org \
--cc=kishon@ti.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=nm@ti.com \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.