mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <rafal@milecki.pl>
To: Wim Van Sebroeck <wim@linux-watchdog.org>
Cc: 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>,
	Alistair Francis <alistair@alistair23.me>,
	Chris Packham <chris.packham@alliedtelesis.co.nz>,
	Daniel Bristot de Oliveira <bristot@kernel.org>,
	Eduardo Valentin <eduval@amazon.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Miaoqian Lin <linmq006@gmail.com>,
	Terry Bowman <terry.bowman@amd.com>,
	Thanh Quan <thanh.quan.xn@renesas.com>
Subject: Re: [GIT PULL REQUEST] watchdog - v5.18 Merge window
Date: Thu, 31 Mar 2022 22:55:59 +0200	[thread overview]
Message-ID: <174471c557f778c0c5e55ca7f9bc02fc@milecki.pl> (raw)
In-Reply-To: <20220331182454.GA14072@www.linux-watchdog.org>

Hi Wim,

On 2022-03-31 20:24, Wim Van Sebroeck wrote:
> This series contains:
> * Add support for BCM4908

It indeed includes
[PATCH] watchdog: allow building BCM7038_WDT for BCM4908

but somehow misses
[PATCH] watchdog: bcm7038_wdt: Support BCM6345 compatible string
(which is Patchwork marked as Accepted).

This is NOT pull blocker, just sth I'd like to ask you to look at for
the next release :)

  reply	other threads:[~2022-03-31 21:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 18:24 Wim Van Sebroeck
2022-03-31 20:55 ` Rafał Miłecki [this message]
2022-03-31 21: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=174471c557f778c0c5e55ca7f9bc02fc@milecki.pl \
    --to=rafal@milecki.pl \
    --cc=akpm@linux-foundation.org \
    --cc=alistair@alistair23.me \
    --cc=bristot@kernel.org \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=eduval@amazon.com \
    --cc=linmq006@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=terry.bowman@amd.com \
    --cc=thanh.quan.xn@renesas.com \
    --cc=torvalds@linux-foundation.org \
    --cc=wim@linux-watchdog.org \
    /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®