All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Yixun Lan <dlan@kernel.org>
Cc: Yixun Lan <dlan@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Brian Masney <bmasney@redhat.com>,
	Troy Mitchell <troy.mitchell@linux.spacemit.com>,
	linux-clk@vger.kernel.org, spacemit@lists.linux.dev,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] clk: spacemit: Updates for v7.3
Date: Tue, 11 Aug 2026 22:22:32 -0700	[thread overview]
Message-ID: <178651215252.5862.4480686966770442690@lazor> (raw)
In-Reply-To: <20260802014217-KYC2734409@kernel.org>

Quoting Yixun Lan (2026-08-01 18:42:52)
> Hi Stephen,
> 
>    Please pull SpacemiT's clock changes for v7.3
> 
> Yixun Lan
> 
> The following changes since commit dc59e4fea9d83f03bad6bddf3fa2e52491777482:
> 
>   Linux 7.2-rc1 (2026-06-28 12:01:31 -0700)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/spacemit/linux.git/ tags/spacemit-clk-for-7.3-1
> 
> for you to fetch changes up to 8a7d4b1924d2a424b1a6fe69de4f9464ee1fb485:
> 
>   clk: spacemit: k3: fix missing /2 factor in i2s sysclk dividers (2026-07-29 02:42:06 +0000)
> 
> ----------------------------------------------------------------

Thanks. Pulled into clk-next

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Yixun Lan <dlan@kernel.org>
Cc: Yixun Lan <dlan@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Brian Masney <bmasney@redhat.com>,
	Troy Mitchell <troy.mitchell@linux.spacemit.com>,
	linux-clk@vger.kernel.org, spacemit@lists.linux.dev,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] clk: spacemit: Updates for v7.3
Date: Tue, 11 Aug 2026 22:22:32 -0700	[thread overview]
Message-ID: <178651215252.5862.4480686966770442690@lazor> (raw)
In-Reply-To: <20260802014217-KYC2734409@kernel.org>

Quoting Yixun Lan (2026-08-01 18:42:52)
> Hi Stephen,
> 
>    Please pull SpacemiT's clock changes for v7.3
> 
> Yixun Lan
> 
> The following changes since commit dc59e4fea9d83f03bad6bddf3fa2e52491777482:
> 
>   Linux 7.2-rc1 (2026-06-28 12:01:31 -0700)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/spacemit/linux.git/ tags/spacemit-clk-for-7.3-1
> 
> for you to fetch changes up to 8a7d4b1924d2a424b1a6fe69de4f9464ee1fb485:
> 
>   clk: spacemit: k3: fix missing /2 factor in i2s sysclk dividers (2026-07-29 02:42:06 +0000)
> 
> ----------------------------------------------------------------

Thanks. Pulled into clk-next

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

  reply	other threads:[~2026-08-12  5:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-02  1:42 [GIT PULL] clk: spacemit: Updates for v7.3 Yixun Lan
2026-08-02  1:42 ` Yixun Lan
2026-08-12  5:22 ` Stephen Boyd [this message]
2026-08-12  5:22   ` Stephen Boyd

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=178651215252.5862.4480686966770442690@lazor \
    --to=sboyd@kernel.org \
    --cc=bmasney@redhat.com \
    --cc=dlan@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mturquette@baylibre.com \
    --cc=spacemit@lists.linux.dev \
    --cc=troy.mitchell@linux.spacemit.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 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.