All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	platform-driver-x86@vger.kernel.org,
	Mark Gross <mgross@linux.intel.com>,
	linux-watchdog@vger.kernel.org,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Linus Walleij <linus.walleij@linaro.org>,
	Alessandro Zummo <a.zummo@towertech.it>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Arnd Bergmann <arnd@kernel.org>, Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH v1 1/5] watchdog: intel_scu_watchdog: Remove driver for deprecated platform
Date: Fri, 22 Jan 2021 17:45:06 +0200	[thread overview]
Message-ID: <YArzAvcZXfv8DaI4@smile.fi.intel.com> (raw)
In-Reply-To: <YArtsQSQsGdfNlBI@smile.fi.intel.com>

+Cc: Arnd, RTC maintainers, Lee

On Fri, Jan 22, 2021 at 05:22:25PM +0200, Andy Shevchenko wrote:
> On Fri, Jan 22, 2021 at 03:59:34PM +0100, Hans de Goede wrote:
> > Hi,
> > 
> > What is the plan for merging this series ?
> > 
> > It touches files under:
> > arch/x86
> > drivers/watchdog
> > drivers/platform/x86
> > 
> > It is probably best if the entire series is merged through a single
> > tree. I don't expect this to cause any conflicts with current / upcoming
> > changes under drivers/platform/x86, so I'm fine with this being merged
> > through another tree.
> > 
> > Or if I can get an ack for that from the x86 and watchdog maintainers
> > I can merge the entire series through the pdx86 tree.
> 
> For time being I'm collecting tags and comments.
> As of today this series is independent per se, but other (later) clean up
> patches may rely on this.
> 
> One strategy can be providing an immutable branch for anybody who wants it and
> merge thru PDx86 or watchdog tree (I guess PDx86 is preferable because there
> are more patches touching other stuff, though independently, in this matters).

Yes, I think one more time and guess the best is:
 - get tags from x86 / watchdog
 - get tag from RTC
 - collect everything in PDx86 immutable branch
 - part 2 can be merged thru Lee's MFD tree with taking above mentioned branch
   as a base
 - part 3 (SFI removal) can be done based on Lee's branch and via tip tree

in this case we won't wait all maintainers to give a tag in a short period of
time (like couple of weeks from now on).

The full series (all three parts) are located in [1].

[1]: https://gitlab.com/andy-shev/next/-/tree/topic/mid-removal-next

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2021-01-22 18:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 12:31 [PATCH v1 1/5] watchdog: intel_scu_watchdog: Remove driver for deprecated platform Andy Shevchenko
2021-01-22 12:31 ` [PATCH v1 2/5] watchdog: intel-mid_wdt: Postpone IRQ handler registration till SCU is ready Andy Shevchenko
2021-01-22 14:17   ` Guenter Roeck
2021-01-22 12:31 ` [PATCH v1 3/5] platform/x86: intel_scu_wdt: Move driver from arch/x86 Andy Shevchenko
2021-01-22 14:21   ` Guenter Roeck
2021-01-22 12:32 ` [PATCH v1 4/5] platform/x86: intel_scu_wdt: Drop SCU notification Andy Shevchenko
2021-01-22 14:21   ` Guenter Roeck
2021-01-22 12:32 ` [PATCH v1 5/5] platform/x86: intel_scu_wdt: Get rid of custom x86 model comparison Andy Shevchenko
2021-01-22 14:23   ` Guenter Roeck
2021-01-22 14:16 ` [PATCH v1 1/5] watchdog: intel_scu_watchdog: Remove driver for deprecated platform Guenter Roeck
2021-01-22 14:59 ` Hans de Goede
2021-01-22 15:22   ` Andy Shevchenko
2021-01-22 15:45     ` Andy Shevchenko [this message]
2021-01-22 21:04       ` Hans de Goede
2021-01-23  0:27         ` Guenter Roeck
2021-01-23 12:05           ` Hans de Goede
2021-01-25 11:15             ` Andy Shevchenko
2021-01-25 11:23               ` Hans de Goede
2021-01-25 13:52                 ` Andy Shevchenko

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=YArzAvcZXfv8DaI4@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arnd@kernel.org \
    --cc=bp@alien8.de \
    --cc=hdegoede@redhat.com \
    --cc=hpa@zytor.com \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mgross@linux.intel.com \
    --cc=mingo@redhat.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=wim@linux-watchdog.org \
    --cc=x86@kernel.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 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.