From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: error trying to fetch the clockevents tree
Date: Tue, 20 May 2025 19:23:28 +0200 [thread overview]
Message-ID: <3f2c15b3-1daa-4386-a6a1-1d05c33d58d8@linaro.org> (raw)
In-Reply-To: <20250515221042.7471ffc9@canb.auug.org.au>
Hi Stephen,
On 15/05/2025 14:10, Stephen Rothwell wrote:
> Hi Daniel,
>
> On Thu, 15 May 2025 11:20:01 +0200 Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>>
>> I had no time yet to migrate the git tree to kernel.org but the
>> servers seem to work correctly now.
>>
>> Is it possible to enable back the tree so its content gets some round
>> in linux-next before the PR ?
>
> Restored from tomorrow.
>
> Just to make sure - this is still
>
> https://git.linaro.org/people/daniel.lezcano/linux.git#timers/drivers/next
I migrated the repo to kernel.org:
https://git.kernel.org/pub/scm/linux/kernel/git/daniel.lezcano/linux.git#imers/drivers/next
Is it possible to update?
Thanks in advance
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2025-05-20 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 22:20 linux-next: error trying to fetch the clockevents tree Stephen Rothwell
2025-04-28 22:35 ` Daniel Lezcano
2025-04-28 22:49 ` Stephen Rothwell
2025-05-15 9:20 ` Daniel Lezcano
2025-05-15 12:10 ` Stephen Rothwell
2025-05-15 12:11 ` Daniel Lezcano
2025-05-20 17:23 ` Daniel Lezcano [this message]
2025-05-20 22:47 ` Stephen Rothwell
2025-05-20 22:59 ` Daniel Lezcano
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=3f2c15b3-1daa-4386-a6a1-1d05c33d58d8@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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