On 09/13/2018 10:15 AM, Chao Yu wrote:
On 2018/9/12 13:10, Chengguang Xu wrote:
Define a dummpy function of erofs_build_fault_attr() when macro
CONFIG_EROFS_FAULT_INJECTION is disabled, so that we don't have to
check the macro in calling place. Based on above adjustment,
do proper code cleanup f
On 09/13/2018 10:04 AM, Chao Yu wrote:
On 2018/9/12 13:10, Chengguang Xu wrote:
Define a dummy function of time_to_inject(), so that we don't
have to check macro CONFIG_EROFS_FAULT_INJECTION in calling place.
Base on above adjustment, do proper code cleanup for erofs_kmalloc().
Signed-off-by: C
On 2018/9/12 13:10, Chengguang Xu wrote:
> Define a dummpy function of erofs_build_fault_attr() when macro
> CONFIG_EROFS_FAULT_INJECTION is disabled, so that we don't have to
> check the macro in calling place. Based on above adjustment,
> do proper code cleanup for option parsing of fault_injecti
On 2018/9/12 13:10, Chengguang Xu wrote:
> Define a dummy function of time_to_inject(), so that we don't
> have to check macro CONFIG_EROFS_FAULT_INJECTION in calling place.
> Base on above adjustment, do proper code cleanup for erofs_kmalloc().
>
> Signed-off-by: Chengguang Xu
> ---
> drivers/s
On Wed, Sep 12, 2018 at 4:07 PM Mauro Carvalho Chehab
wrote:
>
> Em Wed, 12 Sep 2018 15:26:48 -0500
> Rob Herring escreveu:
>
> > +Joe P
> >
> > On Wed, Sep 12, 2018 at 10:17 AM Mauro Carvalho Chehab
> > wrote:
> > >
> > > Em Tue, 28 Aug 2018 10:44:33 -0500
> > > Rob Herring escreveu:
> > >
> >
Em Wed, 12 Sep 2018 15:26:48 -0500
Rob Herring escreveu:
> +Joe P
>
> On Wed, Sep 12, 2018 at 10:17 AM Mauro Carvalho Chehab
> wrote:
> >
> > Em Tue, 28 Aug 2018 10:44:33 -0500
> > Rob Herring escreveu:
> >
> > > In preparation to remove the node name pointer from struct device_node,
> > > c
+Joe P
On Wed, Sep 12, 2018 at 10:17 AM Mauro Carvalho Chehab
wrote:
>
> Em Tue, 28 Aug 2018 10:44:33 -0500
> Rob Herring escreveu:
>
> > In preparation to remove the node name pointer from struct device_node,
> > convert printf users to use the %pOFn format specifier.
> >
> > Cc: Steve Longerbe
On Wed, Sep 12, 2018 at 05:08:52PM +0200, Arnd Bergmann wrote:
> The .ioctl and .compat_ioctl file operations have the same prototype so
> they can both point to the same function, which works great almost all
> the time when all the commands are compatible.
>
> One exception is the s390 architect
On Wed, Sep 12, 2018 at 05:01:03PM +0200, Arnd Bergmann wrote:
> Each of these drivers has a copy of the same trivial helper function to
> convert the pointer argument and then call the native ioctl handler.
>
> We now have a generic implementation of that, so use it.
>
> Signed-off-by: Arnd Berg
On Wed, Sep 12, 2018 at 5:33 PM Jason Gunthorpe wrote:
>
> On Wed, Sep 12, 2018 at 05:01:03PM +0200, Arnd Bergmann wrote:
> > Each of these drivers has a copy of the same trivial helper function to
> > convert the pointer argument and then call the native ioctl handler.
> >
> > We now have a gener
On Wed, Sep 12, 2018 at 5:08 PM, Arnd Bergmann wrote:
> The .ioctl and .compat_ioctl file operations have the same prototype so
> they can both point to the same function, which works great almost all
> the time when all the commands are compatible.
>
> One exception is the s390 architecture, wher
On Wed, Sep 12, 2018 at 05:08:52PM +0200, Arnd Bergmann wrote:
> The .ioctl and .compat_ioctl file operations have the same prototype so
> they can both point to the same function, which works great almost all
> the time when all the commands are compatible.
>
> One exception is the s390 architect
Em Wed, 12 Sep 2018 17:08:52 +0200
Arnd Bergmann escreveu:
> The .ioctl and .compat_ioctl file operations have the same prototype so
> they can both point to the same function, which works great almost all
> the time when all the commands are compatible.
>
> One exception is the s390 architectur
On Wed, Sep 12, 2018 at 05:01:03PM +0200, Arnd Bergmann wrote:
> Each of these drivers has a copy of the same trivial helper function to
> convert the pointer argument and then call the native ioctl handler.
>
> We now have a generic implementation of that, so use it.
>
> Signed-off-by: Arnd Berg
Em Tue, 28 Aug 2018 10:44:33 -0500
Rob Herring escreveu:
> In preparation to remove the node name pointer from struct device_node,
> convert printf users to use the %pOFn format specifier.
>
> Cc: Steve Longerbeam
> Cc: Philipp Zabel
> Cc: Mauro Carvalho Chehab
> Cc: Greg Kroah-Hartman
> Cc:
The .ioctl and .compat_ioctl file operations have the same prototype so
they can both point to the same function, which works great almost all
the time when all the commands are compatible.
One exception is the s390 architecture, where a compat pointer is only
31 bit wide, and converting it into a
Each of these drivers has a copy of the same trivial helper function to
convert the pointer argument and then call the native ioctl handler.
We now have a generic implementation of that, so use it.
Signed-off-by: Arnd Bergmann
---
drivers/char/ppdev.c | 12 +-
drivers/char/
On Tue, 4 Sep 2018 11:44:26 +0900
Jaejoong Kim wrote:
> Many drivers with tty use the tty_stand_install(). But, there is no
> need to handle the error, since it always returns 0.
And what happens if another change means it can fail again. It's just a
property of the current implementation that
On 09/12/2018 10:50 PM, Gao Xiang wrote:
On 2018/9/12 22:23, cgxu519 wrote:
On 09/12/2018 07:22 PM, Gao Xiang wrote:
Hi Chengguang,
On 2018/9/12 13:10, Chengguang Xu wrote:
Introduce a new helper __erofs_build_fault_attr() to handle set/clear
erofs_fault_info, we need this funciton for inter
On 2018/9/12 22:23, cgxu519 wrote:
> On 09/12/2018 07:22 PM, Gao Xiang wrote:
>> Hi Chengguang,
>>
>> On 2018/9/12 13:10, Chengguang Xu wrote:
>>> Introduce a new helper __erofs_build_fault_attr() to handle set/clear
>>> erofs_fault_info, we need this funciton for internal use case.
>>> for examp
On 09/12/2018 10:25 PM, Dan Carpenter wrote:
On Wed, Sep 12, 2018 at 10:05:26PM +0800, cgxu519 wrote:
On 09/12/2018 05:16 PM, Dan Carpenter wrote:
On Wed, Sep 12, 2018 at 01:10:31PM +0800, Chengguang Xu wrote:
Set fault rate to 0 is useless and confusable, so add check to
avoid it.
I would h
On Wed, Sep 12, 2018 at 10:05:26PM +0800, cgxu519 wrote:
> On 09/12/2018 05:16 PM, Dan Carpenter wrote:
> > On Wed, Sep 12, 2018 at 01:10:31PM +0800, Chengguang Xu wrote:
> > > Set fault rate to 0 is useless and confusable, so add check to
> > > avoid it.
> > >
> > I would have assumed setting rat
On 09/12/2018 07:22 PM, Gao Xiang wrote:
Hi Chengguang,
On 2018/9/12 13:10, Chengguang Xu wrote:
Introduce a new helper __erofs_build_fault_attr() to handle set/clear
erofs_fault_info, we need this funciton for internal use case.
for example, reset fault_injection option in remount.
Signed-off
On 09/12/2018 05:16 PM, Dan Carpenter wrote:
On Wed, Sep 12, 2018 at 01:10:31PM +0800, Chengguang Xu wrote:
Set fault rate to 0 is useless and confusable, so add check to
avoid it.
I would have assumed setting rate to zero just disabled it.
I think currently it is useless because we have not
Hi Sean:
Thanks for your review.
On 9/10/2018 10:21 PM, Sean Christopherson wrote:
> On Mon, 2018-09-10 at 08:38 +, Tianyu Lan wrote:
>> Add flush range call back in the kvm_x86_ops and platform can use it
>> to register its associated function. The parameter "kvm_tlb_range"
>> accepts
Hi Michael:
Thanks for your review.
On 9/12/2018 8:22 AM, Michael Kelley (EOSG) wrote:
> From: Tianyu Lan Sent: Monday, September 10, 2018 1:39 AM
>> +
>> +int hyperv_flush_guest_mapping_range(u64 as, struct kvm_tlb_range *range)
>
> I'm really concerned about defining the Hyper-V functi
Hi Chengguang,
On 2018/9/12 13:10, Chengguang Xu wrote:
> Introduce a new helper __erofs_build_fault_attr() to handle set/clear
> erofs_fault_info, we need this funciton for internal use case.
> for example, reset fault_injection option in remount.
>
> Signed-off-by: Chengguang Xu
> ---
> drive
On Wed, Sep 12, 2018 at 01:10:31PM +0800, Chengguang Xu wrote:
> Set fault rate to 0 is useless and confusable, so add check to
> avoid it.
>
I would have assumed setting rate to zero just disabled it.
regards,
dan carpenter
___
devel mailing list
de.
Hi Stephen,
On 2018/9/12 15:34, Stephen Rothwell wrote:
> Hi Chao,
>
> On Wed, 12 Sep 2018 15:19:16 +0800 Chao Yu wrote:
>>
>> To make sure, did -next tree enable erofs compiling now?
>
> Yes, from yesterday.
Great, thanks for your help. :)
>
>> Xiang has made two patches to fix integration
On Wed, Sep 12, 2018 at 09:54:51AM +0200, Hans de Goede wrote:
> Hi,
>
> On 11-09-18 20:46, Greg Kroah-Hartman wrote:
> > On Tue, Sep 11, 2018 at 09:15:41AM +0200, Hans de Goede wrote:
> > > The default settings for Linux vms created in VirtualBox allocate only
> > > 16M of videomem. When running
On 09/12/2018 09:23 AM, Maxime Ripard wrote:
> On Tue, Sep 11, 2018 at 12:46:25PM -0300, Mauro Carvalho Chehab wrote:
>> Em Fri, 7 Sep 2018 00:24:38 +0200
>> Paul Kocialkowski escreveu:
>>
>>> From: Paul Kocialkowski
>>>
>>> This introduces the Cedrus VPU driver that supports the VPU found in
>>
Hi,
On 11-09-18 20:46, Greg Kroah-Hartman wrote:
On Tue, Sep 11, 2018 at 09:15:41AM +0200, Hans de Goede wrote:
The default settings for Linux vms created in VirtualBox allocate only
16M of videomem. When running fullscreen on a 1920x1080 (or bigger) monitor
this is not a lot.
When using GNOME
On 11.09.2018 20:38, Colin King wrote:
> From: Colin Ian King
>
> Currently the pointer wilc is being null checked several times
> and yet not checked for the final workqueue flush and destroy
> (which can lead to a null pointer dereference if wilc is null);
> these missing null checks were ov
Hi Chao,
On Wed, 12 Sep 2018 15:19:16 +0800 Chao Yu wrote:
>
> To make sure, did -next tree enable erofs compiling now?
Yes, from yesterday.
> Xiang has made two patches to fix integration issue with other vfs changes,
> and Greg and David have already picked them in their tree.
>
> staging: e
On Tue, Sep 11, 2018 at 12:46:25PM -0300, Mauro Carvalho Chehab wrote:
> Em Fri, 7 Sep 2018 00:24:38 +0200
> Paul Kocialkowski escreveu:
>
> > From: Paul Kocialkowski
> >
> > This introduces the Cedrus VPU driver that supports the VPU found in
> > Allwinner SoCs, also known as Video Engine. It
Hi Stephen,
To make sure, did -next tree enable erofs compiling now?
Xiang has made two patches to fix integration issue with other vfs changes,
and Greg and David have already picked them in their tree.
staging: erofs: rename superblock flags (MS_xyz -> SB_xyz)
staging: erofs: update .mount and
On Fri, Sep 07, 2018 at 12:34:19PM +0900, Minchan Kim wrote:
> Thanks, Martijn,
>
> Greg, could you have a look to pick up?
Now queued up, thanks.
greg k-h
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mail
37 matches
Mail list logo
