mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: paulmck@kernel.org
Cc: Tiezhu Yang <yangtiezhu@loongson.cn>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	shuah@kernel.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2 0/6] selftests: Use "grep -E" instead of "egrep"
Date: Tue, 29 Nov 2022 16:30:39 -0700	[thread overview]
Message-ID: <07f475de-98ae-87b2-0215-12a4a2b054d6@linuxfoundation.org> (raw)
In-Reply-To: <20221129232212.GG4001@paulmck-ThinkPad-P17-Gen-1>

On 11/29/22 16:22, Paul E. McKenney wrote:

> Lazybones that I am, I would rather carry the patch than resolve
> conflicts.  Especially given the tendency for new rcutorture patches to
> appear, thus changing the conflict resolution.
> 

Sounds good. I will drop the one I applied to my tree.

> My guess is that the patch is this one:
> 
> https://lore.kernel.org/lkml/1669165413-12035-2-git-send-email-yangtiezhu@loongson.cn/
> 
> Or should I be looking elsewhere?
> 

Yup that is one.

thanks,
-- Shuah


  reply	other threads:[~2022-11-29 23:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23  1:03 Tiezhu Yang
2022-11-23  1:03 ` [PATCH v2 1/6] selftests: rcutorture: " Tiezhu Yang
2022-11-23  1:03 ` [PATCH v2 2/6] selftests: ftrace: " Tiezhu Yang
2022-11-23  1:03 ` [PATCH v2 3/6] selftests: powerpc: " Tiezhu Yang
2022-11-23  1:03 ` [PATCH v2 4/6] selftests: gpio: " Tiezhu Yang
2022-11-23  1:03 ` [PATCH v2 5/6] selftests: net: " Tiezhu Yang
2022-11-23  1:03 ` [PATCH v2 6/6] selftests: kselftest_deps: " Tiezhu Yang
2022-11-23  2:27 ` [PATCH v2 0/6] selftests: " Tiezhu Yang
2022-11-29 21:39   ` Shuah Khan
2022-11-29 22:13     ` Paul E. McKenney
2022-11-29 22:24       ` Shuah Khan
2022-11-29 23:22         ` Paul E. McKenney
2022-11-29 23:30           ` Shuah Khan [this message]
2022-11-29 23:58             ` Paul E. McKenney

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=07f475de-98ae-87b2-0215-12a4a2b054d6@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=shuah@kernel.org \
    --cc=yangtiezhu@loongson.cn \
    /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

all inboxes | Powered by JetHome®