Re: arch/mips/include/asm/addrspace.h:88:37: warning: passing argument 1 of 'kfree' makes pointer from integer without a cast

2020-10-16 Thread Valentin Vidić
On Fri, Oct 16, 2020 at 08:02:51AM -0700, Jakub Kicinski wrote: > Valentin, looks like we're missing a cast to (void *) or some other > pointer.. Would you mind sending a fix? You can find cross compilers > to test it here, cause this probably only builds for MIPS: > >

Re: [PATCH] net: korina: free array used for rx/tx descriptors

2020-10-11 Thread Valentin Vidić
On Sun, Oct 11, 2020 at 02:37:33PM -0400, Willem de Bruijn wrote: > Slightly off-topic, but I don't fully fathom what goes on with this > pointer straight after the initial kmalloc. > > lp->td_ring = (struct dma_desc *)KSEG1ADDR(lp->td_ring); KSEG1ADDR should rewrite the memory address

Re: [PATCH] s390/sclp_vt220: Fix console name to match device

2020-05-20 Thread Valentin Vidić
On Wed, May 20, 2020 at 09:14:23AM +0200, Christian Borntraeger wrote: > My point was more that a similar issue should happen when installing in LPAR. > LPAR > uses the line mode style console which is ttyS0 for the console but > sclp_line0 for the > tty. How does the debian installer handle

Re: [PATCH] s390/sclp_vt220: Fix console name to match device

2020-05-20 Thread Valentin Vidić
On Wed, May 20, 2020 at 07:25:06AM +0200, Christian Borntraeger wrote: > This is not as simple. ttyS1 is the the console name and ttysclp0 is the tty > name. > This has mostly historic reasons and it obviously causes problems. > But there is documentation out that that actually describes the use

Re: [PATCH v2 2/3] staging: exfat: drop unused field access_time_ms

2019-09-09 Thread Valentin Vidić
On Sun, Sep 08, 2019 at 08:19:21PM -0400, Valdis Klētnieks wrote: > In that case, rather than removing it, shouldn't we be *adding* > code to properly set it instead? Right, setting the UtcOffset fields to 0 is the first step marking them as invalid for now. This is also why access_time_ms did

Re: [PATCH v3 2/4] staging: exfat: drop duplicate date_time_t struct

2019-09-08 Thread Valentin Vidić
On Sun, Sep 08, 2019 at 07:50:31PM +0100, Greg Kroah-Hartman wrote: > Wait, how are these "duplicate"? The fields are in different order, > don't these refer to things on-disk? On-disk combines the values from these structures in a different form: offset bits DoubleSeconds 0 5

Re: [PATCH v3 2/4] staging: exfat: drop duplicate date_time_t struct

2019-09-08 Thread Valentin Vidić
On Sun, Sep 08, 2019 at 07:54:24PM +0100, Greg Kroah-Hartman wrote: > On Sun, Sep 08, 2019 at 05:35:37PM +, Valentin Vidic wrote: > > +struct timestamp_t { > > + u16 millisec; /* 0 ~ 999 */ > > You added this field to this structure, why? You did not document that > in

Re: [PATCH v2 3/3] staging: exfat: add millisecond support

2019-09-08 Thread Valentin Vidić
On Sun, Sep 08, 2019 at 05:40:40PM +0100, Greg Kroah-Hartman wrote: > On Sun, Sep 08, 2019 at 04:10:15PM +, Valentin Vidic wrote: > > void fat_set_entry_time(struct dentry_t *p_entry, struct timestamp_t *tp, > > u8 mode) > > { > > + u8 ms; > > u16 t, d; > >

Re: [PATCH] staging: exfat: add millisecond support

2019-09-08 Thread Valentin Vidić
On Sun, Sep 08, 2019 at 02:03:37PM +0100, Greg Kroah-Hartman wrote: > Please run checkpatch on your patches so that we don't have to go and > fix up those issues later on. Strange, it did not report anything for me: total: 0 errors, 0 warnings, 0 checks, 439 lines checked

Re: [PATCH] staging: exfat: cleanup braces for if/else statements

2019-09-04 Thread Valentin Vidić
On Wed, Sep 04, 2019 at 09:38:55AM +, David Laight wrote: > From: Valentin Vidic > > Sent: 03 September 2019 19:12 > > On Tue, Sep 03, 2019 at 06:32:49PM +0100, Al Viro wrote: > > > On Tue, Sep 03, 2019 at 06:47:32PM +0200, Valentin Vidic wrote: > > > > + } else if (uni

Re: [PATCH] staging: exfat: cleanup braces for if/else statements

2019-09-03 Thread Valentin Vidić
On Tue, Sep 03, 2019 at 06:32:49PM +0100, Al Viro wrote: > On Tue, Sep 03, 2019 at 06:47:32PM +0200, Valentin Vidic wrote: > > + } else if (uni == 0x) { > > skip = TRUE; > > While we are at it, could you get rid of that 'TRUE' macro? Sure, but