Pushed to cifs-2.6.git for-next (after minor commit description text
cleanup and adding acked-by and reviewed-by)
Paulo/Aurelien,
Let me know your thoughts about Arnd's additional comments which were
interesting.
On Mon, Dec 17, 2018 at 6:49 AM Arnd Bergmann wrote:
>
> On Mon, Dec 17, 2018 at
On Mon, Dec 17, 2018 at 10:11 AM Stephen Rothwell wrote:
> I have applied the following merge fix patch (better versions welcome):
>
> From: Stephen Rothwell
> Date: Mon, 17 Dec 2018 20:03:28 +1100
> Subject: [PATCH] cifs: update for current_kernel_time64() removal
>
> Signed-off-by: Stephen
Hi Arnd,
After merging the y2038 tree, today's linux-next build (x86_64
allmodconfig) failed like this:
fs/cifs/dfs_cache.c: In function 'cache_entry_expired':
fs/cifs/dfs_cache.c:106:7: error: implicit declaration of function
'current_kernel_time64'; did you mean 'core_kernel_text'?
Hi Arnd,
After merging the y2038 tree, today's linux-next build (sparc defconfig)
failed like this:
In file included from include/linux/compat.h:22:0,
from arch/sparc/kernel/systbls.h:7,
from arch/sparc/kernel/sys_sparc_32.c:30:
arch/sparc/include/asm/compat.h:
Hi Arnd,
After merging the y2038 tree, today's linux-next build (sparc defconfig)
failed like this:
In file included from include/linux/compat.h:22:0,
from arch/sparc/kernel/systbls.h:7,
from arch/sparc/kernel/sys_sparc_32.c:30:
arch/sparc/include/asm/compat.h:
I posted the patch.
The patch has simple changes. Let me know if maybe posting a new
version makes sense.
I also needed this patch to build linux-next:
commit b784c76bb7c1c440a4ce06a18f4b3a936f33967d
Author: Deepa Dinamani
Date: Fri Mar 16 20:57:10 2018 -0700
I posted the patch.
The patch has simple changes. Let me know if maybe posting a new
version makes sense.
I also needed this patch to build linux-next:
commit b784c76bb7c1c440a4ce06a18f4b3a936f33967d
Author: Deepa Dinamani
Date: Fri Mar 16 20:57:10 2018 -0700
i40iw: add missing irq.h
On Fri, Mar 16, 2018 at 6:23 AM, Deepa Dinamani wrote:
> Hi Arnd,
>
> Do you want me to send the fix as a patch or should I re-post the series?
Please send a fix relative to linux-next. Due to my travel next week, I might
not be able to apply it right away but maybe
On Fri, Mar 16, 2018 at 6:23 AM, Deepa Dinamani wrote:
> Hi Arnd,
>
> Do you want me to send the fix as a patch or should I re-post the series?
Please send a fix relative to linux-next. Due to my travel next week, I might
not be able to apply it right away but maybe Stephen can add it on top
Hi Arnd,
Do you want me to send the fix as a patch or should I re-post the series?
Thanks,
Deepa
On Thu, Mar 15, 2018 at 7:25 PM, Stephen Rothwell wrote:
> Hi Arnd,
>
> After merging the y2038 tree, today's linux-next build (s390 allnoconfig)
> failed like this:
>
> In
Hi Arnd,
Do you want me to send the fix as a patch or should I re-post the series?
Thanks,
Deepa
On Thu, Mar 15, 2018 at 7:25 PM, Stephen Rothwell wrote:
> Hi Arnd,
>
> After merging the y2038 tree, today's linux-next build (s390 allnoconfig)
> failed like this:
>
> In file included from
Hi Arnd,
After merging the y2038 tree, today's linux-next build (s390 allnoconfig)
failed like this:
In file included from include/linux/elf.h:5:0,
from include/linux/module.h:15,
from init/main.c:16:
arch/s390/include/asm/elf.h:138:1: error: unknown type name
Hi Arnd,
After merging the y2038 tree, today's linux-next build (s390 allnoconfig)
failed like this:
In file included from include/linux/elf.h:5:0,
from include/linux/module.h:15,
from init/main.c:16:
arch/s390/include/asm/elf.h:138:1: error: unknown type name
13 matches
Mail list logo