All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Michal Sekletar <msekleta@redhat.com>
Cc: jirislaby@kernel.org, arozansk@redhat.com,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	shuah@kernel.org
Subject: Re: [PATCH v2 2/2] selftests: tty: add selftest for tty timestamp updates
Date: Thu, 8 Jun 2023 13:49:44 +0200	[thread overview]
Message-ID: <2023060823-uncoated-humid-e53f@gregkh> (raw)
In-Reply-To: <20230608101616.44152-2-msekleta@redhat.com>

On Thu, Jun 08, 2023 at 12:16:16PM +0200, Michal Sekletar wrote:
> Signed-off-by: Michal Sekletar <msekleta@redhat.com>

Sorry, but for obvious reasons, I can't take patches without any
changelog text at all (and neither would you want me to.)

thanks,

greg k-h

  reply	other threads:[~2023-06-08 11:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03 13:36 [PATCH 1/2] tty: tty_io: update timestamps on all device nodes Michal Sekletar
2023-03-03 13:36 ` [PATCH 2/2] selftests: tty: add selftest for tty timestamp updates Michal Sekletar
2023-03-06  8:03 ` [PATCH 1/2] tty: tty_io: update timestamps on all device nodes Jiri Slaby
2023-06-08 10:16   ` [PATCH v2 " Michal Sekletar
2023-06-08 10:16     ` [PATCH v2 2/2] selftests: tty: add selftest for tty timestamp updates Michal Sekletar
2023-06-08 11:49       ` Greg KH [this message]
2023-06-08 11:51     ` [PATCH v2 1/2] tty: tty_io: update timestamps on all device nodes Greg KH
     [not found]       ` <CALVzVJas7g8PrTavpQ01J4vpKtqNP7fYznMMXYEM4K5XbbXRhg@mail.gmail.com>
2023-06-13 10:23         ` Greg KH
2023-06-13 10:24           ` Greg KH
2023-06-13 17:21             ` [PATCH v3 " Michal Sekletar
2023-06-13 17:21               ` [PATCH v3 2/2] selftests: tty: add selftest for tty timestamp updates Michal Sekletar

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=2023060823-uncoated-humid-e53f@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=arozansk@redhat.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=msekleta@redhat.com \
    --cc=shuah@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 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.