From: Yuehaibing <yuehaibing@huawei.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<linuxppc-dev@lists.ozlabs.org>, <mpe@ellerman.id.au>,
<paulus@samba.org>, <benh@kernel.crashing.org>
Subject: Re: linux-next: Tree for Apr 3
Date: Fri, 3 Apr 2020 17:00:32 +0800 [thread overview]
Message-ID: <97daf9ff-fff9-0fd2-6121-73eba88a50f4@huawei.com> (raw)
In-Reply-To: <62438df4-3546-bfea-6e7f-825faaacfaff@huawei.com>
+cc linuxppc-dev@lists.ozlabs.org
On 2020/4/3 16:54, Yuehaibing wrote:
>
>
> On 2020/4/3 13:29, Stephen Rothwell wrote:
>> Hi all,
>>
>> The merge window has opened, so please do not add any material for the
>> next release into your linux-next included trees/branches until after
>> the merge window closes.
>>
>> Changes since 20200402:
>>
>
> On PPC32, randcondfig warning this:
>
> WARNING: unmet direct dependencies detected for HOTPLUG_CPU
> Depends on [n]: SMP [=y] && (PPC_PSERIES [=n] || PPC_PMAC [=n] || PPC_POWERNV [=n] || FSL_SOC_BOOKE [=n])
> Selected by [y]:
> - PM_SLEEP_SMP [=y] && SMP [=y] && (ARCH_SUSPEND_POSSIBLE [=y] || ARCH_HIBERNATION_POSSIBLE [=y]) && PM_SLEEP [=y]
>
WARNING: multiple messages have this Message-ID (diff)
From: Yuehaibing <yuehaibing@huawei.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: linuxppc-dev@lists.ozlabs.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
paulus@samba.org
Subject: Re: linux-next: Tree for Apr 3
Date: Fri, 3 Apr 2020 17:00:32 +0800 [thread overview]
Message-ID: <97daf9ff-fff9-0fd2-6121-73eba88a50f4@huawei.com> (raw)
In-Reply-To: <62438df4-3546-bfea-6e7f-825faaacfaff@huawei.com>
+cc linuxppc-dev@lists.ozlabs.org
On 2020/4/3 16:54, Yuehaibing wrote:
>
>
> On 2020/4/3 13:29, Stephen Rothwell wrote:
>> Hi all,
>>
>> The merge window has opened, so please do not add any material for the
>> next release into your linux-next included trees/branches until after
>> the merge window closes.
>>
>> Changes since 20200402:
>>
>
> On PPC32, randcondfig warning this:
>
> WARNING: unmet direct dependencies detected for HOTPLUG_CPU
> Depends on [n]: SMP [=y] && (PPC_PSERIES [=n] || PPC_PMAC [=n] || PPC_POWERNV [=n] || FSL_SOC_BOOKE [=n])
> Selected by [y]:
> - PM_SLEEP_SMP [=y] && SMP [=y] && (ARCH_SUSPEND_POSSIBLE [=y] || ARCH_HIBERNATION_POSSIBLE [=y]) && PM_SLEEP [=y]
>
next prev parent reply other threads:[~2020-04-03 9:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 5:29 linux-next: Tree for Apr 3 Stephen Rothwell
2020-04-03 8:54 ` Yuehaibing
2020-04-03 9:00 ` Yuehaibing [this message]
2020-04-03 9:00 ` Yuehaibing
-- strict thread matches above, loose matches on Subject: below --
2024-04-03 2:22 Stephen Rothwell
2023-04-03 10:24 Stephen Rothwell
2023-04-03 15:51 ` Nathan Chancellor
2023-04-03 16:01 ` Greg Kroah-Hartman
2023-04-03 22:52 ` Stephen Rothwell
2019-04-03 8:24 Stephen Rothwell
2018-04-03 9:03 Stephen Rothwell
2017-04-03 8:13 Stephen Rothwell
2014-04-03 5:02 Stephen Rothwell
2014-04-03 5:02 ` Stephen Rothwell
2013-04-03 6:52 Stephen Rothwell
2013-04-03 6:52 ` Stephen Rothwell
2012-04-03 3:41 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=97daf9ff-fff9-0fd2-6121-73eba88a50f4@huawei.com \
--to=yuehaibing@huawei.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.