The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Stephen Eta Zhou <stephen.eta.zhou@outlook.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] clocksource: timer-sp804: Fix read_current_timer() issue when clock source is not registered
Date: Tue, 8 Apr 2025 20:52:18 +0200	[thread overview]
Message-ID: <65bfb302-3e93-4d1f-a70c-66439cf5f122@kernel.org> (raw)
In-Reply-To: <BYAPR12MB320552F9F18EBC4F51E7213CD5B52@BYAPR12MB3205.namprd12.prod.outlook.com>

On 08/04/2025 09:00, Stephen Eta Zhou wrote:
> Hi all,
> 
> Just pinging this patch, it's been about a month since I sent out v2,
> but I haven't received any feedback yet.
> 
> If there are any issues with this patch, feel free to let me know. Thanks!
It does not look like patch at all - it has duplicated From and Subject.
Please read submitting patches. The patch fails this in multiple places.

What's more the actual patch is corrupted, so could not be even applied.
You can try by yourself to apply it and see.

Anyway, follow closely submitting patches.

About the actual problem: I don't understand how commit msg is related
to it.

Best regards,
Krzysztof

  reply	other threads:[~2025-04-08 18:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-08 16:31 [PATCH v2] clocksource: timer-sp804: Fix read_current_timer() issue when clock source is not registered stephen eta zhou
2025-04-08  7:00 ` Stephen Eta Zhou
2025-04-08 18:52   ` Krzysztof Kozlowski [this message]
2025-04-09  5:34     ` Stephen Eta Zhou

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=65bfb302-3e93-4d1f-a70c-66439cf5f122@kernel.org \
    --to=krzk@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stephen.eta.zhou@outlook.com \
    --cc=tglx@linutronix.de \
    /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