public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Donghoon Yu <hoony.yu@samsung.com>,
	Will McVicker <willmcvicker@google.com>,
	Youngmin Nam <youngmin.nam@samsung.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: linux-next: build warning after merge of the clockevents tree
Date: Thu, 31 Jul 2025 00:26:54 +1000	[thread overview]
Message-ID: <20250731002654.19af9458@canb.auug.org.au> (raw)
In-Reply-To: <e8e2bc93-1639-433d-9689-d1ce9f28b877@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 236 bytes --]

Hi Daniel,

On Wed, 30 Jul 2025 14:22:27 +0200 Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>
> This should be fixed now.
> 
> Also the clockevent branch has been reset.

Thanks for both.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2025-07-30 14:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16  6:08 linux-next: build warning after merge of the clockevents tree Stephen Rothwell
     [not found] ` <CAKnoXLynCY8dAe8k+ttTVpN2U49_-DyQFU7t1BRk-x74tfJ78Q@mail.gmail.com>
2025-07-18 22:08   ` Stephen Rothwell
2025-07-29  1:40 ` Stephen Rothwell
2025-07-30 12:22   ` Daniel Lezcano
2025-07-30 14:26     ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-14  1:16 Stephen Rothwell
2020-01-06  2:37 Stephen Rothwell
2014-01-16  4:03 Stephen Rothwell

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=20250731002654.19af9458@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=daniel.lezcano@linaro.org \
    --cc=hoony.yu@samsung.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=willmcvicker@google.com \
    --cc=youngmin.nam@samsung.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