Re: linux-next: Tree for Sep 12 (bcachefs)

On Thu, Sep 14, 2023 at 03:38:07PM -0400, Kent Overstreet wrote: > On Wed, Sep 13, 2023 at 06:17:00PM -0700, Kees Cook wrote: > > It looks like you just want a type union for the flexible array. > > This can be done like this: > > > > struct bch_sb_field_journal_seq_blacklist { > > struct

Re: linux-next: Tree for Sep 12 (bcachefs)

On 9/14/23 13:38, Kent Overstreet wrote: On Wed, Sep 13, 2023 at 06:17:00PM -0700, Kees Cook wrote: On Tue, Sep 12, 2023 at 03:26:45PM +1000, Stephen Rothwell wrote: New tree: bcachefs Thanks for going through and fixing all the fake flexible array members. It looks much nicer. :) I have

Re: linux-next: Tree for Sep 12 (bcachefs)

On Wed, Sep 13, 2023 at 06:17:00PM -0700, Kees Cook wrote: > On Tue, Sep 12, 2023 at 03:26:45PM +1000, Stephen Rothwell wrote: > > New tree: bcachefs > > Thanks for going through and fixing all the fake flexible array members. > It looks much nicer. :) > > I have some questions about the

Re: linux-next: Tree for Sep 12 (bcachefs)

On Tue, Sep 12, 2023 at 03:26:45PM +1000, Stephen Rothwell wrote: > New tree: bcachefs Thanks for going through and fixing all the fake flexible array members. It looks much nicer. :) I have some questions about the remaining "markers", for example: $ git grep -A8 '\bkey_start\b' -- fs/bcachefs

linux-next: Tree for Sep 12

Hi all, News: there will be no linux-next releases on Friday or Monday. Changes since 20180911: Dropped trees: xarray, ida (temporarily) I applied a patch for a runtime problem in the vfs tree and I still disabled building some samples. The drm-misc tree gained a conflict against the drm

linux-next: Tree for Sep 12

Hi all, News: there will be no linux-next releases on Friday or Monday. Changes since 20180911: Dropped trees: xarray, ida (temporarily) I applied a patch for a runtime problem in the vfs tree and I still disabled building some samples. The drm-misc tree gained a conflict against the drm

Re: linux-next: Tree for Sep 12

On (09/14/17 09:48), Andy Lutomirski wrote: > On Tue, Sep 12, 2017 at 6:18 AM, Sergey Senozhatsky > wrote: > > Hi Andy, > > > > got the following warn for each CPU > > > > > > [0.00] [ cut here ] > > [0.00] WARNING: CPU: 0 PID:

Re: linux-next: Tree for Sep 12

On (09/14/17 09:48), Andy Lutomirski wrote: > On Tue, Sep 12, 2017 at 6:18 AM, Sergey Senozhatsky > wrote: > > Hi Andy, > > > > got the following warn for each CPU > > > > > > [0.00] [ cut here ] > > [0.00] WARNING: CPU: 0 PID: 0 at arch/x86/mm/tlb.c:245 >

Re: linux-next: Tree for Sep 12

On Tue, Sep 12, 2017 at 6:18 AM, Sergey Senozhatsky wrote: > Hi Andy, > > got the following warn for each CPU > > > [0.00] [ cut here ] > [0.00] WARNING: CPU: 0 PID: 0 at arch/x86/mm/tlb.c:245 >

Re: linux-next: Tree for Sep 12

On Tue, Sep 12, 2017 at 6:18 AM, Sergey Senozhatsky wrote: > Hi Andy, > > got the following warn for each CPU > > > [0.00] [ cut here ] > [0.00] WARNING: CPU: 0 PID: 0 at arch/x86/mm/tlb.c:245 > initialize_tlbstate_and_flush+0x60/0xd4 > [0.00]

Re: linux-next: Tree for Sep 12

Hi Andy, got the following warn for each CPU [0.00] [ cut here ] [0.00] WARNING: CPU: 0 PID: 0 at arch/x86/mm/tlb.c:245 initialize_tlbstate_and_flush+0x60/0xd4 [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted

Re: linux-next: Tree for Sep 12

Hi Andy, got the following warn for each CPU [0.00] [ cut here ] [0.00] WARNING: CPU: 0 PID: 0 at arch/x86/mm/tlb.c:245 initialize_tlbstate_and_flush+0x60/0xd4 [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted

linux-next: Tree for Sep 12

Hi all, Please do not add any v4.15 related material to your linux-next included branches until after v4.14-rc1 has been released. Changes since 20170911: Non-merge commits (relative to Linus' tree): 1124 1423 files changed, 55946 insertions(+), 14234 deletions(-)

linux-next: Tree for Sep 12

Hi all, Please do not add any v4.15 related material to your linux-next included branches until after v4.14-rc1 has been released. Changes since 20170911: Non-merge commits (relative to Linus' tree): 1124 1423 files changed, 55946 insertions(+), 14234 deletions(-)

Re: linux-next: Tree for Sep 12 (leds/leds-mlxcpld.c)

Hi Randy, On 09/12/2016 07:01 PM, Randy Dunlap wrote: On 09/11/16 22:42, Stephen Rothwell wrote: Hi all, Changes since 20160909: on x86_64: ../drivers/leds/leds-mlxcpld.c: In function 'mlxcpld_led_bus_access_func': ../drivers/leds/leds-mlxcpld.c:253:3: error: implicit declaration of

Re: linux-next: Tree for Sep 12 (leds/leds-mlxcpld.c)

Hi Randy, On 09/12/2016 07:01 PM, Randy Dunlap wrote: On 09/11/16 22:42, Stephen Rothwell wrote: Hi all, Changes since 20160909: on x86_64: ../drivers/leds/leds-mlxcpld.c: In function 'mlxcpld_led_bus_access_func': ../drivers/leds/leds-mlxcpld.c:253:3: error: implicit declaration of

Re: linux-next: Tree for Sep 12 (leds/leds-mlxcpld.c)

On 09/11/16 22:42, Stephen Rothwell wrote: > Hi all, > > Changes since 20160909: > on x86_64: ../drivers/leds/leds-mlxcpld.c: In function 'mlxcpld_led_bus_access_func': ../drivers/leds/leds-mlxcpld.c:253:3: error: implicit declaration of function 'outb' [-Werror=implicit-function-declaration]

Re: linux-next: Tree for Sep 12 (leds/leds-mlxcpld.c)

On 09/11/16 22:42, Stephen Rothwell wrote: > Hi all, > > Changes since 20160909: > on x86_64: ../drivers/leds/leds-mlxcpld.c: In function 'mlxcpld_led_bus_access_func': ../drivers/leds/leds-mlxcpld.c:253:3: error: implicit declaration of function 'outb' [-Werror=implicit-function-declaration]

linux-next: Tree for Sep 12

Hi all, Changes since 20160909: The arm64 tree gained a conflict against Linus' tree. The btrfs-kdave tree lost its build failure. The v4l-dvb tree gained a build failure for which I reverted a commit. The net-next tree gained a conflict against the net tree. The kbuild tree still had its

linux-next: Tree for Sep 12

Hi all, Changes since 20160909: The arm64 tree gained a conflict against Linus' tree. The btrfs-kdave tree lost its build failure. The v4l-dvb tree gained a build failure for which I reverted a commit. The net-next tree gained a conflict against the net tree. The kbuild tree still had its

linux-next: Tree for Sep 12

Hi all, Please do not add material for v4.4 until after v4.3-rc1 is out. Changes since 20150911: Dropped tree: akpm-current (build conflict) I used the h8300 tree from next-20150828 since the current tree has been rebased onto something very old :-( The drm-misc tree gained a conflict against

linux-next: Tree for Sep 12

Hi all, Please do not add material for v4.4 until after v4.3-rc1 is out. Changes since 20150911: Dropped tree: akpm-current (build conflict) I used the h8300 tree from next-20150828 since the current tree has been rebased onto something very old :-( The drm-misc tree gained a conflict against

Re: [Kernel.org Helpdesk #7062] AutoReply: Re: linux-next: Tree for Sep 12

Hi, On Sat, 13 Sep 2014 02:00:02 + "Kernel.org IT Helpdesk via RT" wrote: > > > Greetings, > > Your support ticket regarding: > "Re: linux-next: Tree for Sep 12", > has been entered in our ticket tracker. A summary of your ticket appears

Re: linux-next: Tree for Sep 12

Hi Randy, On Sat, 13 Sep 2014 11:59:50 +1000 Stephen Rothwell wrote: > > On Fri, 12 Sep 2014 10:39:19 -0700 Randy Dunlap wrote: > > > > On 09/12/14 00:38, Stephen Rothwell wrote: > > > > > > Changes since 20140911: > > > > >

Re: linux-next: Tree for Sep 12

Hi Randy, On Fri, 12 Sep 2014 10:39:19 -0700 Randy Dunlap wrote: > > On 09/12/14 00:38, Stephen Rothwell wrote: > > > > Changes since 20140911: > > > - > > > > I have created today's linux-next tree at > >

Re: linux-next: Tree for Sep 12

On 09/12/14 00:38, Stephen Rothwell wrote: > Hi all, > > Changes since 20140911: > - > > I have created today's linux-next tree at > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > (patches at

linux-next: Tree for Sep 12

Hi all, Changes since 20140911: The v4l-dvb tree still had its build failure so I used the version from next-20140908. The slave-dma tree gained a build faiure so I used the version from next-20140911. The drm tree still had its build failure for which I applied a merge fix patch. Non-merge

linux-next: Tree for Sep 12

Hi all, Changes since 20140911: The v4l-dvb tree still had its build failure so I used the version from next-20140908. The slave-dma tree gained a build faiure so I used the version from next-20140911. The drm tree still had its build failure for which I applied a merge fix patch. Non-merge

Re: linux-next: Tree for Sep 12

On 09/12/14 00:38, Stephen Rothwell wrote: Hi all, Changes since 20140911: - I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at

Re: linux-next: Tree for Sep 12

Hi Randy, On Fri, 12 Sep 2014 10:39:19 -0700 Randy Dunlap rdun...@infradead.org wrote: On 09/12/14 00:38, Stephen Rothwell wrote: Changes since 20140911: - I have created today's linux-next tree at

Re: linux-next: Tree for Sep 12

Hi Randy, On Sat, 13 Sep 2014 11:59:50 +1000 Stephen Rothwell s...@canb.auug.org.au wrote: On Fri, 12 Sep 2014 10:39:19 -0700 Randy Dunlap rdun...@infradead.org wrote: On 09/12/14 00:38, Stephen Rothwell wrote: Changes since 20140911:

Re: [Kernel.org Helpdesk #7062] AutoReply: Re: linux-next: Tree for Sep 12

Hi, On Sat, 13 Sep 2014 02:00:02 + Kernel.org IT Helpdesk via RT kernel-helpd...@rt.linuxfoundation.org wrote: Greetings, Your support ticket regarding: Re: linux-next: Tree for Sep 12, has been entered in our ticket tracker. A summary of your ticket appears below

Re: linux-next: Tree for Sep 12 (block/skd_main.c)

On 09/11/13 21:34, Stephen Rothwell wrote: > Hi all, > > Please do not add any code for v3.13 to your linux-next included branches > until after v3.12-rc1 is released. > > Changes since 20130911: > on i386 (32-bit): drivers/block/skd_main.c: In function 'skd_reg_write64':

Re: linux-next: Tree for Sep 12 (block/skd_main.c)

On 09/11/13 21:34, Stephen Rothwell wrote: Hi all, Please do not add any code for v3.13 to your linux-next included branches until after v3.12-rc1 is released. Changes since 20130911: on i386 (32-bit): drivers/block/skd_main.c: In function 'skd_reg_write64':

linux-next: Tree for Sep 12

Hi all, Please do not add any code for v3.13 to your linux-next included branches until after v3.12-rc1 is released. Changes since 20130911: The akpm tree gained a conflict against Linus' tree. I have created today's

linux-next: Tree for Sep 12

Hi all, Please do not add any code for v3.13 to your linux-next included branches until after v3.12-rc1 is released. Changes since 20130911: The akpm tree gained a conflict against Linus' tree. I have created today's