Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Wander Lairson Costa <wander@redhat.com>,
	kunit-dev@googlegroups.com, linux-kselftest@vger.kernel.org,
	kernel-janitors@vger.kernel.org,
	Brendan Higgins <brendan.higgins@linux.dev>,
	David Gow <davidgow@google.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Matti Vaittinen <mazziesaccount@gmail.com>,
	Maxime Ripard <mripard@kernel.org>, Rae Moar <rmoar@google.com>,
	Shuah Khan <skhan@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/2] kunit: fix minor error path mistakes
Date: Fri, 19 Apr 2024 18:18:22 +0200	[thread overview]
Message-ID: <4dd9babe-1e4d-46d9-b3dc-cc8978e74e5f@web.de> (raw)
In-Reply-To: <20240419132504.9488-1-wander@redhat.com>

…
> * Remove some changes requested by Marcus Elfring,

I became curious how affected software components can evolve further.


>   as I was alerted he is a known troll.

I would appreciate if this interpretation will be reconsidered somehow.

Regards,
Markus

      parent reply	other threads:[~2024-04-19 16:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19 13:25 [PATCH v4 0/2] kunit: fix minor error path mistakes Wander Lairson Costa
2024-04-19 13:25 ` [PATCH v4 1/2] kunit: unregister the device on error Wander Lairson Costa
2024-04-19 14:04   ` Greg Kroah-Hartman
2024-04-19 16:32     ` Markus Elfring
2024-04-20  6:27       ` Greg Kroah-Hartman
2024-04-19 13:25 ` [PATCH v4 2/2] kunit: avoid memory leak on device register error Wander Lairson Costa
2024-04-19 14:03   ` Greg Kroah-Hartman
2024-04-19 14:11     ` Wander Lairson Costa
2024-04-23  8:00       ` David Gow
2024-04-19 16:18 ` Markus Elfring [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=4dd9babe-1e4d-46d9-b3dc-cc8978e74e5f@web.de \
    --to=markus.elfring@web.de \
    --cc=brendan.higgins@linux.dev \
    --cc=davidgow@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mazziesaccount@gmail.com \
    --cc=mripard@kernel.org \
    --cc=rmoar@google.com \
    --cc=skhan@linuxfoundation.org \
    --cc=wander@redhat.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