public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Alexandre Torgue <alexandre.torgue@st•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patches in the stm32 tree
Date: Thu, 5 Jan 2023 08:37:57 +1100	[thread overview]
Message-ID: <20230105083757.0eddcd51@canb.auug.org.au> (raw)

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

Hi all,

The following commits already exist in Linus Torvald's tree as different
commits (but the same patches):

  7ad436adc788 ("ARM: multi_v7_defconfig: enable Type-C UCSI and STM32G0 as modules")
  f6309efcf037 ("ARM: dts: stm32: add mcp23017 pinctrl entry for stm32mp13")
  c07696f72ebb ("ARM: dts: stm32: add mcp23017 IO expander on I2C1 on stm32mp135f-dk")
  4cca342b840e ("ARM: dts: stm32: Rename mdio0 to mdio on DHCOR Testbench board")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2023-01-04 21:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 21:37 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-30  1:04 linux-next: duplicate patches in the stm32 tree Stephen Rothwell
2024-05-13 22:33 ` Stephen Rothwell
2024-05-14 23:54   ` Stephen Rothwell
2024-07-09  0:13 Stephen Rothwell
2024-07-16 21:53 Stephen Rothwell
2024-07-31 23:46 ` Stephen Rothwell
2024-09-06  2:08 Stephen Rothwell
2024-09-17 20:43 ` Stephen Rothwell
2025-01-05 22:37 Stephen Rothwell
2025-05-01  1:37 Stephen Rothwell
2025-05-05 21:44 ` Stephen Rothwell
2025-05-22  1:38 Stephen Rothwell
2025-06-10 23:04 ` 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=20230105083757.0eddcd51@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=alexandre.torgue@st$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /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