All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Peter Griffin <peter.griffin@linaro.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	Peng Fan <peng.fan@nxp.com>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	Sergio Paracuellos <sergio.paracuellos@gmail.com>,
	Mubin Sayyed <mubin.sayyed@amd.com>,
	Ley Foon Tan <lftan@altera.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] timer drivers for v6.9-rc1
Date: Sat, 16 Mar 2024 00:58:36 +0100	[thread overview]
Message-ID: <87a5mzjbdf.ffs@tglx> (raw)
In-Reply-To: <5552010a-1ce2-46a1-a740-a69f2e9a2cf2@linaro.org>

On Wed, Mar 13 2024 at 16:37, Daniel Lezcano wrote:
> The following changes since commit 71fee48fb772ac4f6cfa63dbebc5629de8b4cc09:
>
>    tick-sched: Fix idle and iowait sleeptime accounting vs CPU hotplug 
> (2024-01-19 16:40:38 +0100)
>
> are available in the Git repository at:
>
>    https://git.linaro.org/people/daniel.lezcano/linux.git 
> tags/timers-v6.9-rc1

First of all why are you sending this pull request in the middle of the
merge window instead of having it in my tree at least a week ago?

That aside:

git pull https://git.linaro.org/people/daniel.lezcano/linux.git tags/timers-v6.9-rc1
fatal: protocol error: bad pack header

Three times in a row with a 5 minutes gap between each attempts. I try
it again tomorrow morning.

Thanks,

        tglx

  reply	other threads:[~2024-03-15 23:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13 15:37 [GIT PULL] timer drivers for v6.9-rc1 Daniel Lezcano
2024-03-15 23:58 ` Thomas Gleixner [this message]
2024-03-18  8:36   ` Daniel Lezcano
2024-03-18 10:07 ` [tip: timers/core] Merge tag 'timers-v6.9-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=87a5mzjbdf.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=daniel.lezcano@linaro.org \
    --cc=lftan@altera.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=mubin.sayyed@amd.com \
    --cc=peng.fan@nxp.com \
    --cc=peter.griffin@linaro.org \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=rdunlap@infradead.org \
    --cc=sergio.paracuellos@gmail.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.