linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: "Guenter Roeck" <linux@roeck-us.net>,
	linux-watchdog@vger.kernel.org, wim@linux-watchdog.org,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	matthias.bgg@gmail.com, arinc.unal@arinc9.com,
	p.zabel@pengutronix.de, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, linux-mips@vger.kernel.org,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v7 2/5] mips: dts: ralink: mt7621: rename watchdog node from 'wdt' into 'watchdog'
Date: Tue, 28 Feb 2023 09:39:20 +0100	[thread overview]
Message-ID: <20230228083920.GA5801@alpha.franken.de> (raw)
In-Reply-To: <CAMhs-H_Ce-+MFi5zTMg8v8dSSg5ioaTy+Pw-0QMgK++PVtEViQ@mail.gmail.com>

On Tue, Feb 28, 2023 at 05:44:21AM +0100, Sergio Paracuellos wrote:
> On Tue, Feb 14, 2023 at 4:12 PM Sergio Paracuellos
> <sergio.paracuellos@gmail.com> wrote:
> >
> > On Tue, Feb 14, 2023 at 4:11 PM Guenter Roeck <linux@roeck-us.net> wrote:
> > >
> > > On Tue, Feb 14, 2023 at 11:39:33AM +0100, Sergio Paracuellos wrote:
> > > > Watchdog nodes must use 'watchdog' for node name. When a 'make dtbs_check'
> > > > is performed the following warning appears:
> > > >
> > > > wdt@100: $nodename:0: 'wdt@100' does not match '^watchdog(@.*|-[0-9a-f])?$'
> > > >
> > > > Fix this warning up properly renaming the node into 'watchdog'.
> > > >
> > > > Reviewed-by: Arınç ÜNAL <arinc.unal@arinc9.com>
> > > > Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> > > > Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> > >
> > > Acked-by: Guenter Roeck <linux@roeck-us.net>
> > >
> > > Note that we can not apply this and the next patch of the series
> > > through the watchdog tree since it crosses a maintainer boundary.
> >
> > I was expecting Thomas to get these two arch/mips patches or get an
> > Acked-by from him in order for you to apply them.
> 
> Hi Thomas,
> 
> I think you have missed this series since you have started to apply
> newer stuff in mips-next. Are you ok with taking or Acking patches 2
> and 3 of this series?

yes, I sort of missed it. If it's enough to take patch 2/3 I'll do that.
If it's better to keep the series, I'm also ok with acking them.
What's the best way forward ?

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2023-02-28  8:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 10:39 [PATCH v7 0/5] watchdog: mt7621-wdt: avoid globals and arch dependencies Sergio Paracuellos
2023-02-14 10:39 ` [PATCH v7 1/5] dt-bindings: watchdog: mt7621-wdt: add phandle to access system controller registers Sergio Paracuellos
2023-02-14 15:10   ` Guenter Roeck
2023-02-14 10:39 ` [PATCH v7 2/5] mips: dts: ralink: mt7621: rename watchdog node from 'wdt' into 'watchdog' Sergio Paracuellos
2023-02-14 15:11   ` Guenter Roeck
2023-02-14 15:12     ` Sergio Paracuellos
2023-02-28  4:44       ` Sergio Paracuellos
2023-02-28  8:39         ` Thomas Bogendoerfer [this message]
2023-02-28  8:51           ` Sergio Paracuellos
2023-02-28 14:55             ` Guenter Roeck
2023-02-28 15:46               ` Sergio Paracuellos
2023-02-28 22:15   ` Thomas Bogendoerfer
2023-02-14 10:39 ` [PATCH v7 3/5] mips: dts: ralink: mt7621: add phandle to system controller node for watchdog Sergio Paracuellos
2023-02-14 15:11   ` Guenter Roeck
2023-02-28 22:15   ` Thomas Bogendoerfer
2023-02-14 10:39 ` [PATCH v7 4/5] watchdog: mt7621-wdt: avoid static global declarations Sergio Paracuellos
2023-02-14 10:39 ` [PATCH v7 5/5] watchdog: mt7621-wdt: avoid ralink architecture dependent code Sergio Paracuellos
2023-02-14 15:11   ` Guenter Roeck

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=20230228083920.GA5801@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=arinc.unal@arinc9.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=matthias.bgg@gmail.com \
    --cc=p.zabel@pengutronix.de \
    --cc=philmd@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=sergio.paracuellos@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).