mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Liao, Chang" <liaochang1@huawei.com>
To: Will Deacon <will@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>, <catalin.marinas@arm.com>,
	<ptosi@google.com>, <oliver.upton@linux.dev>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: Return early when break handler is found on linked-list
Date: Thu, 24 Oct 2024 11:54:01 +0800	[thread overview]
Message-ID: <da6a0b86-4797-486c-8f02-472c9dcc01fa@huawei.com> (raw)
In-Reply-To: <20241023164014.GE29251@willie-the-truck>



在 2024/10/24 0:40, Will Deacon 写道:
> On Wed, Oct 23, 2024 at 09:52:27AM +0800, Liao, Chang wrote:
>> Kindly ping.
>>
>> I'd like to get your input on the next step. Should I send a v2 patch
>> that only removes the WARN_ON() as Will suggested? Or should I push
>> forward the refactoring of calling BRK hook [1].
> 
> If you have the bandwidth to tackle Mark's refactoring idea, then please
> feel free to send a series. Otherwise, I'm happy to merge the v2. We
> could even do both.

Will, please pick the v2 from here:

  https://lore.kernel.org/all/20241024034120.3814224-1-liaochang1@huawei.com/

Meanwhile, I will discuss the refactoring patch with Mark. Thanks for your
suggestion.

> 
> Will

-- 
BR
Liao, Chang


      reply	other threads:[~2024-10-24  3:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27 11:00 Liao Chang
2024-08-27 12:30 ` Will Deacon
2024-08-29  3:29   ` Liao, Chang
2024-08-27 12:50 ` Mark Rutland
2024-08-29  3:29   ` Liao, Chang
2024-10-23  1:52   ` Liao, Chang
2024-10-23 16:40     ` Will Deacon
2024-10-24  3:54       ` Liao, Chang [this message]

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=da6a0b86-4797-486c-8f02-472c9dcc01fa@huawei.com \
    --to=liaochang1@huawei.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=oliver.upton@linux.dev \
    --cc=ptosi@google.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

all inboxes | Powered by JetHome®