On 11/1/20 9:28 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20201030:
>
on x86_64:
WARNING: unmet direct dependencies detected for MTD_NAND_ECC
Depends on [n]: MTD [=m] && MTD_NAND_CORE [=n]
Selected by [m]:
- MTD_NAND_ECC_SW_HAMMING [=y] && MTD [=m]
- MTD_NAND_ECC_SW_BCH [
On 11/1/20 9:28 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20201030:
>
on x86_64:
when CONFIG_NET is not enabled:
ERROR: modpost: "mac_pton" [drivers/vdpa/vdpa_sim/vdpa_sim.ko] undefined!
Should VDPA_SIM, IFCVF, MLX5_VDPA_NET depend on NET or NETDEVICES?
--
~Randy
Reported-b
On 11/1/20 9:28 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20201030:
>
on i386:
CONFIG_QCOM_RPMH=m
CONFIG_REGULATOR_QCOM_RPMH=y
ld: drivers/regulator/qcom-rpmh-regulator.o: in function
`rpmh_regulator_send_request':
qcom-rpmh-regulator.c:(.text+0xcf): undefined reference to `rpmh
Hi all,
Changes since 20201030:
The drm-misc tree lost its build failure but gained another for which
I applied a patch for a previous commit.
The pinctrl tree still had its build failure.
Non-merge commits (relative to Linus' tree): 2300
2763 files changed, 339392 insertions(+), 31126 deletio
On Fri, Nov 2, 2018 at 4:56 PM Randy Dunlap wrote:
>
> Hi,
>
> on i386 or x86_64, with gcc (SUSE Linux) 4.8.5, I am seeing this problem:
>
> In file included from :0:0:
> ../include/linux/compiler-gcc.h:75:45: internal compiler error: in
> function_and_variable_visibility, at ipa.c:825
> #define
On 11/2/18 6:57 AM, Miguel Ojeda wrote:
> On Fri, Nov 2, 2018 at 2:22 PM Stephen Rothwell wrote:
>>
>> Its always OK (and actually useful) to move your branch head up to
>> where Linus merged it (this is usually a fast forward anyway) since
>> that doesn't add any new code to linux-next to conflic
On Fri, Nov 2, 2018 at 2:22 PM Stephen Rothwell wrote:
>
> Its always OK (and actually useful) to move your branch head up to
> where Linus merged it (this is usually a fast forward anyway) since
> that doesn't add any new code to linux-next to conflict with code that
> is still pending to be merg
Hi Miguel,
On Fri, 2 Nov 2018 11:44:07 +0100 Miguel Ojeda
wrote:
>
> On Fri, Nov 2, 2018 at 4:33 AM Stephen Rothwell wrote:
> >
> > Please do not add any v4.21/v5.1 code to your linux-next included trees
> > until after the merge window closes.
>
> Is it OK to move forward the branch up to t
Hi Stephen,
On Fri, Nov 2, 2018 at 4:33 AM Stephen Rothwell wrote:
>
> Hi all,
>
> Please do not add any v4.21/v5.1 code to your linux-next included trees
> until after the merge window closes.
Is it OK to move forward the branch up to the point where it landed in
mainline, no? What about change
Hi all,
Please do not add any v4.21/v5.1 code to your linux-next included trees
until after the merge window closes.
Changes since 20181101:
Removed trees: hvc (finished with)
Non-merge commits (relative to Linus' tree): 628
817 files changed, 36481 insertions(+), 8817 deletions(-)
--
Hi all,
Changes since 20171018:
New trees: risc-v, mips-fixes, drm-amd-dc
The sunxi tree gained a build failure so I used the version from
next-20171018.
The arm64 tree gained a conflict against Linus' tree.
The powerpc tree gained a conflict against the powerpc-fixes tree.
The jc_docs tree g
On Mon, 2 Nov 2015 17:30:23 +1100
Stephen Rothwell wrote:
> So I guess I need that (or something similar) in linux-next until these
> trees are merged.
>
Yeah, the fixup looks fine to me. It will be something that Linus will
need to do himself when he hits the conflict too.
-- Steve
--
To uns
Hi Sergey,
[Excess quoted for new cc's]
On Mon, 2 Nov 2015 14:58:16 +0900 Sergey Senozhatsky
wrote:
>
> unregister_trace_sched_switch/register_trace_prio_sched_switch/etc.
> (see the log below. 80-cols unfriendly. sorry.)
> expect proto to contain 'bool preempt'
>
> TRACE_EVENT(sched_switch,
>
On (11/02/15 15:40), Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20151101:
>
Hi,
unregister_trace_sched_switch/register_trace_prio_sched_switch/etc.
(see the log below. 80-cols unfriendly. sorry.)
expect proto to contain 'bool preempt'
TRACE_EVENT(sched_switch,
TP_PROTO(bool
Hi all,
Changes since 20151101:
The pci tree still had its build failure for which I disabled a driver.
The device-mapper tree lost its build failure.
The battery tree still had its build failure so I used the version from
next-20150925.
The iommu tree lost its build failure.
The mailbox tree
Hi all,
Changes since 20121101:
The v4l-dvb tree still had its build failure so I used the version from
next-20121026.
The modules tree gained a build failure so I used the version from
next-20121101.
The kvm tree lost its conflicts.
The tmem tree lost its conflicts.
The usb tree gained 2 bui
16 matches
Mail list logo
