public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
	james.clark@linaro.org, leo.yan@linux.dev, mike.leach@linaro.org
Subject: Re: [UPDATED] [GIT PULL] coresight: Updates for Linux v6.18
Date: Wed, 24 Sep 2025 13:06:02 +0200	[thread overview]
Message-ID: <2025092446-spinout-paramount-a27b@gregkh> (raw)
In-Reply-To: <20250924082242.2306143-1-suzuki.poulose@arm.com>

On Wed, Sep 24, 2025 at 09:22:42AM +0100, Suzuki K Poulose wrote:
> Hi Greg
> 
> Please find the updated pull request to fix the invalid commit reference in
> the fixes tag, in the original pull request [0]
> 
> Apologies for the inconvenience.
> 
> [0] https://lkml.kernel.org/r/20250922125907.2268152-1-suzuki.poulose@arm.com
> 
> Kindly pull,
> 
> Suzuki
> 
> ---
> 
> The following changes since commit 1b237f190eb3d36f52dffe07a40b5eb210280e00:
> 
>   Linux 6.17-rc3 (2025-08-24 12:04:12 -0400)
> 
> are available in the Git repository at:
> 
>   git//git.kernel.org/pub/scm/linux/kernel/git/coresight/linux.git tags/coresight-next-v6.18-v2

That is not a valid "url" to pull from, how did you create this?

I've added the missing ':', but you might want to check your scripts to
verify you aren't doing something odd.

Pulled and pushed out now, thanks.

greg k-h


  reply	other threads:[~2025-09-24 11:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 12:59 [GIT PULL] coresight: Updates for Linux v6.18 Suzuki K Poulose
2025-09-23 12:14 ` Greg KH
2025-09-24  8:22   ` [UPDATED] " Suzuki K Poulose
2025-09-24 11:06     ` Greg KH [this message]
2025-09-24 11:27       ` Suzuki K Poulose

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=2025092446-spinout-paramount-a27b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=coresight@lists.linaro.org \
    --cc=james.clark@linaro.org \
    --cc=leo.yan@linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mike.leach@linaro.org \
    --cc=suzuki.poulose@arm.com \
    /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