public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Hans de Goede <hdegoede@redhat.com>, 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 16:58:56 +1000	[thread overview]
Message-ID: <20230815165856.051fb20f@canb.auug.org.au> (raw)
In-Reply-To: <20230815165725.30a01fe9@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 483 bytes --]

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.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-08-15  6:59 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 [this message]
2023-08-15  7:59   ` Hans de Goede
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=20230815165856.051fb20f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=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=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