From: Hans de Goede <hdegoede@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Mark Gross <markgross@kernel.org>
Cc: Henning Schild <henning.schild@siemens.com>,
Guenter Roeck <linux@roeck-us.net>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the drivers-x86 tree
Date: Tue, 15 Aug 2023 09:59:45 +0200 [thread overview]
Message-ID: <2f9489b4-2414-9f03-4f66-9838b8ee6be0@redhat.com> (raw)
In-Reply-To: <20230815165856.051fb20f@canb.auug.org.au>
Hi,
On 8/15/23 08:58, Stephen Rothwell wrote:
> Hi Stephen,
>
> On Tue, 15 Aug 2023 16:57:25 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> Hi all,
>>
>> The following commit is also in the watchdog tree as a different commit
>> (but the same patch):
>>
>> 3fce06406c59 ("watchdog: make Siemens Simatic watchdog driver default on platform")
>>
>> This is commit
>>
>> 926df9ae133d ("watchdog: make Siemens Simatic watchdog driver default on platform")
>
> in the watchdog tree.
Guenter, IIRC we agreed that I would merge this one through
the pdx86 tree?
specifically through the platform-drivers-x86-simatic-ipc branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=platform-drivers-x86-simatic-ipc
I even Cc-ed you on the pull-req for the the ib-pdx86-simatic-v6.6-2
tag for which I send a pull-req to Lee because it contains some bits
which are dependencies for some LED driver patches:
https://lore.kernel.org/linux-leds/f16554b9-d34e-4e19-052b-c818ef81d361@redhat.com/
Regards,
Hans
next prev parent reply other threads:[~2023-08-15 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 6:57 linux-next: duplicate patch in the drivers-x86 tree Stephen Rothwell
2023-08-15 6:58 ` Stephen Rothwell
2023-08-15 7:59 ` Hans de Goede [this message]
2023-08-15 15:21 ` Guenter Roeck
2023-08-19 15:25 ` Wim Van Sebroeck
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=2f9489b4-2414-9f03-4f66-9838b8ee6be0@redhat.com \
--to=hdegoede@redhat.com \
--cc=henning.schild@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=markgross@kernel.org \
--cc=sfr@canb.auug.org.au \
--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