[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YnzZ7XeHqRaBka50@smile.fi.intel.com>
Date: Thu, 12 May 2022 12:57:01 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Henning Schild <henning.schild@...mens.com>
Cc: Guenter Roeck <linux@...ck-us.net>,
Mark Gross <markgross@...nel.org>,
Wim Van Sebroeck <wim@...ux-watchdog.org>,
linux-kernel@...r.kernel.org, linux-leds@...r.kernel.org,
platform-driver-x86@...r.kernel.org,
linux-watchdog@...r.kernel.org, Enrico Weigelt <lkml@...ux.net>,
Gerd Haeussler <gerd.haeussler.ext@...mens.com>
Subject: Re: [PATCH v2 2/4] watchdog: simatic-ipc-wdt: convert to use P2SB
accessor
On Thu, May 12, 2022 at 10:58:36AM +0200, Henning Schild wrote:
> Am Wed, 11 May 2022 11:03:04 -0700
> schrieb Guenter Roeck <linux@...ck-us.net>:
> > On 5/11/22 08:39, Henning Schild wrote:
...
> > Also, I just noticed that P2SB is neither in mainline nor
> > in linux-next, meaning this code won't even compile right now.
> > That should be mentioned in the introduction e-mail (the use
> > of "introduced" suggests that it is already there; you could
> > just use "will be introduced" instead).
>
> It was kind of in the cover letter, but maybe not verbose enough. Sorry
> for the confusion. v1 was sent in-reply-to on top of P2SB, maybe i will
> do that again for v3 but for sure point out the order in case i send it
> without the reply.
A new version of a series should start a new thread. Just use cover letter
to explain the dependencies. My expectations here is to see v3 with comments
addressed and I will incorporate it into v6 of mine. Then LKP and other
bots will be happy to test all bunch. Also, I would wait a bit for your v3,
so maintainers will have time to give their tags and/or comments.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists