X86 platform drivers
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
	<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
	Platform Driver <platform-driver-x86@vger.kernel.org>,
	Mark Gross <mgross@linux.intel.com>,
	linux-watchdog@vger.kernel.org,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	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: Mon, 25 Jan 2021 12:23:03 +0100	[thread overview]
Message-ID: <f89f2650-73aa-337d-5219-141cd1a2ba32@redhat.com> (raw)
In-Reply-To: <CAHp75VdE4LSHTKLuZ6x744224N2AvbMU0JeMmTWoqeEHDj7=2A@mail.gmail.com>

Hi,

On 1/25/21 12:15 PM, Andy Shevchenko wrote:
> On Sat, Jan 23, 2021 at 2:08 PM Hans de Goede <hdegoede@redhat.com> wrote:
>> On 1/23/21 1:27 AM, Guenter Roeck wrote:
>>> On 1/22/21 1:04 PM, Hans de Goede wrote:
>>>> On 1/22/21 4:45 PM, Andy Shevchenko wrote:
>>>>> 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:
> 
>>>>>>> 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
>>>>
>>>> Ok, that works for me. I assume that it is best for the other subsystems
>>>> if I create an immutable branch for this based on 5.11-rc1
>>>> (and then merge that into pdx86/for-next) ?
>>>>
>>>> Guenter, I believe you have already reviewed all the watchdog changes,
>>>> are you ok with me creating an immutable branch for the entire series
>>>> and then sending you a pull-req for that ?
>>>
>>> Wim handles watchdog pull requests,
> 
> Wim, can you Ack the watchdog changes?
> 
>> Ah, sorry I was under the impression you would do that because you were
>> doing the reviews (which I'm sure Wim appreciates).
>>
>>> and he usually creates a branch
>>> for Linus to pull from either during or shortly before a commit window.
>>> Also, I don't immediately see why the watchdog tree should carry the other
>>> patches of this series, immutable or not; I would not expect a dependency
>>> against those.
>>>
>>> Anyway, I am fine if the the wdt driver removal is submitted through some
>>> other branch.
>>
>> Hmm, looking at the code again it indeed seems that patch 1/5 + 2/5 could
>> be simply merged through the watchdog tree, as they don't appear to
>> have any interdependencies with the arch/x86 and drivers/platform/x86
>> changes.  Andy ?
> 
> The first patch is a dependency to the later (that are not published yet).
> I was considering gathering all dependent patches in immutable
> branches and doing in three parts / phases.
> 
> I can prepare a branch with a first batch (with Acks from respective
> maintainers) and send a PR to you.
> Would it work?

I guess you would then publish this as an immutable branch yourself and
send a PR to all involved subsys-maintainers ?

You have commit rights to the pdx86/platform-drivers-x86 git repo if
I'm not mistaken, so you could publish the immutable branch there if
you want.

That actually sounds like a good plan to me, assuming the other maintainers
are ok with it too.

Regards,

Hans


  reply	other threads:[~2021-01-26 19:18 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
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 [this message]
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=f89f2650-73aa-337d-5219-141cd1a2ba32@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=arnd@kernel.org \
    --cc=bp@alien8.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox