public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: wonder_rock@126.com
To: catalin.marinas@arm.com, will@kernel.org
Cc: ardb@kernel.org, frederic@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, mark.rutland@arm.com
Subject: Re: [PATCH 1/1] arm64: preempt: Add NEED_RESCHED to the preempt_count()
Date: Mon,  5 Sep 2022 23:50:13 +0800	[thread overview]
Message-ID: <20220905155013.20118-1-wonder_rock@126.com> (raw)
In-Reply-To: <20220905141829.28605-1-wonder_rock@126.com>

I know it is wrong. I just want to say I think preempt_count() need include NEED_RESCHED


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-09-05 18:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 14:18 [PATCH 1/1] arm64: preempt: Add NEED_RESCHED to the preempt_count() wonder_rock
2022-09-05 15:50 ` wonder_rock [this message]
2022-09-06 12:11   ` Will Deacon

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=20220905155013.20118-1-wonder_rock@126.com \
    --to=wonder_rock@126.com \
    --cc=ardb@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=frederic@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=will@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