mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH 0/6] gpio: extend build coverage with COMPILE_TEST=y
Date: Wed, 16 Apr 2025 17:56:25 +0200	[thread overview]
Message-ID: <174481898217.8191.5994115925573733265.b4-ty@bgdev.pl> (raw)
In-Reply-To: <20250408-gpio-compile-test-v1-0-140e108e9392@linaro.org>


On Tue, 08 Apr 2025 14:59:00 +0200, Bartosz Golaszewski wrote:
> There are some drivers that aren't build with allmodconfig that don't
> have any requirements on arch/ headers so make them depend on
> COMPILE_TEST and extend the build coverage.
> 
> 

Applied, thanks!

[1/6] gpio: zynq: enable building the modules with COMPILE_TEST=y
      https://git.kernel.org/brgl/linux/c/27cdde96fd1eb38cd0675c6ad4be769f852b3528
[2/6] gpio: msc313: enable building the module with COMPILE_TEST=y
      https://git.kernel.org/brgl/linux/c/ce4f4ce18e162c15d7288e78383e9a5000cd0b61
[3/6] gpio: pl061: enable building the module with COMPILE_TEST=y
      https://git.kernel.org/brgl/linux/c/e40952bb8c6c54efbb1ae1dc8dc8ab71e17587ca
[4/6] gpio: rtd: enable building the module with COMPILE_TEST=y
      https://git.kernel.org/brgl/linux/c/27747874cd90a5b61fd50f1df7f7af017b42f479
[5/6] gpio: tb10x: enable building the module with COMPILE_TEST=y
      https://git.kernel.org/brgl/linux/c/90d80a3dc4fb24446d9d423c1c8967a63f136b0b
[6/6] gpio: tn48m: enable building the module with COMPILE_TEST=y
      https://git.kernel.org/brgl/linux/c/a5d8e0cc96eed600a347bbdcd125a9274a92e187

Best regards,
-- 
Bartosz Golaszewski <brgl@bgdev.pl>

      parent reply	other threads:[~2025-04-16 15:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 12:59 Bartosz Golaszewski
2025-04-08 12:59 ` [PATCH 1/6] gpio: zynq: enable building the modules " Bartosz Golaszewski
2025-04-08 12:59 ` [PATCH 2/6] gpio: msc313: enable building the module " Bartosz Golaszewski
2025-04-08 12:59 ` [PATCH 3/6] gpio: pl061: " Bartosz Golaszewski
2025-04-08 12:59 ` [PATCH 4/6] gpio: rtd: " Bartosz Golaszewski
2025-04-08 12:59 ` [PATCH 5/6] gpio: tb10x: " Bartosz Golaszewski
2025-04-08 12:59 ` [PATCH 6/6] gpio: tn48m: " Bartosz Golaszewski
2025-04-15 21:40 ` [PATCH 0/6] gpio: extend build coverage " Linus Walleij
2025-04-16 15:56 ` Bartosz Golaszewski [this message]

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=174481898217.8191.5994115925573733265.b4-ty@bgdev.pl \
    --to=brgl@bgdev.pl \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®