mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>
Cc: ARM <linux-arm-kernel@lists.infradead.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 samsung-krzk tree
Date: Wed, 10 Jul 2024 08:38:37 +0200	[thread overview]
Message-ID: <6c4f0f95-8555-4907-9ed9-863add5af99a@kernel.org> (raw)
In-Reply-To: <20240710123327.632f7400@canb.auug.org.au>

On 10/07/2024 04:33, Stephen Rothwell wrote:
> Hi all,
> 
> The following commit is also in the arm-soc tree as a different commit
> (but the same patch):
> 
>   85863cee8ce0 ("soc: samsung: exynos-pmu: add support for PMU_ALIVE non atomic registers")
> 
> This is commit
> 
>   97c4264f62a7 ("soc: samsung: exynos-pmu: add support for PMU_ALIVE non atomic registers")
> 


That's expected. I dropped the patch from my tree now, thanks.

Best regards,
Krzysztof


  reply	other threads:[~2024-07-10  6:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-10  2:33 Stephen Rothwell
2024-07-10  6:38 ` Krzysztof Kozlowski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-11-24  1:09 Stephen Rothwell
2025-11-24  7:49 ` Krzysztof Kozlowski
2023-10-17  0:01 Stephen Rothwell
2023-10-17  9:42 ` Uwe Kleine-König
2023-10-17  9:50   ` Krzysztof Kozlowski
2023-09-29  0:25 Stephen Rothwell
2023-10-03  6:22 ` Krzysztof Kozlowski
2023-10-03 14:31   ` Arnd Bergmann
2023-08-15  2:06 Stephen Rothwell
2023-08-15  4:59 ` Krzysztof Kozlowski
2023-06-29 22:46 Stephen Rothwell
2023-07-01  7:57 ` Krzysztof Kozlowski

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=6c4f0f95-8555-4907-9ed9-863add5af99a@kernel.org \
    --to=krzk@kernel.org \
    --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=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

all inboxes | Powered by JetHome®