Linux IIO development
 help / color / mirror / Atom feed
From: Liam Beguin <liambeguin@gmail.com>
To: liambeguin@gmail.com, jic23@kernel.org, geert@linux-m68k.org
Cc: peda@axentia.se, linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 2/5] iio: test: format: add MODULE_* information
Date: Sat,  9 Jul 2022 21:31:06 -0400	[thread overview]
Message-ID: <20220710013109.3349104-3-liambeguin@gmail.com> (raw)
In-Reply-To: <20220710013109.3349104-1-liambeguin@gmail.com>

In preparation for module support, add missing MODULE_* information.

Signed-off-by: Liam Beguin <liambeguin@gmail.com>
---
 drivers/iio/test/iio-test-format.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/drivers/iio/test/iio-test-format.c b/drivers/iio/test/iio-test-format.c
index 237321436b83..fc67e6b73df7 100644
--- a/drivers/iio/test/iio-test-format.c
+++ b/drivers/iio/test/iio-test-format.c
@@ -265,3 +265,7 @@ static struct kunit_suite iio_format_test_suite = {
 	.test_cases = iio_format_test_cases,
 };
 kunit_test_suite(iio_format_test_suite);
+
+MODULE_AUTHOR("Lars-Peter Clausen <lars@metafoo.de>");
+MODULE_DESCRIPTION("Test IIO formatting functions");
+MODULE_LICENSE("GPL v2");
-- 
2.35.1.4.g5d01301f2b86


  parent reply	other threads:[~2022-07-10  1:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-10  1:31 [PATCH v1 0/5] Add module build support for KUnit IIO tests Liam Beguin
2022-07-10  1:31 ` [PATCH v1 1/5] iio: test: rescale: add MODULE_* information Liam Beguin
2022-07-10  1:31 ` Liam Beguin [this message]
2022-07-10  1:31 ` [PATCH v1 3/5] iio: test: format: follow CONFIG_ naming convention Liam Beguin
2022-07-10  1:31 ` [PATCH v1 4/5] iio: afe: rescale: export symbols used during testing Liam Beguin
2022-07-10  1:31 ` [PATCH v1 5/5] iio: test: rework Kconfig to support modules Liam Beguin
2022-07-16 18:03   ` Jonathan Cameron

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=20220710013109.3349104-3-liambeguin@gmail.com \
    --to=liambeguin@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peda@axentia.se \
    /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