All of lore.kernel.org
 help / color / mirror / Atom feed
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 v4 0/2] memory: omap-gpmc: Allow module build
Date: Tue, 26 Apr 2022 11:26:09 +0300	[thread overview]
Message-ID: <20220426082611.24427-1-rogerq@kernel.org> (raw)

Hi,

These patches allow OMAP_GPMC config to be visible in menuconfig
and buildable as a module.

cheers,
-roger

Changelog:
v4:
- drop COMPILE_TEST as include/linux/irqdomain.h does not have
fallbacks if CONFIG_IRQ_DOMAIN is not available. So build will
fail with COMPILE_TEST on platforms not having CONFIG_IRQ_DOMAIN.
- use GPL instead of GPL v2 for MODULE_LICENSE. Fixes checkpatch
warning.

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     |  2 +-
 drivers/memory/omap-gpmc.c | 43 ++++++++++++++++++++------------------
 2 files changed, 24 insertions(+), 21 deletions(-)

-- 
2.17.1


             reply	other threads:[~2022-04-26  8:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26  8:26 Roger Quadros [this message]
2022-04-26  8:26 ` [PATCH v4 1/2] memory: omap-gpmc: Make OMAP_GPMC config visible and selectable Roger Quadros
2022-04-26  8:26 ` [PATCH v4 2/2] memory: omap-gpmc: Allow building as a module Roger Quadros
2022-04-29  6:59   ` Krzysztof Kozlowski
2022-04-26  8:40 ` [PATCH v4 0/2] memory: omap-gpmc: Allow module build Roger Quadros
2022-04-29  6:58 ` 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=20220426082611.24427-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.