From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Rob Herring <robh@kernel•org>, Wim Van Sebroeck <wim@iguana•be>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patch in the devicetree tree
Date: Tue, 7 Jan 2025 15:20:38 +1100 [thread overview]
Message-ID: <20250107152038.02dbb1b0@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 326 bytes --]
Hi all,
The following commit is also in the watchdog tree as a different commit
(but the same patch):
d3571aa59a61 ("dt-bindings: watchdog: Document Qualcomm IPQ5424")
This is commit
b3db0b5356ff ("dt-bindings: watchdog: Document Qualcomm IPQ5424")
in the watchdog tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-01-07 4:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 4:20 Stephen Rothwell [this message]
2025-01-07 14:23 ` linux-next: duplicate patch in the devicetree tree Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2025-08-13 2:14 Stephen Rothwell
2025-08-13 17:30 ` Bjorn Helgaas
2024-09-16 6:01 Stephen Rothwell
2024-09-16 17:04 ` Wim Van Sebroeck
2024-09-05 6:40 Stephen Rothwell
2024-09-05 7:27 ` Krzysztof Wilczyński
2024-09-05 12:57 ` Rob Herring
2024-05-03 4:15 Stephen Rothwell
2024-05-03 7:13 ` Lee Jones
2024-05-03 12:44 ` Rob Herring
2024-04-11 5:48 Stephen Rothwell
2024-04-11 12:40 ` Rob Herring
2024-03-11 22:51 Stephen Rothwell
2023-10-25 21:19 Stephen Rothwell
2023-10-26 12:43 ` Rob Herring
2023-01-18 0:19 Stephen Rothwell
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=20250107152038.02dbb1b0@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=robh@kernel$(echo .)org \
--cc=wim@iguana$(echo .)be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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