public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Greg KH <greg@kroah.com>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Brendan Higgins <brendanhiggins@google.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: linux-next: duplicate patch in the kunit-next tree
Date: Mon, 13 Jan 2025 15:45:34 -0700	[thread overview]
Message-ID: <5e7eda18-6a1d-4008-bc6c-c3b59c27cc9e@linuxfoundation.org> (raw)
In-Reply-To: <2025011331-chef-unwired-e143@gregkh>

On 1/12/25 22:21, Greg KH wrote:
> On Mon, Jan 13, 2025 at 03:25:11PM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> The following commit is also in the driver-core tree as a different commit
>> (but the same patch):
>>
>>    875aec2357cd ("kunit: platform: Resolve 'struct completion' warning")
>>
>> This is commit
>>
>>    7687c66c18c6 ("kunit: platform: Resolve 'struct completion' warning")
>>
>> in the driver-core tree.
> 
> Thanks for letting me know.  Ugh, so many duplicates this development
> cycle, probably due to delays in the holiday season...
> 
> sorry,
> 
> greg k-h

Greg,

I can drop this patch if it is better for this to go through
driver-core.

thanks,
-- Shuah

  reply	other threads:[~2025-01-13 22:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-13  4:25 linux-next: duplicate patch in the kunit-next tree Stephen Rothwell
2025-01-13  5:21 ` Greg KH
2025-01-13 22:45   ` Shuah Khan [this message]
2025-01-14  7:28     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2024-06-11  5:22 Stephen Rothwell
2024-06-17 19:21 ` Shuah Khan
2024-06-17 19:30   ` Andrew Morton
2023-12-11 21:01 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=5e7eda18-6a1d-4008-bc6c-c3b59c27cc9e@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=brendanhiggins@google.com \
    --cc=greg@kroah.com \
    --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