On 2020/10/31 0:55, Eric Biggers wrote:
On Fri, Oct 30, 2020 at 03:26:10PM +0800, Chao Yu wrote:
+
+struct f2fs_gc_range {
+ u32 sync;
+ u64 start;
+ u64 len;
+};
Userspace headers need to use __u32, __u64, etc. instead of u32, u64, etc.
Correct.
Did you try installing t
Acked-by: Peter Chen
For:
Documentation/ABI/testing/usb-charger-uevent
Peter
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
On Fri, 30 Oct 2020 at 01:41, Mauro Carvalho Chehab
wrote:
>
> There are some ABI documents that, while they don't generate
> any warnings, they have issues when parsed by get_abi.pl script
> on its output result.
>
> Address them, in order to provide a clean output.
>
> Acked-by: Jonathan Cameron
On Fri, Oct 30, 2020 at 03:26:10PM +0800, Chao Yu wrote:
> +
> +struct f2fs_gc_range {
> + u32 sync;
> + u64 start;
> + u64 len;
> +};
Userspace headers need to use __u32, __u64, etc. instead of u32, u64, etc.
Did you try installing this header, and including it in a userspace program
On 2020-10-30 20:30, Jaegeuk Kim wrote:
Hi Chao,
Can we make a documentation for this in f2fs.rst?
Jaegeuk,
Sure, let me work on this.
Thanks,
Thanks,
On 10/30, Chao Yu wrote:
Like other filesystem does, we introduce a new file f2fs.h in path of
include/uapi/linux/, and move f2fs-specif
Hi Chao,
Can we make a documentation for this in f2fs.rst?
Thanks,
On 10/30, Chao Yu wrote:
> Like other filesystem does, we introduce a new file f2fs.h in path of
> include/uapi/linux/, and move f2fs-specified ioctl interface definitions
> to that file, after then, in order to use those definit
On Fri, Oct 30, 2020 at 8:41 AM Mauro Carvalho Chehab
wrote:
>
> There are some ABI documents that, while they don't generate
> any warnings, they have issues when parsed by get_abi.pl script
> on its output result.
>
> Address them, in order to provide a clean output.
>
> Acked-by: Jonathan Camer
On Fri, 2020-10-30 at 17:06 +0800, Chao Yu wrote:
> On 2020/10/30 16:56, kitestramuort wrote:
>
>
> It doesn't print function name in callstack, could you check your
> linker option, I guess it needs to add -rdynamic option? not sure.
Apologies. The correct call trace and fsck follow. I just rea
On 10/30/20 7:40 AM, Mauro Carvalho Chehab wrote:
There are some ABI documents that, while they don't generate
any warnings, they have issues when parsed by get_abi.pl script
on its output result.
Address them, in order to provide a clean output.
Acked-by: Jonathan Cameron #for IIO
Reviewed-by
On 2020/10/30 16:56, kitestramuort wrote:
On Fri, 2020-10-30 at 09:50 +0800, Chao Yu wrote:
On 2020/10/30 0:40, kitestramuort wrote:
Hello,
the new rc is generating the error below multiple times a few
minutes
after boot.
Could you please try fsck --dry-run, and share the output?
What's yo
On Fri, 2020-10-30 at 09:50 +0800, Chao Yu wrote:
> On 2020/10/30 0:40, kitestramuort wrote:
> > Hello,
> > the new rc is generating the error below multiple times a few
> > minutes
> > after boot.
> >
>
> Could you please try fsck --dry-run, and share the output?
Info: Dry run
Info: Segments pe
On 2020-10-30 8:40 AM, Mauro Carvalho Chehab wrote:
> There are some ABI documents that, while they don't generate
> any warnings, they have issues when parsed by get_abi.pl script
> on its output result.
>
> Address them, in order to provide a clean output.
>
> Acked-by: Jonathan Cameron #for I
Like other filesystem does, we introduce a new file f2fs.h in path of
include/uapi/linux/, and move f2fs-specified ioctl interface definitions
to that file, after then, in order to use those definitions, userspace
developer only need to include the new header file rather than
copy & paste definitio
13 matches
Mail list logo
