linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: ARM <linux-arm-kernel@lists.infradead.org>,
	Rob Herring <robh@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the rockchip tree
Date: Wed, 16 Aug 2023 23:28:52 +0200	[thread overview]
Message-ID: <2873632.NG923GbCHz@diego> (raw)
In-Reply-To: <20230815120307.3dce0db5@canb.auug.org.au>

Hi,

Am Dienstag, 15. August 2023, 04:03:07 CEST schrieb Stephen Rothwell:
> The following commits are also in the arm-soc tree as different commits
> (but the same patches):
> 
>   8cbdf5d28809 ("ARM: rockchip: Drop unused includes")
>   fc7696e2ae81 ("soc: rockchip: grf: Explicitly include correct DT includes")
> 
> These are commits
> 
>   ab7c1ad11da4 ("ARM: rockchip: Drop unused includes")
>   0e7ed4dda9ef ("soc: rockchip: Explicitly include correct DT includes")
> 
> in the arm-soc tree.

I've dropped the patches from my side now.


Thanks for catching the duplication
Heiko




_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2023-08-16 21:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15  2:03 linux-next: duplicate patches in the rockchip tree Stephen Rothwell
2023-08-16 21:28 ` Heiko Stübner [this message]

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=2873632.NG923GbCHz@diego \
    --to=heiko@sntech.de \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=robh@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).