This patch fixes following coding style warning for reported by
check patch scrpit:
- Block comments use a trailing */ on a separate line
Signed-off-by: Bijosh Thykkoottathil
---
drivers/staging/iio/light/tsl2583.c | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff
The following changes since commit 388f7b1d6e8ca06762e2454d28d6c3c55ad0fe95:
Linux 4.5-rc3 (2016-02-07 15:38:30 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/
tags/staging-4.5-rc6
for you to fetch changes up to 7a64cd887fdb9
On Sat, 2016-02-27 at 10:28 -0800, Edward Lipinsky wrote:
> This patch fixes the checkpatch.pl warning:
> WARNING: line over 80 characters
[]
> diff --git a/drivers/staging/rtl8723au/core/rtw_ap.c
> b/drivers/staging/rtl8723au/core/rtw_ap.c
[]
> @@ -1834,7 +1834,8 @@ void stop_ap_mode23a(struct rt
This patch fixes the checkpatch.pl warning:
WARNING: line over 80 characters
Signed-off-by: Edward Lipinsky
---
drivers/staging/rtl8723au/core/rtw_ap.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8723au/core/rtw_ap.c
b/drivers/staging/rtl8723au/c
With conccurency managed workqueues, use of dedicated workqueues can
be replaced by system_wq. Drop cvm_oct_poll_queue by using system_wq.
There are multiple work items per cvm_oct_poll_queue (viz.
cvm_oct_rx_refill_work, port_periodic_work) and different
cvm_oct_poll_queues need not be be ordered
Hi Emil,
2016-02-27 Emil Velikov :
> Hi Gustavo,
>
> On 26 February 2016 at 18:31, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > Play safe and add flags member to all structs. So we don't need to
> > break API or create new IOCTL in the future if new features that requires
> > flags
Hi Emil,
2016-02-27 Emil Velikov :
> Hi Gustavo,
>
> On 26 February 2016 at 21:00, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > Change SYNC_IOC_FILE_INFO behaviour to avoid future API breaks and
> > optimize buffer allocation. In the new approach the ioctl needs to be called
> > tw
We may choose to load the module without the hardware present. That will
register the pci driver but since probe will not succeed so
dgnc_NumBoards will be 0. Now if we unload the module then the pci
driver stays registered as dgnc_NumBoards is 0. And if we try to load
the module again it fails wit
dgnc_cleanup_module() was called when the module unloaded to do a total
cleanup and it was also called if pci_register_driver() fails. But
dgnc_cleanup_module() will try dgnc_remove_driver_sysfiles() but the
sysfiles will be created only if pci_register_driver() succeeds.
So if pci_register_driver(
If pci_register_driver() fails then dgnc_NumBoards can never be more
than zero. dgnc_NumBoards is incremented only at the end of a successful
probe. And moreover if the pci driver has failed to register then we
never need to unregister it. Lets just print the warning, perform the
cleanup and exit w
If pci_enable_device() fails then we can return directly.
Signed-off-by: Sudip Mukherjee
---
I saw there is some pending dgnc patch in outreachy, so this series
might not apply. This series is based on staging-testing.
I will resend v2 if it fails.
drivers/staging/dgnc/dgnc_driver.c | 14 +
If we throw away the very last item on the list, then we could end up
with a use after free of "dr".
Fixes: 15ca17645f19 ('PCI: hv: Add paravirtual PCI front-end for Microsoft
Hyper-V VMs')
Signed-off-by: Dan Carpenter
diff --git a/drivers/pci/host/pci-hyperv.c b/drivers/pci/host/pci-hyperv.c
i
12 matches
Mail list logo