linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Brendan Higgins <brendan.higgins@linux.dev>,
	David Gow <davidgow@google.com>, Jonathan Corbet <corbet@lwn.net>,
	Khalid Masum <khalid.masum.92@gmail.com>,
	Sadiya Kazi <sadiyakazi@google.com>
Subject: Re: [PATCH] Documentation: kunit: rewrite writing first test instructions
Date: Thu, 29 Sep 2022 20:00:40 +0700	[thread overview]
Message-ID: <a0545ea0-2ce5-68d1-4cbd-bfaa3ff453b5@gmail.com> (raw)
In-Reply-To: <20220929125458.52979-1-bagasdotme@gmail.com>

On 9/29/22 19:54, Bagas Sanjaya wrote:
>  Writing Your First Test
>  =======================
> -In your kernel repository, let's add some code that we can test.
> +In your kernel repository, let's add some code that we can test. For this
> +purpose, we are going to add simple addition driver.
>  
> -1. Create a file ``drivers/misc/example.h``, which includes:
> +1. Write the feature that will be tested. First, write the declaration
> +   for ``misc_example_add()`` in ``drivers/misc/example.h``:
>  
> -.. code-block:: c
> +   .. code-block:: c
>  
>  	int misc_example_add(int left, int right);
>  
> -2. Create a file ``drivers/misc/example.c``, which includes:
> +   Then implement the function in ``drivers/misc/example.c``:
>  
> -.. code-block:: c
> +   .. code-block:: c
>  
>  	#include <linux/errno.h>
>  
> @@ -152,24 +154,25 @@ In your kernel repository, let's add some code that we can test.
>  		return left + right;
>  	}
>  
> -3. Add the following lines to ``drivers/misc/Kconfig``:
> +3. Add Kconfig menu entry for the feature to ``drivers/misc/Kconfig``:
>  

The numbering looks jumped. Please ignore this patch as I'll resend shortly.

-- 
An old man doll... just what I always wanted! - Clara

      reply	other threads:[~2022-09-29 13:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29 12:54 [PATCH] Documentation: kunit: rewrite writing first test instructions Bagas Sanjaya
2022-09-29 13:00 ` Bagas Sanjaya [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=a0545ea0-2ce5-68d1-4cbd-bfaa3ff453b5@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=brendan.higgins@linux.dev \
    --cc=corbet@lwn.net \
    --cc=davidgow@google.com \
    --cc=khalid.masum.92@gmail.com \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=sadiyakazi@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).