All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Zhijian <zhijianx.li@intel.com>
To: paulmck@kernel.org
Cc: dave@stgolabs.net, joel@joelfernandes.org, josh@joshtriplett.org,
	mathieu.desnoyers@efficios.com, rostedt@goodmis.org,
	rcu@vger.kernel.org, philip.li@intel.com,
	lizhijian@cn.fujitsu.com, jiangshanlai@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] scftorture: always log error message
Date: Wed, 3 Nov 2021 16:24:53 +0800	[thread overview]
Message-ID: <15e9b661-d61b-f555-b16e-671a4aabc8db@intel.com> (raw)
In-Reply-To: <20211102160656.GI880162@paulmck-ThinkPad-P17-Gen-1>



On 03/11/2021 00:06, Paul E. McKenney wrote:
> On Fri, Oct 29, 2021 at 05:40:27PM +0800, Li Zhijian wrote:
>> Generally, error message should be logged anyhow.
>>
>> Signed-off-by: Li Zhijian<zhijianx.li@intel.com>
> I have queued the patches up to this point for the v5.17 merge window
> (not the current one, but the next one).
>
> This one does not apply.  It looks like you created it against mainline
> rather than -rcu.  You can learn about the -rcu tree and its habits here:
>
> https://mirrors.edge.kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
>
> Please port this patch to -rcu so that I can pull it in without
> conflicting with patches in -rcu.
Glad to know this, i will rebase the rest 2 patches and resubmit them soon.

Thanks
Zhijian


>


  reply	other threads:[~2021-11-03  8:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29  9:40 [PATCH 0/6] minor fixes and cleanups in rcuscale and torture tests Li Zhijian
2021-10-29  9:40 ` [PATCH 1/6] refscale: add missing '\n' to flush message out Li Zhijian
2021-10-29  9:40 ` [PATCH 2/6] scftorture: " Li Zhijian
2021-10-29  9:40 ` [PATCH 3/6] scftorture: remove unused SCFTORTOUT Li Zhijian
2021-10-29  9:40 ` [PATCH 4/6] scftorture: always log error message Li Zhijian
2021-11-02 16:06   ` Paul E. McKenney
2021-11-03  8:24     ` Li Zhijian [this message]
2021-10-29  9:40 ` [PATCH 5/6] rcuscale: alwaly " Li Zhijian
2021-10-29 16:40   ` Davidlohr Bueso
2021-11-02 16:09   ` Paul E. McKenney
2021-10-29  9:40 ` [PATCH 6/6] locktorture,rcutorture,torture: always " Li Zhijian
2021-10-29 16:41 ` [PATCH 0/6] minor fixes and cleanups in rcuscale and torture tests Davidlohr Bueso

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=15e9b661-d61b-f555-b16e-671a4aabc8db@intel.com \
    --to=zhijianx.li@intel.com \
    --cc=dave@stgolabs.net \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=paulmck@kernel.org \
    --cc=philip.li@intel.com \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.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.