llvm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Edward Liaw <edliaw@google.com>,
	linux-kernel@vger.kernel.org, John Stultz <jstultz@google.com>,
	Stephen Boyd <sboyd@kernel.org>, Shuah Khan <shuah@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>
Cc: linux-kselftest@vger.kernel.org, kernel-team@android.com,
	Edward Liaw <edliaw@google.com>,
	llvm@lists.linux.dev
Subject: Re: [PATCH v1 0/3] selftests/timers/posix_timers: various cleanups
Date: Thu, 07 Mar 2024 22:04:43 +0100	[thread overview]
Message-ID: <87bk7pu51w.ffs@tglx> (raw)
In-Reply-To: <20240304181140.644212-1-edliaw@google.com>

On Mon, Mar 04 2024 at 18:11, Edward Liaw wrote:
> I'm sending some patches that were orignally in
> https://lore.kernel.org/lkml/20230606132949.068951363@linutronix.de/
> to prevent the timer_distribution test from hanging and also fix some
> format inconsistencies.

Thanks for picking those up and moving them forward. Any particular
reason why you didn't pick up the full set?

Thanks,

        tglx

  parent reply	other threads:[~2024-03-07 21:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 18:11 [PATCH v1 0/3] selftests/timers/posix_timers: various cleanups Edward Liaw
2024-03-04 18:11 ` [PATCH v1 1/3] selftests/timers/posix_timers: Make signal distribution test less fragile Edward Liaw
2024-03-04 18:11 ` [PATCH v1 2/3] selftests/timers/posix_timers: Use TAP reporting format Edward Liaw
2024-03-04 18:11 ` [PATCH v1 3/3] selftests/timers/posix_timers: Use llabs for long long Edward Liaw
2024-03-07 21:04 ` Thomas Gleixner [this message]
     [not found]   ` <CAG4es9XXYzzrt3-eybtXZ2Cy9fTtEPiCbggDxPcaRY=fiKM78A@mail.gmail.com>
2024-03-07 21:41     ` [PATCH v1 0/3] selftests/timers/posix_timers: various cleanups Thomas Gleixner

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=87bk7pu51w.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=edliaw@google.com \
    --cc=jstultz@google.com \
    --cc=justinstitt@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=sboyd@kernel.org \
    --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 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).