All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Shuah Khan <skhan@linuxfoundation.org>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: Christoph Hellwig <hch@lst.de>, Joel Becker <jlbec@evilplan.org>,
	linux-kernel@vger.kernel.org,
	Brendan Higgins <brendanhiggins@google.com>,
	David Gow <davidgow@google.com>,
	kunit-dev@googlegroups.com, linux-kselftest@vger.kernel.org,
	Bodo Stroesser <bostroesser@gmail.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	Yanko Kaneti <yaneti@declera.com>
Subject: Re: [PATCH v2 2/3] kunit: Add support for suite initialization and cleanup
Date: Thu, 29 Jul 2021 12:22:06 -0700	[thread overview]
Message-ID: <5f356522-e61b-9605-5f82-e805efcaef3d@acm.org> (raw)
In-Reply-To: <81edb935-aabd-bd05-c3d1-260903b3c726@linuxfoundation.org>

On 7/29/21 11:42 AM, Shuah Khan wrote:
> Please take a look at Documentation/process/submitting-patches.rst
> for information on commit logs.

As one can see below, I'm already familiar with the kernel development 
process:

$ git log --author="Bart Van Assche" | grep -c ^commit
1664

Bart.

  reply	other threads:[~2021-07-29 19:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29  4:41 [PATCH v2 0/3] Restore the kernel v5.13 text attribute write behavior Bart Van Assche
2021-07-29  4:41 ` [PATCH v2 1/3] configfs: " Bart Van Assche
2021-07-29  4:41 ` [PATCH v2 2/3] kunit: Add support for suite initialization and cleanup Bart Van Assche
2021-07-29  5:55   ` Greg KH
2021-07-29 16:52     ` Bart Van Assche
2021-07-29 16:55       ` Shuah Khan
2021-07-29 17:16         ` Bart Van Assche
2021-07-29 18:42           ` Shuah Khan
2021-07-29 19:22             ` Bart Van Assche [this message]
2021-07-29 20:42               ` Shuah Khan
2021-07-29  4:41 ` [PATCH v2 3/3] configfs: Add unit tests Bart Van Assche

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=5f356522-e61b-9605-5f82-e805efcaef3d@acm.org \
    --to=bvanassche@acm.org \
    --cc=bostroesser@gmail.com \
    --cc=brendanhiggins@google.com \
    --cc=davidgow@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=jlbec@evilplan.org \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=skhan@linuxfoundation.org \
    --cc=yaneti@declera.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.