Linux-Next Archive mirror
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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 slimbus tree
Date: Mon, 6 May 2024 10:58:56 +0100	[thread overview]
Message-ID: <42e1341a-e06d-446c-8992-986263d527db@linaro.org> (raw)
In-Reply-To: <20240506152414.5796b14b@canb.auug.org.au>

Hi Stephen,
These branches are now fixed. Thanks for reporting.

thanks,
Srini

On 06/05/2024 06:24, Stephen Rothwell wrote:
> Hi all,
> 
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):
> 
>    b12bd525ca6e ("slimbus: qcom-ngd-ctrl: Add timeout for wait operation")
>    772be93c1c24 ("slimbus: qcom-ctrl: fix module autoloading")
>    f6c637ffe528 ("slimbus: Convert to platform remove callback returning void")
>    5e8e32f81813 ("slimbus: qcom-ngd-ctrl: Reduce auto suspend delay")
> 
> These are commits
> 
>    98241a774db4 ("slimbus: qcom-ngd-ctrl: Add timeout for wait operation")
> 
> in the char-misc.current tree and
> 
>    35230d31056d ("slimbus: qcom-ctrl: fix module autoloading")
>    880b33b0580c ("slimbus: Convert to platform remove callback returning void")
>    4286dbcecc3f ("slimbus: qcom-ngd-ctrl: Reduce auto suspend delay")
> 
> in the char-misc tree.
> 

      parent reply	other threads:[~2024-05-06  9:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06  5:24 linux-next: duplicate patches in the slimbus tree Stephen Rothwell
2024-05-06  5:45 ` Stephen Rothwell
2024-05-06  9:58 ` Srinivas Kandagatla [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=42e1341a-e06d-446c-8992-986263d527db@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.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 read-only IMAP folder(s) and NNTP newsgroup(s).