In existing code, this tree of resources is created
in single-threaded code and never modified after it is
created, and thus needs no locking. This patch introduces
a semaphore for tree access, as other patches in this
series introduce run-time modifications of this resource
tree which can happen
This patch changes vmbus_allocate_mmio() and vmbus_free_mmio() so
that when child paravirtual devices allocate memory-mapped I/O
space, they allocate it privately from a resource tree pointed
at by hyperv_mmio and also by the public resource tree
iomem_resource. This allows the region to be marked
This patch introduces a function that reverses everything
done by vmbus_allocate_mmio(). Existing code just called
release_mem_region(). Future patches in this series
require a more complex sequence of actions, so this function
is introduced to wrap those actions.
Signed-off-by: Jake Oshins
---
Later in the boot sequence, we need to figure out which memory
ranges can be given out to various paravirtual drivers. The
hyperv_fb driver should, ideally, be placed right on top of
the frame buffer, without some other device getting plopped on
top of this range in the meantime. Recording this n
This series differs from v3 in that it folds in a patch suggested by
the kbuild test robot, substituting resource_size() for directly
calculating the size.
Hyper-V VMs expose paravirtual drivers through a mechanism called
VMBus, which is managed by hv_vmbus.ko. For each parvirtual service
instanc
Simplify the logic that picks MMIO ranges by pulling out the
logic related to trying to lay frame buffer claim on top of where
the firmware placed the frame buffer.
Signed-off-by: Jake Oshins
---
drivers/hv/vmbus_drv.c | 80 ++
1 file changed, 35 i
This patch modifies all the callers of vmbus_mmio_allocate()
to call vmbus_mmio_free() instead of release_mem_region().
Signed-off-by: Jake Oshins
---
drivers/pci/host/pci-hyperv.c | 14 +++---
drivers/video/fbdev/hyperv_fb.c | 4 ++--
2 files changed, 9 insertions(+), 9 deletions(-)
A patch later in this series allocates child nodes
in this resource tree. For that to work, this tree
needs to be sorted in ascending order.
Signed-off-by: Jake Oshins
---
drivers/hv/vmbus_drv.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/hv/vmbus_drv.c b/drive
drivers/hv/vmbus_drv.c:1099:15-18: ERROR: Missing resource_size with fb_mmio
Use resource_size function on resource object
instead of explicit computation.
Generated by: scripts/coccinelle/api/resource_size.cocci
CC: Jake Oshins
Signed-off-by: Fengguang Wu
---
vmbus_drv.c |2 +-
1 fil
Hi Jake,
[auto build test WARNING on v4.6-rc1]
[also build test WARNING on next-20160401]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Jake-Oshins/drivers-hv-Ensure-that-bridge-windows-don
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, March 31, 2016 5:01 PM
> To: KY Srinivasan
> Cc: linux-ker...@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com;
> jasow...@redhat.com
> Subje
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, March 31, 2016 5:00 PM
> To: KY Srinivasan
> Cc: linux-ker...@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com;
> jasow...@redhat.com; sta...
A patch later in this series allocates child nodes
in this resource tree. For that to work, this tree
needs to be sorted in ascending order.
Signed-off-by: Jake Oshins
---
drivers/hv/vmbus_drv.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/hv/vmbus_drv.c b/drive
This patch modifies all the callers of vmbus_mmio_allocate()
to call vmbus_mmio_free() instead of release_mem_region().
Signed-off-by: Jake Oshins
---
drivers/pci/host/pci-hyperv.c | 14 +++---
drivers/video/fbdev/hyperv_fb.c | 4 ++--
2 files changed, 9 insertions(+), 9 deletions(-)
This patch changes vmbus_allocate_mmio() and vmbus_free_mmio() so
that when child paravirtual devices allocate memory-mapped I/O
space, they allocate it privately from a resource tree pointed
at by hyperv_mmio and also by the public resource tree
iomem_resource. This allows the region to be marked
This patch introduces a function that reverses everything
done by vmbus_allocate_mmio(). Existing code just called
release_mem_region(). Future patches in this series
require a more complex sequence of actions, so this function
is introduced to wrap those actions.
Signed-off-by: Jake Oshins
---
In existing code, this tree of resources is created
in single-threaded code and never modified after it is
created, and thus needs no locking. This patch introduces
a semaphore for tree access, as other patches in this
series introduce run-time modifications of this resource
tree which can happen
Simplify the logic that picks MMIO ranges by pulling out the
logic related to trying to lay frame buffer claim on top of where
the firmware placed the frame buffer.
Signed-off-by: Jake Oshins
---
drivers/hv/vmbus_drv.c | 80 ++
1 file changed, 35 i
Later in the boot sequence, we need to figure out which memory
ranges can be given out to various paravirtual drivers. The
hyperv_fb driver should, ideally, be placed right on top of
the frame buffer, without some other device getting plopped on
top of this range in the meantime. Recording this n
This series differs from v2 in that it reserves not only the memory
in use as the UEFI frame buffer but also the off-screen memory, so
that PCI devices can't reserve that, either.
Hyper-V VMs expose paravirtual drivers through a mechanism called
VMBus, which is managed by hv_vmbus.ko. For each pa
Just use struct lnet_msg instead.
Signed-off-by: Joe Perches
---
.../staging/lustre/include/linux/lnet/lib-lnet.h | 38 ++--
.../staging/lustre/include/linux/lnet/lib-types.h | 10 +--
.../staging/lustre/lnet/klnds/o2iblnd/o2iblnd.h| 6 +-
.../staging/lustre/lnet/klnds/o2iblnd/o2
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, March 31, 2016 5:00 PM
> To: KY Srinivasan
> Cc: linux-ker...@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com;
> jasow...@redhat.com; sta...
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, March 31, 2016 1:19 PM
> To: Vitaly Kuznetsov
> Cc: KY Srinivasan ; o...@aepfle.de;
> jasow...@redhat.com; linux-ker...@vger.kernel.org; a...@canonical.com;
> de...@linuxdriverproject.org
> Subject
> > I know James is working on cleaning up LNet, but I don't know if he has
> > anything this would be conflicting at this moment or not.
> >
> > Thanks for the patches. I wonder if you are generating them automatically?
> > Because it would be great if it also fixes the alignment issues
>
> It'
> > I know James is working on cleaning up LNet, but I don't know if he has
> > anything this would be conflicting at this moment or not.
> >
> > Thanks for the patches. I wonder if you are generating them automatically?
> > Because it would be great if it also fixes the alignment issues
>
> It'
> > I know James is working on cleaning up LNet, but I don't know if he has
> > anything this would be conflicting at this moment or not.
> >
> > Thanks for the patches. I wonder if you are generating them automatically?
> > Because it would be great if it also fixes the alignment issues
>
> It'
> > I know James is working on cleaning up LNet, but I don't know if he has
> > anything this would be conflicting at this moment or not.
> >
> > Thanks for the patches. I wonder if you are generating them automatically?
> > Because it would be great if it also fixes the alignment issues
>
> It'
> > I know James is working on cleaning up LNet, but I don't know if he has
> > anything this would be conflicting at this moment or not.
> >
> > Thanks for the patches. I wonder if you are generating them automatically?
> > Because it would be great if it also fixes the alignment issues
>
> It'
Sorry I was seeing a email error that I thought was preventing my email
being sent out. That is not the case.
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
On Fri, 2016-04-01 at 19:14 +, Drokin, Oleg wrote:
> On Apr 1, 2016, at 2:44 PM, Joe Perches wrote:
> > On Fri, 2016-04-01 at 14:23 +, Drokin, Oleg wrote:
> > > On Apr 1, 2016, at 9:02 AM, Joe Perches wrote:
> > > > Question about removing lustre typedefs.
> > > >
> > > > Various bits of l
On Fri, 2016-04-01 at 14:23 +, Drokin, Oleg wrote:
> On Apr 1, 2016, at 9:02 AM, Joe Perches wrote:
> >
> > Question about removing lustre typedefs.
> >
> > Various bits of lustre code use a mix of struct foo and foo_t.
> >
> > When would be an appropriate time to submit patches similar to
>
From: Oleg Drokin
This fixes all checkpatch form of this from the Lustre tree:
CHECK: braces {} should be used on all arms of this statement
Signed-off-by: Oleg Drokin
---
drivers/staging/lustre/lustre/fld/fld_cache.c| 3 ++-
.../lustre/lustre/include/lustre/lustre_idl.h| 3 +
From: Oleg Drokin
Directly use enum ldlm_policy_res everywhere.
Signed-off-by: Oleg Drokin
---
drivers/staging/lustre/lustre/ldlm/ldlm_internal.h | 2 -
drivers/staging/lustre/lustre/ldlm/ldlm_request.c | 49 +++---
2 files changed, 24 insertions(+), 27 deletions(-)
diff --g
From: Oleg Drokin
This patch fixes all checkpatch occurences of
CHECK: Blank lines aren't necessary after an open brace '{'
CHECK: Blank lines aren't necessary before a close brace '}'
in Lustre code.
Signed-off-by: Oleg Drokin
---
drivers/staging/lustre/lustre/fld/fld_request.c | 1 -
dri
From: Oleg Drokin
More of the checkpatch warning fixes.
Oleg Drokin (3):
staging/lustre: Fix braces {} style
staging/lustre: Fix blank line after/before {/} style
staging/lustre: Get rid of ldlm_policy_res_t typedef
drivers/staging/lustre/lustre/fld/fld_cache.c | 3 +-
drivers/stag
On Apr 1, 2016, at 2:44 PM, Joe Perches wrote:
> On Fri, 2016-04-01 at 14:23 +, Drokin, Oleg wrote:
>> On Apr 1, 2016, at 9:02 AM, Joe Perches wrote:
>>>
>>> Question about removing lustre typedefs.
>>>
>>> Various bits of lustre code use a mix of struct foo and foo_t.
>>>
>>> When would b
On Fri, 2016-04-01 at 15:58 +, Simmons, James A. wrote:
> > When would be an appropriate time to submit patches similar to
> > below that individually remove various typedefs from lustre code?
> >
> > These are pretty trivial to produce and verify so there's no
> > particular hurry to do them
Two instances are moved to the new claim/release API:
In the first instance, the driver was using mlock followed by
iio_buffer_enabled(). Replace that code with the new API to guarantee
the device stays in direct mode. There is no change in driver behavior.
In the second instance, the driver was
On 2016-03-30 09:15, Boris Brezillon wrote:
> Implementing the mtd_ooblayout_ops interface is the new way of exposing
> ECC/OOB layout to MTD users.
I think I sent this already in the last revision:
Tested-by: Stefan Agner
Acked-by: Stefan Agner
--
Stefan
>
> Signed-off-by: Boris Brezillon
>Question about removing lustre typedefs.
>
>Various bits of lustre code use a mix of struct foo and foo_t.
>
>When would be an appropriate time to submit patches similar to
>below that individually remove various typedefs from lustre code?
>
>These are pretty trivial to produce and verify so there
On Apr 1, 2016, at 9:02 AM, Joe Perches wrote:
> Question about removing lustre typedefs.
>
> Various bits of lustre code use a mix of struct foo and foo_t.
>
> When would be an appropriate time to submit patches similar to
> below that individually remove various typedefs from lustre code?
I
Question about removing lustre typedefs.
Various bits of lustre code use a mix of struct foo and foo_t.
When would be an appropriate time to submit patches similar to
below that individually remove various typedefs from lustre code?
These are pretty trivial to produce and verify so there's no
pa
Just use struct lnet_peer instead.
Signed-off-by: Joe Perches
---
.../staging/lustre/include/linux/lnet/lib-lnet.h | 18 ++---
.../staging/lustre/include/linux/lnet/lib-types.h | 6 ++---
drivers/staging/lustre/lnet/lnet/lib-move.c| 20 +++
drivers/staging/lustre/
Just use struct lnet_lnd instead.
Signed-off-by: Joe Perches
---
drivers/staging/lustre/include/linux/lnet/lib-lnet.h | 6 +++---
drivers/staging/lustre/include/linux/lnet/lib-types.h | 6 +++---
drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c | 4 ++--
drivers/staging/lustre/lnet/klnd
This patch is adds a check routine when performed del_key().
We was find this situation while test the 'rmmod sdio'.
That is received inform a .del_key cmd from cfg80211.
If is not exist wep keys, must be ignore a wilc_remove_wep_key() function.
Thus, adds a check routine that key length of wep.
S
This patch add set to null after release firmware.
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/linux_wlan.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/wilc1000/linux_wlan.c
b/drivers/staging/wilc1000/linux_wlan.c
index 47c0132..48bbfa2 100644
This patch is adds a cfg80211_disconnected() when connection is lost already.
We was find this situation while test the 'rmmod sdio'.
SDIO remove function are include both remove mac_close and unregister
net_device.
That is received one more a disconnect cmd from cfg80211.
Driver was already perfo
This patch replaces a semaphore(txq_thread_started) with a completion.
Struct semaphore txq_thread_started is used to signal completion of txq thread.
It is better to use completion than semaphore for this case.
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/linux_wlan.c | 10 +-
This patch changes logic when happened mq_send fail.
The check as a result value that mq_send fail.
But, regardless of the result value then perform a semaphore up.
That is an occur that semaphore locking.
Add to 'else' routine and move to 'else' position a semaphore up.
Signed-off-by: Leo Kim
--
This patch removes unnecessary test code that mac address hardcoding setting.
This test code is support to old firmware.
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/linux_wlan.c | 9 -
1 file changed, 9 deletions(-)
diff --git a/drivers/staging/wilc1000/linux_wlan.c
b/drivers/s
This patch removes del_timer_sync(&periodic_rssi) which was
already performed this action.
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/host_interface.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/wilc1000/host_interface.c
b/drivers/staging/wilc1000/host_interface.
fix checkpatch.pl warning about 'Avoid CamelCase'
Signed-off-by: Daeseok Youn
---
drivers/staging/dgnc/dgnc_tty.c | 2 +-
drivers/staging/dgnc/digi.h | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_tty.c b/drivers/staging/dgnc/dgnc_tty.c
ind
The "ch->ch_bd" is already assined to "bd" but this is only
for checking null or MAGIC number.
in the dgnc_tty_ioctl function, bd can be used for referencing
to board_ops structure.
Signed-off-by: Daeseok Youn
---
drivers/staging/dgnc/dgnc_tty.c | 37 -
1 file
53 matches
Mail list logo
