From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Fabio Estevam" <festevam@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Tony Lindgren" <tony@atomide.com>,
"Cristian Ciocaltea" <cristian.ciocaltea@collabora.com>,
"Qinrun Dai" <flno@hust.edu.cn>
Subject: Re: [GIT PULL] timers material for v6.4-rc1
Date: Wed, 26 Apr 2023 13:17:49 +0200 [thread overview]
Message-ID: <e3efb318-2cf2-b73b-2f4d-7927a66b472c@linaro.org> (raw)
In-Reply-To: <87fs8nyplm.ffs@tglx>
On 26/04/2023 11:12, Thomas Gleixner wrote:
> On Tue, Apr 25 2023 at 13:45, Daniel Lezcano wrote:
>> The following changes since commit f7abf14f0001a5a47539d9f60bbdca649e43536b:
>>
>> posix-cpu-timers: Implement the missing timer_wait_running callback
>> (2023-04-21 15:34:33 +0200)
>>
>> are available in the Git repository at:
>>
>> ssh://git@git.linaro.org/people/daniel.lezcano/linux.git tags/timers-v6.4-rc1
>
> git@git.linaro.org: Permission denied (publickey).
>
> I used the https variant as usual ...
Oops :)
I'll see if I can do something to fix this in the future. May be migrate
the tree at git.kernel.org so whatever ssh or https, that will work
--
<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:[~2023-04-26 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 11:45 Daniel Lezcano
2023-04-26 9:12 ` Thomas Gleixner
2023-04-26 11:17 ` Daniel Lezcano [this message]
2023-04-26 9:12 ` [tip: timers/core] Merge tag 'timers-v6.4-rc1' of https://git.linaro.org/people/daniel.lezcano/linux into timers/core tip-bot2 for Thomas Gleixner
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=e3efb318-2cf2-b73b-2f4d-7927a66b472c@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=cristian.ciocaltea@collabora.com \
--cc=festevam@gmail.com \
--cc=flno@hust.edu.cn \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=u.kleine-koenig@pengutronix.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
all inboxes | Powered by JetHome®