Linux Watchdog driver development
 help / color / mirror / Atom feed
From: Wim Van Sebroeck <wim@linux-watchdog.org>
To: Sasha Levin <sashal@kernel.org>
Cc: "Wim Van Sebroeck" <wim@linux-watchdog.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Linux Watchdog Mailing List" <linux-watchdog@vger.kernel.org>,
	"Guenter Roeck" <linux@roeck-us.net>,
	"Alexander Sverdlin" <alexander.sverdlin@siemens.com>,
	"Animesh Agarwal" <animeshagarwal28@gmail.com>,
	"Byoungtae Cho" <bt.cho@samsung.com>,
	"Christian Marangi" <ansuelsmth@gmail.com>,
	"Claudiu Beznea" <claudiu.beznea.uj@bp.renesas.com>,
	"Colin Ian King" <colin.i.king@gmail.com>,
	"Fabio Estevam" <festevam@denx.de>, "Harini T" <harini.t@amd.com>,
	"James Hilliard" <james.hilliard1@gmail.com>,
	"Jean Delvare" <jdelvare@suse.de>,
	lijuang <quic_lijuang@quicinc.com>, "Marek Vasut" <marex@denx.de>,
	"Nick Chan" <towinchenmi@gmail.com>,
	"Oleksandr Ocheretnyi" <oocheret@cisco.com>,
	"Peter Griffin" <peter.griffin@linaro.org>,
	"Rosen Penev" <rosenp@gmail.com>,
	"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
	"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	"Xingyu Wu" <xingyu.wu@starfivetech.com>,
	"Xin Liu" <quic_liuxin@quicinc.com>,
	"Yan Zhen" <yanzhen@vivo.com>,
	"Yassine Oudjana" <y.oudjana@protonmail.com>
Subject: Re: [GIT PULL REQUEST] watchdog - v6.13 release cycle.
Date: Tue, 3 Dec 2024 12:53:01 +0100	[thread overview]
Message-ID: <20241203115301.GA27487@www.linux-watchdog.org> (raw)
In-Reply-To: <Z04WJYlsYQABwAZb@sashalap>

Hi Sasha,

> On Mon, Dec 02, 2024 at 07:18:49PM +0100, Wim Van Sebroeck wrote:
> >are available in the git repository at:
> >
> > git://www.linux-watchdog.org/linux-watchdog.git linux-watchdog-6.13-rc1
> 
> Hey Wim,
> 
> Have you pushed the tag to the repo?
> 
> $ git ls-remote --tags git://www.linux-watchdog.org/linux-watchdog.git | grep v6\.13 | wc -l
> 0

Due to lack of sleep, I indeed added the tag on the wrong repo (the linux-watchdog-next repo).
Fixed.

Kind regards,
Wim.


  reply	other threads:[~2024-12-03 12:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-02 18:18 [GIT PULL REQUEST] watchdog - v6.13 release cycle Wim Van Sebroeck
2024-12-02 20:18 ` Sasha Levin
2024-12-03 11:53   ` Wim Van Sebroeck [this message]
2024-12-05 18:21 ` pr-tracker-bot

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=20241203115301.GA27487@www.linux-watchdog.org \
    --to=wim@linux-watchdog.org \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.sverdlin@siemens.com \
    --cc=animeshagarwal28@gmail.com \
    --cc=ansuelsmth@gmail.com \
    --cc=bt.cho@samsung.com \
    --cc=claudiu.beznea.uj@bp.renesas.com \
    --cc=colin.i.king@gmail.com \
    --cc=festevam@denx.de \
    --cc=harini.t@amd.com \
    --cc=james.hilliard1@gmail.com \
    --cc=jdelvare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=marex@denx.de \
    --cc=oocheret@cisco.com \
    --cc=peter.griffin@linaro.org \
    --cc=quic_lijuang@quicinc.com \
    --cc=quic_liuxin@quicinc.com \
    --cc=rosenp@gmail.com \
    --cc=sashal@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=towinchenmi@gmail.com \
    --cc=u.kleine-koenig@baylibre.com \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=xingyu.wu@starfivetech.com \
    --cc=y.oudjana@protonmail.com \
    --cc=yanzhen@vivo.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