On 6/28/19 1:52 PM, Randy Dunlap wrote:
> On 6/28/19 3:38 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20190627:
>>
>
> on i386:
>
> ld: kernel/bpf/cgroup.o: in function `cg_sockopt_func_proto':
> cgroup.c:(.text+0x2906): undefined reference to `bpf_sk_storage_delete_proto'
> ld: cg
On 6/28/19 3:38 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190627:
>
on x86_64:
when CONFIG_OF is not set/enabled, but
CONFIG_NVMEM_REBOOT_MODE=m selects REBOOT_MODE:
CC [M] drivers/power/reset/reboot-mode.o
../drivers/power/reset/reboot-mode.c: In function ‘reboot_mode_regis
On 6/28/19 3:38 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190627:
>
> New tree: arm-soc-fixes
>
> The net-next tree lost its build failure. It also gained a conflict
> against the net tree.
>
> The battery tree gained conflicts against the mfd and pci trees. It also
> gained a
Hi all,
Changes since 20190627:
New tree: arm-soc-fixes
The net-next tree lost its build failure. It also gained a conflict
against the net tree.
The battery tree gained conflicts against the mfd and pci trees. It also
gained a build failure for which I reverted a commit.
The devicetree tree
Hi all,
Changes since 20180627:
The sunxi tree gained a build failure so I used the version from
next-20180627.
The btrfs-kdave tree gained a build failure so I used the version from
next-20180626.
The drm tree lost its build failure.
The xarray tree gained a conflict against the wireless-driv
Hi all,
Changes since 20170627:
I applied a supplied patch to the pci tree to fix a build problem.
The i2c tree lost its build failure.
The block tree gained a conflict against the file-locks tree. It also
gained a build failure on 32 bit powerpc for which I applied a patch.
The tip tree gaine
Hi all,
Changes since 20160627:
New tree: binfmt_misc
The nfs tree lost its build failure.
The net-next tree gained a conflict against the imx-mxs tree.
The iommu tree gained a conflict against the arm tree.
The audit tree gained a conflict against the security tree.
Non-merge commits (relat
On Wed, Jul 3, 2013 at 12:37 AM, Oleg Nesterov wrote:
> Hi Sedat,
>
> On 07/02, Sedat Dilek wrote:
>>
>> did you made a cleaned-up version?
>> AFAICS v3, I read that on linux-mm ML, sorry if I ask here in this thread.
>
> Yes, I am going to send v3 with this fix + another minor change.
> Sorry for
Hi Sedat,
On 07/02, Sedat Dilek wrote:
>
> did you made a cleaned-up version?
> AFAICS v3, I read that on linux-mm ML, sorry if I ask here in this thread.
Yes, I am going to send v3 with this fix + another minor change.
Sorry for delay, I was distracted, will try tomorrow.
Besides, I think Andre
On Sun, Jun 30, 2013 at 8:19 PM, Oleg Nesterov wrote:
> Andrew, please drop these
>
> wait-introduce-wait_event_commonwq-condition-state-timeout.patch
> wait-introduce-prepare_to_wait_event.patch
>
> patches again. I'll send v3 although it really looks like I should
> never try to
Hi Oleg, Andrew,
On Sun, 30 Jun 2013 20:19:45 +0200 Oleg Nesterov wrote:
>
> Andrew, please drop these
>
> wait-introduce-wait_event_commonwq-condition-state-timeout.patch
> wait-introduce-prepare_to_wait_event.patch
>
> patches again. I'll send v3 although it really looks like I sh
On Sun, Jun 30, 2013 at 10:17 PM, wrote:
> On Sun, 30 Jun 2013 20:19:45 +0200, Oleg Nesterov said:
>>
>> Not only "__wait_no_timeout(tout) ?:" was wrong, I didn't bother
>> to recheck this logic even after I got the "warning: the omitted
>> middle operand in ?:" reports.
>>
>> Sedat, thanks you v
On Sun, Jun 30, 2013 at 8:19 PM, Oleg Nesterov wrote:
> Andrew, please drop these
>
> wait-introduce-wait_event_commonwq-condition-state-timeout.patch
> wait-introduce-prepare_to_wait_event.patch
>
> patches again. I'll send v3 although it really looks like I should
> never try to
On Sun, 30 Jun 2013 20:19:45 +0200, Oleg Nesterov said:
>
> Not only "__wait_no_timeout(tout) ?:" was wrong, I didn't bother
> to recheck this logic even after I got the "warning: the omitted
> middle operand in ?:" reports.
>
> Sedat, thanks you very much! Any chance you can try the patch below?
Andrew, please drop these
wait-introduce-wait_event_commonwq-condition-state-timeout.patch
wait-introduce-prepare_to_wait_event.patch
patches again. I'll send v3 although it really looks like I should
never try to touch wait.h.
On 06/29, Sedat Dilek wrote:
>
> As this all did not
On Sat, Jun 29, 2013 at 11:44 PM, Sedat Dilek wrote:
> On Fri, Jun 28, 2013 at 9:33 AM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> Changes since 20130627:
>>
>> This tree produces the following warning when built for many (all?)
>> configs (it has been fixed in the drm tree):
>>
>> drivers/video
On Fri, Jun 28, 2013 at 11:21 AM, Sedat Dilek wrote:
> On Fri, Jun 28, 2013 at 10:31 AM, Sedat Dilek wrote:
>> On Fri, Jun 28, 2013 at 10:29 AM, Dave Airlie wrote:
[ CC wq and drm(-intel) folks ]
>>>
>>> Already know the commit which caused it, mentioned on dri-devel,
>>> waiting
On Fri, Jun 28, 2013 at 10:31 AM, Sedat Dilek wrote:
> On Fri, Jun 28, 2013 at 10:29 AM, Dave Airlie wrote:
>>>
>>> [ CC wq and drm(-intel) folks ]
>>>
>>
>> Already know the commit which caused it, mentioned on dri-devel,
>> waiting for danvet to wake up and look, before I revert it later.
>>
>
On Fri, Jun 28, 2013 at 10:29 AM, Dave Airlie wrote:
>>
>> [ CC wq and drm(-intel) folks ]
>>
>
> Already know the commit which caused it, mentioned on dri-devel,
> waiting for danvet to wake up and look, before I revert it later.
>
Thanks, I like fast responses.
For followers... See "workqueue
>
> [ CC wq and drm(-intel) folks ]
>
Already know the commit which caused it, mentioned on dri-devel,
waiting for danvet to wake up and look, before I revert it later.
Dave.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kern
On Fri, Jun 28, 2013 at 9:33 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130627:
>
> This tree produces the following warning when built for many (all?)
> configs (it has been fixed in the drm tree):
>
> drivers/video/Kconfig:42:error: recursive dependency detected!
> drivers/video/K
21 matches
Mail list logo
