Can you work with me?
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
From: Marco Ballesio
when interrupted by a signal, binder_wait_for_work currently returns
-ERESTARTSYS. This error code isn't propagated to user space, but a way
to handle interruption due to signals must be provided to code using
this API.
Replace this instance of -ERESTARTSYS with -EINTR, whic
From: Marco Ballesio
when interrupted by a signal, binder_wait_for_work currently returns
-ERESTARTSYS. This error code isn't propagated to user space, but a way
to handle interruption due to signals must be provided to code using
this API.
Replace this instance of -ERESTARTSYS with -EINTR, whic
From: Marco Ballesio
when interrupted by a signal, binder_wait_for_work currently returns
-ERESTARTSYS. This error code isn't propagated to user space, but a way
to handle interruption due to signals must be provided to code using
this API.
Replace this instance of -ERESTARTSYS with -EINTR, whic
HELLO,Offer for humanitarian work in your country
My name is Mrs. Lily Lyman from America, I read about you from a reliable web
site and i will love to employ you into a humanitarian work in your country,
Please reply with your private email address so that i will give you further
details
HELLO,
My name is Mrs. Jane from America, I read about you from a reliable web site
and i will love to employ you into humanitarian work in your country, I'm ready
to donate some money for you to carry out the work in your country. Please
reply with your private email address so that i
From: John Stultz
Update the driver to work with v4.9 kernels
Signed-off-by: John Stultz
Signed-off-by: Mauro Carvalho Chehab
---
drivers/staging/hikey9xx/gpu/dw_drm_dsi.c | 4 +-
drivers/staging/hikey9xx/gpu/kirin_dpe_reg.h | 1 +
drivers/staging/hikey9xx/gpu/kirin_drm_drv.c | 3
Do some cleanups at the mode validation code. Right now, there
is a known issue with this driver which makes it to set up
some invalid modes, depending on the display.
We don't know yet what the issue is, so, instead, let's add
a table with the modes which are known to work.
Signed-off
Currently, this driver OOPSes. It turns that this driver
needs to be updated in order to work with the current
iommu kAPI.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/staging/hikey9xx/hisi_smmu.h | 2 +
drivers/staging/hikey9xx/hisi_smmu_lpae.c | 81 ---
2 files
Hi Tobias,
On Thu, May 21, 2020 at 1:17 PM Tobias Baumann <017623705...@o2online.de> wrote:
[...]
>>> with my patch and oleg RC5 hotstart(shutdown now) do not work with my
>>> box ( wlan goes back to sleep mode always)
>>
>> I'm not sure what you mean he
wrote:
good morning
i got the new image from oleg(balbes150) 20200518 RC5 and some more
feedback
with my patch and oleg RC5 hotstart(shutdown now) do not work with my
box ( wlan goes back to sleep mode always)
I'm not sure what you mean here.
if you run "shutdown now" then the syst
Hi Tobias,
On Tue, May 19, 2020 at 8:21 AM Tobias Baumann <017623705...@o2online.de> wrote:
>
> good morning
>
> i got the new image from oleg(balbes150) 20200518 RC5 and some more
> feedback
>
> with my patch and oleg RC5 hotstart(shutdown now) do not work with m
good morning
i got the new image from oleg(balbes150) 20200518 RC5 and some more
feedback
with my patch and oleg RC5 hotstart(shutdown now) do not work with my
box ( wlan goes back to sleep mode always)
with my patch chance 1 of 5 till 1 of 3 that my wlan is up and not
sleep from cold
Hi Tobias,
On Mon, May 18, 2020 at 7:59 AM Tobias Baumann <017623705...@o2online.de> wrote:
>
> hi martin
>
> i activate your patch ; wlan works ; also with only edit GPIOX_11 wlan
> works
>
> its now GPIO-402 out high ACTIVE_LOW ( 3.3V on pin12)
great, thank you for doing the research!
did yo
hi martin
i activate your patch ; wlan works ; also with only edit GPIOX_11 wlan
works
its now GPIO-402 out high ACTIVE_LOW ( 3.3V on pin12)
i also attached the performance infos Wlan0->Router and RAM->SDHC
Am 18.05.2020 um 00:31 schrieb Martin Blumenstingl:
Hi Tobias,
On Sun, May 17,
Hi Tobias,
On Sun, May 17, 2020 at 11:05 PM Tobias Baumann
<017623705...@o2online.de> wrote:
>
> hi martin
>
> sorry for cc -problem it was my fault in thunderbird
>
> thanks for dtb file but this file has problem kernel stop with
>
> [6.122092] mmc0: new high speed SDIO card at address 0001
>
h many modules from Arduino sensor modules not
all datasheet are correct
ok i got into uboot env
i could not get GPIOA0 write because of unknowm pin number
GPIOAO_0 should work though (the underscore is important)
but GPIOX works
now my measurmant show that out high = signal high (3.3V) and o
s not
> all datasheet are correct
>
> ok i got into uboot env
>
> i could not get GPIOA0 write because of unknowm pin number
GPIOAO_0 should work though (the underscore is important)
> but GPIOX works
>
> now my measurmant show that out high = signal high (3.3V) and
Hi Tobias,
On Thu, May 7, 2020 at 10:57 AM Tobias Baumann <017623705...@o2online.de> wrote:
>
> Hello Community
>
> I was referred to you by Martin. I have an older Android TV box that
> runs for over 3 years with Armbian Linux (Debian Jessie Headless Kernel
> 3.10.99). I'm looking forward to the
Hello Community
I was referred to you by Martin. I have an older Android TV box that
runs for over 3 years with Armbian Linux (Debian Jessie Headless Kernel
3.10.99). I'm looking forward to the new kernels and I'm glad that older
hardware is still supported.
Together with Oleg(balbes150) and M
at either initializes or errors
out here, which simplifies the code enough for gcc to figure out
what is going on. The earlier partial workaround can be removed now,
as the new workaround is better.
Fixes: 890f27693f2a ("media: imx: work around false-positive warning")
Signed-off-by: Arnd
On 04/02, Alexandru Ardelean wrote:
> On Mon, Apr 1, 2019 at 7:13 PM Jonathan Cameron
> wrote:
> >
> > On Mon, 1 Apr 2019 11:25:29 -0300
> > Marcelo Schmitt wrote:
> >
> > > Hello,
> > >
> > > I was looking for some work on staging: iio:
On Mon, Apr 1, 2019 at 7:13 PM Jonathan Cameron
wrote:
>
> On Mon, 1 Apr 2019 11:25:29 -0300
> Marcelo Schmitt wrote:
>
> > Hello,
> >
> > I was looking for some work on staging: iio: ad9832 and made some
> > observations while reading the driver.
>
On Mon, 1 Apr 2019 11:25:29 -0300
Marcelo Schmitt wrote:
> Hello,
>
> I was looking for some work on staging: iio: ad9832 and made some
> observations while reading the driver.
>
> Apparently it had no devicetree documentation so I tried to elaborate
> one.
> It uses
Hello,
I was looking for some work on staging: iio: ad9832 and made some
observations while reading the driver.
Apparently it had no devicetree documentation so I tried to elaborate
one.
It uses a platform_data variable to load external clock
frequency (I tried to make it use linux's
Good Day,
Hope you are doing great Today.I have a proposed BUSINESS DEAL that
will benefit both parties. This is legitimate,legal and your
personality will not be compromised.Please Reply to me ONLY if you are
interested and consider your self capable for details.
Sincerely,
Peter OWEN
Good Day,
Hope you are doing great Today.I have a proposed BUSINESS DEAL that
will benefit both parties. This is legitimate,legal and your
personality will not be compromised.Please Reply to me ONLY if you are
interested and consider your self capable for details.
Sincerely,
Peter OWEN
From: Adham Abozaeid
Validate cfg parameters after being called by cfg80211 in set_wiphy_params
before scheduling the work executed in handle_cfg_param
Signed-off-by: Adham Abozaeid
---
drivers/staging/wilc1000/host_interface.c | 61 ++-
.../staging/wilc1000
On Thu, Nov 08, 2018 at 09:50:25PM +, adham.aboza...@microchip.com wrote:
> From: Adham Abozaeid
>
> From: Adham Abozaeid
Twice? Something went wrong on your side, for all of these patches :(
Please fix up and resend.
thanks,
greg k-h
___
deve
From: Adham Abozaeid
From: Adham Abozaeid
Validate cfg parameters after being called by cfg80211 in set_wiphy_params
before scheduling the work executed in handle_cfg_param
Signed-off-by: Adham Abozaeid
---
drivers/staging/wilc1000/host_interface.c | 61 ++-
.../staging
On 11/8/18 4:22 AM, Greg KH wrote:
> On Tue, Nov 06, 2018 at 12:01:18AM +, adham.aboza...@microchip.com wrote:
>> From: Adham Abozaeid
>>
>> Validate cfg parameters after being called by cfg80211 in set_wiphy_params
>> before scheduling the work executed in handle
On Tue, Nov 06, 2018 at 12:01:18AM +, adham.aboza...@microchip.com wrote:
> From: Adham Abozaeid
>
> Validate cfg parameters after being called by cfg80211 in set_wiphy_params
> before scheduling the work executed in handle_cfg_param
>
> Signed-off-by: Adham Abozaeid
Hi Adham,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v4.20-rc1 next-20181106]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.c
From: Adham Abozaeid
Validate cfg parameters after being called by cfg80211 in set_wiphy_params
before scheduling the work executed in handle_cfg_param
Signed-off-by: Adham Abozaeid
---
drivers/staging/wilc1000/host_interface.c | 61 ++-
.../staging/wilc1000
From: Adham Abozaeid
Validate cfg parameters after being called by cfg80211 in set_wiphy_params
before scheduling the work executed in handle_cfg_param
Signed-off-by: Adham Abozaeid
---
drivers/staging/wilc1000/host_interface.c | 61 ++-
.../staging/wilc1000
On 10/26/18 2:36 AM, Dan Carpenter wrote:
> On Thu, Oct 25, 2018 at 09:11:00PM +, adham.aboza...@microchip.com wrote:
>
> You'll need to resend these because your email from header is in the
> wrong format. Also there is a typo in the subject. s/stagign/staging/.
>
Apologies Dan for that! Wil
On Thu, Oct 25, 2018 at 09:11:00PM +, adham.aboza...@microchip.com wrote:
You'll need to resend these because your email from header is in the
wrong format. Also there is a typo in the subject. s/stagign/staging/.
regards,
dan carpenter
___
devel
Validate cfg parameters after being called by cfg80211 in set_wiphy_params
before scheduling the work executed in handle_cfg_param
Signed-off-by: Adham Abozaeid
---
drivers/staging/wilc1000/host_interface.c | 61 ++-
.../staging/wilc1000/wilc_wfi_cfgoperations.c | 50
Did you receive my email from last week?
We are a team to provide you different kind of image editing services.
Such as cutting out your photos or give clipping path.
It includes retouching if needed.
The editing mostly is used for
ecommerce products photos or portrait photos.
We can give you e
On Tue, Sep 18, 2018 at 07:44:26PM +0200, Hans de Goede wrote:
> Hi Greg,
>
> Here is a series of various cleanups and other prep. work for moving
> the vboxvideo driver over to atomic modesetting so that it can be moved
> out of staging.
Nice work, all now app
Hi Greg,
Here is a series of various cleanups and other prep. work for moving
the vboxvideo driver over to atomic modesetting so that it can be moved
out of staging.
Regards,
Hans
___
devel mailing list
de...@linuxdriverproject.org
http
Shooting pictures is easy. However,the most important part often involves
the editing part after the shooting.
For many professional photographers, post processing photo editing has
become a necessity.
They may have shot good pictures yes but they still need to make them
great. It is at this point
figure out
what is going on. The earlier partial workaround can be removed now,
as the new workaround is better.
Fixes: 890f27693f2a ("media: imx: work around false-positive warning")
Signed-off-by: Arnd Bergmann
---
drivers/staging/media/imx/imx-media-csi.c | 5 -
1 file chang
This patch removes the function wait_event_interruptible from the
work function to avoid waiting.
Signed-off-by: Christian Gromm
---
drivers/staging/most/i2c/i2c.c | 54 --
1 file changed, 21 insertions(+), 33 deletions(-)
diff --git a/drivers/staging
K_RETURN_ERROR firstly and finish the transaction immediately,
> jump out of the nest.
>
> 2) Client pick up the left binder work from thread->todo, using the
> same thread, do not need wake up other idle binder thread.
>
> 3) It works fine in the old binder version (before split
From: yuanhuihui
transaction consume mismatched binder work. as follow:
1) Client send transaction when left binder work in the thread->todo
list.
2) in kernel space, client consumed BC_TRANSACTION, and produced
BINDER_WORK_RETURN_ERROR into thread->todo list as target proc is dead
3)
This reverts commit 5a3e59ce3acf2f52c8b4a6fc656c3b1e4a329f06, because the
necessary changes were applied in the "staging: nvec: convert to use GPIO
descriptors" patch.
Signed-off-by: Marc Dietrich
---
drivers/staging/nvec/TODO | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/stagi
I wanted to follow up from last week.
We provide image editing like – photos cutting out and retouching.
We assure you the top quality.
We provide below image editing services :
Clipping path
Image cut out
Image shadow creation
Image masking
Photo retouching
Beauty retouching - (skin, face, body
On Thu, 19 Apr 2018 10:41:21 +0200
Linus Walleij wrote:
> To make sure that this driver does not leave staging before it
> is properly converted to use the new GPIO descriptor API,
> augment the TODO file with this work item.
>
Thanks to update the TODO required to be fixed befor
On Thu, 2018-04-19 at 10:41 +0200, Linus Walleij wrote:
> To make sure that these drivers do not leave staging before they
> are properly converted to use the new GPIO descriptor API,
> augment the TODO file with this work item.
Fine by me.
Acked-by: Andy Shevchenko
> Cc: Alan Cox
On Thu, Apr 19, 2018 at 10:41:15AM +0200, Linus Walleij wrote:
> To make sure that these drivers do not leave staging before they
> are properly converted to use the new GPIO descriptor API, and the
> GPIOLIB_IRQCHIP helper library, create the TODO file with these work
> items.
&g
Hi Linus,
Am Donnerstag, 19. April 2018, 10:41:19 CEST schrieb Linus Walleij:
> To make sure that this driver does not leave staging before it
> is properly converted to use the new GPIO descriptor API,
> augment the TODO file with this work item.
I just sent a patch to convert it. T
> To make sure that these drivers do not leave staging before they
> are properly converted to use the new GPIO descriptor API,
> augment the TODO file with this work item.
>
> Cc: Jonathan Cameron
> Signed-off-by: Linus Walleij
Acked-by: Jonathan Cameron
I hope I haven&#
To make sure that these drivers do not leave staging before they
are properly converted to use the new GPIO descriptor API, and the
GPIOLIB_IRQCHIP helper library, create the TODO file with these work
items.
Cc: Johan Hovold
Signed-off-by: Linus Walleij
---
I started some work in this area
To make sure that this driver does not leave staging before it
is properly converted to use the new GPIO descriptor API,
augment the TODO file with this work item.
Cc: Andres Salomon
Cc: Jens Frederich
Signed-off-by: Linus Walleij
---
drivers/staging/olpc_dcon/TODO | 4
1 file changed, 4
To make sure that this driver does not leave staging before it
is properly converted to use the new GPIO descriptor API,
augment the TODO file with this work item.
Cc: Johnny Kim
Cc: Nicolas Ferre
Signed-off-by: Linus Walleij
---
drivers/staging/wilc1000/TODO | 4
1 file changed, 4
To make sure that this driver does not leave staging before it
is properly converted to use the new GPIO descriptor API,
augment the TODO file with this work item.
Cc: Marc Dietrich
Signed-off-by: Linus Walleij
---
drivers/staging/nvec/TODO | 5 +
1 file changed, 5 insertions(+)
diff
To make sure that these drivers do not leave staging before they
are properly converted to use the new GPIO descriptor API, create
the TODO file with this work item.
Cc: Thomas Petazzoni
Cc: Noralf Tronnes
Signed-off-by: Linus Walleij
---
drivers/staging/fbtft/TODO | 4
1 file changed, 4
-specific VBUS GPIO to work with multiplatform
+* convert VBUS GPIO to use GPIO descriptors from
+ and stop using the old GPIO API
* DT bindings
* move driver into drivers/usb/gadget/
--
2.14.3
___
devel mailing list
de...@linuxdriverproject.org
http
To make sure that these drivers do not leave staging before they
are properly converted to use the new GPIO descriptor API,
augment the TODO file with this work item.
Cc: Alan Cox
Cc: Andy Shevchenko
Signed-off-by: Linus Walleij
---
I'm happy to help to move this forward, however Andy i
To make sure that these drivers do not leave staging before they
are properly converted to use the new GPIO descriptor API,
augment the TODO file with this work item.
Cc: Jonathan Cameron
Signed-off-by: Linus Walleij
---
drivers/staging/iio/TODO | 9 -
1 file changed, 8 insertions
We have got a team of professional to do image editing service.
We have 8 image editors and on daily basis 300 images can be processed,
Detail below:
Photo cut out;
Photo clipping path;
Photo masking
Photo shadow creation;
Photo color correction
Photo retouching;
Beauty Model retouching on skin,
> From: Dexuan Cui
> > From: Lorenzo Pieralisi
> > I need to know either what commit you are fixing (ie Fixes: tag - which
> > is preferrable) or you tell me which kernel versions we are targeting
> > for the stable backport.
> > Lorenzo
>
> Sorry. Here I was hesitant to add a "Fixes:" because t
> From: Lorenzo Pieralisi
> Sent: Thursday, March 15, 2018 10:02
> On Thu, Mar 15, 2018 at 02:20:53PM +, Dexuan Cui wrote:
> > When we hot-remove the device, we first receive a PCI_EJECT message and
> > then receive a PCI_BUS_RELATIONS message with bus_rel->device_count ==
> 0.
> >
> > The fir
On Thu, Mar 15, 2018 at 02:20:53PM +, Dexuan Cui wrote:
> When we hot-remove the device, we first receive a PCI_EJECT message and
> then receive a PCI_BUS_RELATIONS message with bus_rel->device_count == 0.
>
> The first message is offloaded to hv_eject_device_work(), and the second
> is offloa
If there is a pending work, we just need to add the new dr into
the dr_list.
Signed-off-by: Dexuan Cui
Reviewed-by: Michael Kelley
Acked-by: Haiyang Zhang
Cc: Vitaly Kuznetsov
Cc: Jack Morgenstein
Cc: Stephen Hemminger
Cc: K. Y. Srinivasan
---
drivers/pci/host/pci-hyperv.c | 15
When we hot-remove the device, we first receive a PCI_EJECT message and
then receive a PCI_BUS_RELATIONS message with bus_rel->device_count == 0.
The first message is offloaded to hv_eject_device_work(), and the second
is offloaded to pci_devices_present_work(). Both the paths can be running
list_
The IS_ERR()/PTR_ERR() combination confuses gcc to the point that it
cannot prove the upstream_ep variable to be initialized:
drivers/staging/media/imx/imx-media-csi.c: In function 'csi_link_validate':
drivers/staging/media/imx/imx-media-csi.c:1025:20: error: 'upstream_ep' may be
used uninitializ
.org; driverdev-devel@linuxdriverproject.org;
> Haiyang Zhang ; vkuzn...@redhat.com;
> marcelo.ce...@canonical.com; Michael Kelley (EOSG)
> ; Dexuan Cui ; Jack
> Morgenstein ; sta...@vger.kernel.org
> Subject: [PATCH v3 5/6] PCI: hv: hv_pci_devices_present(): only queue a new
> work wh
.org; driverdev-devel@linuxdriverproject.org;
> Haiyang Zhang ; vkuzn...@redhat.com;
> marcelo.ce...@canonical.com; Michael Kelley (EOSG)
> ; Dexuan Cui ; Jack
> Morgenstein ; sta...@vger.kernel.org
> Subject: [PATCH v3 3/6] PCI: hv: serialize the present/eject work items
>
> When we
kernel.org; driverdev-devel@linuxdriverproject.org;
> Haiyang Zhang
> ; vkuzn...@redhat.com; marcelo.ce...@canonical.com;
> Michael
> Kelley (EOSG) ; Dexuan Cui
> ; Jack
> Morgenstein ; sta...@vger.kernel.org
> Subject: [PATCH v3 3/6] PCI: hv: serialize the present/eject work it
kernel.org; driverdev-devel@linuxdriverproject.org;
> Haiyang Zhang
> ; vkuzn...@redhat.com; marcelo.ce...@canonical.com;
> Michael
> Kelley (EOSG) ; Dexuan Cui
> ; Jack
> Morgenstein ; sta...@vger.kernel.org
> Subject: [PATCH v3 5/6] PCI: hv: hv_pci_devices_present(): only qu
When we hot-remove the device, we first receive a PCI_EJECT message and
then receive a PCI_BUS_RELATIONS message with bus_rel->device_count == 0.
The first message is offloaded to hv_eject_device_work(), and the second
is offloaded to pci_devices_present_work(). Both the paths can be running
list_
If there is a pending work, we just need to add the new dr into
the dr_list.
This is suggested by Michael Kelley.
Signed-off-by: Dexuan Cui
Cc: Vitaly Kuznetsov
Cc: Jack Morgenstein
Cc: sta...@vger.kernel.org
Cc: Stephen Hemminger
Cc: K. Y. Srinivasan
Cc: Michael Kelley (EOSG)
---
drivers
> > + /*
> > +* If pending_dr is true, we have already queued a work,
> > +* which will see the new dr. Otherwise, we need to
> > +* queue a new work.
> > +*/
> > + pending_dr = !list_empty(&hbus->dr_list);
> > list_add_tail(&am
kernel.org; driverdev-devel@linuxdriverproject.org;
> Haiyang Zhang
> ; vkuzn...@redhat.com; marcelo.ce...@canonical.com;
> Michael
> Kelley (EOSG) ; Dexuan Cui
> ; Jack
> Morgenstein ; sta...@vger.kernel.org
> Subject: [PATCH v2 5/6] PCI: hv: hv_pci_devices_present(): only queue
When we hot-remove the device, we first receive a PCI_EJECT message and
then receive a PCI_BUS_RELATIONS message with bus_rel->device_count == 0.
The first message is offloaded to hv_eject_device_work(), and the second
is offloaded to pci_devices_present_work(). Both the paths can be running
list_
If there is a pending work, we just need to add the new dr into
the dr_list.
This is suggested by Michael Kelley.
Signed-off-by: Dexuan Cui
Cc: Vitaly Kuznetsov
Cc: Jack Morgenstein
Cc: sta...@vger.kernel.org
Cc: Stephen Hemminger
Cc: K. Y. Srinivasan
Cc: Michael Kelley (EOSG)
---
drivers
When we're in hv_eject_device_work(), IMO hpdev->state must be
hv_pcichild_ejecting, so I'm going to make a patch like this:
@@ -1867,10 +1867,7 @@ static void hv_eject_device_work(struct work_struct
*work)
hpdev = container_of(work, struct hv_pci_dev
kernel.org; driverdev-devel@linuxdriverproject.org;
> Haiyang Zhang
> ; o...@aepfle.de; a...@canonical.com;
> jasow...@redhat.com;
> vkuzn...@redhat.com; marcelo.ce...@canonical.com; Dexuan Cui
> ;
> Jack Morgenstein ; sta...@vger.kernel.org
> Subject: [PATCH 2/3] PCI: hv: serialize the
When we hot-remove the device, we first receive a PCI_EJECT message and
then receive a PCI_BUS_RELATIONS message with bus_rel->device_count == 0.
The first message is offloaded to hv_eject_device_work(), and the second
is offloaded to pci_devices_present_work(). Both the paths can be running
list_
Cathy,
> When running multipath on a VM if all available paths go down the
> driver can schedule large amounts of storvsc_remove_lun work items to
> the same lun. In response to the failing paths typically storvsc
> responds by taking host->scan_mutex and issuing a TUR per lun.
When running multipath on a VM if all available paths go down
the driver can schedule large amounts of storvsc_remove_lun
work items to the same lun. In response to the failing paths
typically storvsc responds by taking host->scan_mutex and issuing
a TUR per lun. If there has been heavy IO to
On 10/31/2017 08:24 AM, Martin K. Petersen wrote:
If you use alloc_ordered_workqueue directly instead of
create_singlethread_workqueue you can pass a format string and don't
need the separate allocation.
But I'm not sure if Tejun is fine with using __WQ_LEGACY directly..
The only thing that fla
>> If you use alloc_ordered_workqueue directly instead of
>> create_singlethread_workqueue you can pass a format string and don't
>> need the separate allocation.
>>
>> But I'm not sure if Tejun is fine with using __WQ_LEGACY directly..
>
> The only thing that flag does is exempting the workqueue
This patchset does some refactoring in the frame buffer area, in order
for it to be in line with firmware (MC) configuration.
Patches 1 - 2 do some label cleanup and move the buffer layout setup
to a dedicated function.
Patch 3 updates tx_data_offset - the offset for Tx frame buffers - to
not acc
This patchset does some refactoring in the frame buffer area, in order
for it to be in line with firmware (MC) configuration.
Patches 1 - 2 do some label cleanup and move the buffer layout setup
to a dedicated function.
Patch 3 updates tx_data_offset - the offset for Tx frame buffers - to
not acc
Hello,
On Thu, Oct 19, 2017 at 08:35:10AM -0700, Christoph Hellwig wrote:
> On Tue, Oct 17, 2017 at 01:35:21PM -0400, Cathy Avery wrote:
> > + /*
> > +* Set the error handler work queue.
> > +*/
> > + snprintf(host_dev->work_q_name
> On Tue, Oct 17, 2017 at 01:35:21PM -0400, Cathy Avery wrote:
> > + /*
> > +* Set the error handler work queue.
> > +*/
> > + snprintf(host_dev->work_q_name, sizeof(host_dev-
> >work_q_name),
> > +"storvsc_error_wq_%d"
On Tue, Oct 17, 2017 at 01:35:21PM -0400, Cathy Avery wrote:
> + /*
> + * Set the error handler work queue.
> + */
> + snprintf(host_dev->work_q_name, sizeof(host_dev->work_q_name),
> + "storvsc_error_wq_%d", host->host_no);
When running multipath on a VM if all available paths go down
the driver can schedule large amounts of storvsc_remove_lun
work items to the same lun. In response to the failing paths
typically storvsc responds by taking host->scan_mutex and issuing
a TUR per lun. If there has been heavy IO to
When running multipath on a VM if all available paths go down
the driver can schedule large amounts of storvsc_remove_lun
work items to the same lun. In response to the failing paths
typically storvsc responds by taking host->scan_mutex and issuing
a TUR per lun. If there has been heavy IO to
More cleanup work from Sunil and myself.
I've previously sent some of these as part of a larger patch set.
I've decided to split the patch set to smaller chunks to make it
more manageable.
This patch set applies on top of commit 28eb51f7468a
("staging:rtl8188eu:core Fix remove un
More cleanup work from Sunil and myself.
I've previously sent some of these as part of a larger patch set.
I've decided to split the patch set to smaller chunks to make it
more manageable.
This patch set applies on top of commit 28eb51f7468a
("staging:rtl8188eu:core Fix remove un
More cleanup work from Sunil and myself.
I've previously sent some of these as part of a larger patch set.
I've decided to split the patch set to smaller chunks to make it
more manageable.
This patch set applies on top of commit 28eb51f7468a
("staging:rtl8188eu:core Fix remove un
This driver supports multiple devices like mma8653, mma8652, mma8452, mma8453
and
fxls8471. Almost all these devices have more than one event. Current driver
design
hardcodes the event specific information, so only one event can be supported by
this
driver and current design doesn't have the fle
On Tue, Jul 18, 2017 at 1:08 PM, Laurentiu Tudor
wrote:
> On 07/17/2017 06:00 PM, Arnd Bergmann wrote:
>> Strictly speaking the __raw_writel() won't guarantee that the
>> data is written as a single word, the compiler might decide to
>> split it up into byte-sized writes if it believes the destin
On 07/17/2017 06:00 PM, Arnd Bergmann wrote:
> On Mon, Jul 17, 2017 at 4:27 PM, Laurentiu Tudor
> wrote:
>> Hi Arnd,
>>
>> On 07/17/2017 04:45 PM, Arnd Bergmann wrote:
>>> On Mon, Jul 17, 2017 at 3:26 PM, wrote:
From: Laurentiu Tudor
Split the 64-bit accesses in 32-bit accesses
Hi Robin,
On 07/17/2017 04:43 PM, Robin Murphy wrote:
> On 17/07/17 14:26, laurentiu.tu...@nxp.com wrote:
>> From: Laurentiu Tudor
>>
>> Split the 64-bit accesses in 32-bit accesses because there's no real
>> constrain in MC to do only atomic 64-bit. There's only one place
>> where ordering is im
On Mon, Jul 17, 2017 at 4:27 PM, Laurentiu Tudor
wrote:
> Hi Arnd,
>
> On 07/17/2017 04:45 PM, Arnd Bergmann wrote:
>> On Mon, Jul 17, 2017 at 3:26 PM, wrote:
>>> From: Laurentiu Tudor
>>>
>>> Split the 64-bit accesses in 32-bit accesses because there's no real
>>> constrain in MC to do only at
1 - 100 of 201 matches
Mail list logo
