[PATCH 25/27] staging: lustre: check wr_id returned by ib_poll_cq

From: Liang Zhen If ib_poll_cq returned +ve without initialising ib_wc::wr_id (bug in driver), then o2iblnd will run into unpredictable situation because ib_wc::wr_id may refer to stale tx/rx pointer in stack. It indicates bug in HCA driver if this happened, ko2iblnd should output console error

[PATCH 27/27] staging: lustre: do less intense allocating retry for ko2iblnd

From: Liang Zhen ko2iblnd may retry too frequent for growing pools, all schedulers are spinning if another thread is in progress of allocating a new pool and can't finish right away because of high system load. Signed-off-by: Liang Zhen Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7054

[PATCH] staging: lustre: Support different ko2iblnd configs between systems

From: Jeremy Filizetti This patch adds suppoort for ko2iblnd to have different values for peer_credits and map_on_demand between systems. Signed-off-by: Jeremy Filizetti Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3322

[PATCH 18/27] staging: lustre: make o2iblnd_cb.c local functions static

From: Frank Zago This reduces the code size by about 1KiB. Signed-off-by: Frank Zago Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-5396 Reviewed-on: http://review.whamcloud.com/11256 Reviewed-by: Patrick Farrell Reviewed-by: John L. Hammond

[PATCH 24/27] staging: lustre: Change connect peer failed cleanup order

From: Doug Oucharek A race condition has been found where connd is cleaning up failed connections, the peer ref counter goes to zero, but we stil have a connecting counter > 0. One possible race is when we are retrying a connection by calling kiblnd_connect_peer()

[PATCH] staging: lustre: Support different ko2iblnd configs between systems

From: Jeremy Filizetti This patch adds suppoort for ko2iblnd to have different values for peer_credits and map_on_demand between systems. Signed-off-by: Jeremy Filizetti Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3322 Reviewed-on: http://review.whamcloud.com/11794 Reviewed-by: Amir

[PATCH 24/27] staging: lustre: Change connect peer failed cleanup order

From: Doug Oucharek A race condition has been found where connd is cleaning up failed connections, the peer ref counter goes to zero, but we stil have a connecting counter > 0. One possible race is when we are retrying a connection by calling kiblnd_connect_peer() which itself fails and

[PATCH 18/27] staging: lustre: make o2iblnd_cb.c local functions static

From: Frank Zago This reduces the code size by about 1KiB. Signed-off-by: Frank Zago Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-5396 Reviewed-on: http://review.whamcloud.com/11256 Reviewed-by: Patrick Farrell Reviewed-by: John L. Hammond Reviewed-by: Oleg Drokin ---

[PATCH 23/27] staging: lustre: take extra refcount in kiblnd_connreq_done

From: Liang Zhen refcount taken by cmid is not reliable after kiblnd_connreq_done released the glock because this connection is visible to other threads, another thread can find and close this connection right after kiblnd_connreq_done released the glock, if

[PATCH 01/27] staging: lustre: set downis to 1 if there's no NI for remote net

From: Liang Zhen lnet_route_t::lr_downis is marked as zero even if there is no NI to target network, this is wrong and breaks logic of ARF. This patch fixes this problem. Signed-off-by: Liang Zhen Intel-bug-id:

[PATCH 04/27] staging: lustre: return proper error code for LNet core

It is consider bad style in the linux kernel to return -1 or a positive number for an error. Instead return the appropriate error codes. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6142 Reviewed-on: http://review.whamcloud.com/17626

[PATCH 01/27] staging: lustre: set downis to 1 if there's no NI for remote net

From: Liang Zhen lnet_route_t::lr_downis is marked as zero even if there is no NI to target network, this is wrong and breaks logic of ARF. This patch fixes this problem. Signed-off-by: Liang Zhen Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6060 Reviewed-on:

[PATCH 04/27] staging: lustre: return proper error code for LNet core

It is consider bad style in the linux kernel to return -1 or a positive number for an error. Instead return the appropriate error codes. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6142 Reviewed-on: http://review.whamcloud.com/17626 Reviewed-by: Doug Oucharek

[PATCH 23/27] staging: lustre: take extra refcount in kiblnd_connreq_done

From: Liang Zhen refcount taken by cmid is not reliable after kiblnd_connreq_done released the glock because this connection is visible to other threads, another thread can find and close this connection right after kiblnd_connreq_done released the glock, if kiblnd_cm_callback for

[PATCH 07/27] staging: lustre: issue in the offset in lnet match hash table

From: Alyona Romanenko the offset in hash table is overflowed for no wildcard portal. The offset for no wildcard has been corrected as for wildcard in the LU-1622 Signed-off-by: Alyona Romanenko Intel-bug-id:

[PATCH 26/27] staging: lustre: avoid intensive reconnecting for ko2iblnd

From: Liang Zhen When there is a connection race between two nodes and one side of the connection is rejected by the other side. o2iblnd will reconnect immediately, this is going to generate a lot of trashes if: - race winner is slow and can't send out connecting request

[PATCH 13/27] staging: lustre: fix api-ni.c issues found by Klocwork Insight tool

From: Dmitry Eremin Pointer 'ni' checked for NULL at line 1569 may be passed to function and may be dereferenced there by passing argument 1 to function 'lnet_ni_notify_locked' at line 1621. Signed-off-by: Dmitry Eremin Intel-bug-id:

[PATCH 07/27] staging: lustre: issue in the offset in lnet match hash table

From: Alyona Romanenko the offset in hash table is overflowed for no wildcard portal. The offset for no wildcard has been corrected as for wildcard in the LU-1622 Signed-off-by: Alyona Romanenko Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7774 Reviewed-on:

[PATCH 26/27] staging: lustre: avoid intensive reconnecting for ko2iblnd

From: Liang Zhen When there is a connection race between two nodes and one side of the connection is rejected by the other side. o2iblnd will reconnect immediately, this is going to generate a lot of trashes if: - race winner is slow and can't send out connecting request in short time. -

[PATCH 13/27] staging: lustre: fix api-ni.c issues found by Klocwork Insight tool

From: Dmitry Eremin Pointer 'ni' checked for NULL at line 1569 may be passed to function and may be dereferenced there by passing argument 1 to function 'lnet_ni_notify_locked' at line 1621. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4629 Reviewed-on:

[PATCH v3 12/16] KVM: x86: remove pointless dereference of PIT

From: Radim Krčmář PIT is known at that point. Reviewed-by: Paolo Bonzini Signed-off-by: Radim Krčmář --- arch/x86/kvm/i8254.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/x86/kvm/i8254.c

[PATCH v3 12/16] KVM: x86: remove pointless dereference of PIT

From: Radim Krčmář PIT is known at that point. Reviewed-by: Paolo Bonzini Signed-off-by: Radim Krčmář --- arch/x86/kvm/i8254.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/x86/kvm/i8254.c b/arch/x86/kvm/i8254.c index 37e665c5f307..964902b33eed 100644 ---

[PATCH v3 10/16] KVM: x86: refactor kvm_free_pit

From: Radim Krčmář Could be easier to read, but git history will become deeper. Reviewed-by: Paolo Bonzini Signed-off-by: Radim Krčmář --- arch/x86/kvm/i8254.c | 22 ++ 1 file changed, 10 insertions(+), 12

[PATCH] eventfd: document lockless access in eventfd_poll

Since commit e22553e2a25e ("eventfd: don't take the spinlock in eventfd_poll", 2015-02-17), eventfd is reading ctx->count outside ctx->wqh.lock. However, things aren't as simple as the read barrier in eventfd_poll would suggest. In fact, the read barrier, besides lacking a comment, is not paired

[PATCH v3 10/16] KVM: x86: refactor kvm_free_pit

From: Radim Krčmář Could be easier to read, but git history will become deeper. Reviewed-by: Paolo Bonzini Signed-off-by: Radim Krčmář --- arch/x86/kvm/i8254.c | 22 ++ 1 file changed, 10 insertions(+), 12 deletions(-) diff --git a/arch/x86/kvm/i8254.c

[PATCH] eventfd: document lockless access in eventfd_poll

Since commit e22553e2a25e ("eventfd: don't take the spinlock in eventfd_poll", 2015-02-17), eventfd is reading ctx->count outside ctx->wqh.lock. However, things aren't as simple as the read barrier in eventfd_poll would suggest. In fact, the read barrier, besides lacking a comment, is not paired

[PATCH v3 11/16] KVM: x86: remove pit and kvm from kvm_kpit_state

From: Radim Krčmář kvm isn't ever used and pit can be accessed with container_of. If you *really* need kvm, pit_state_to_pit(ps)->kvm. Reviewed-by: Paolo Bonzini Signed-off-by: Radim Krčmář --- arch/x86/kvm/i8254.c | 14

[PATCH v3 11/16] KVM: x86: remove pit and kvm from kvm_kpit_state

From: Radim Krčmář kvm isn't ever used and pit can be accessed with container_of. If you *really* need kvm, pit_state_to_pit(ps)->kvm. Reviewed-by: Paolo Bonzini Signed-off-by: Radim Krčmář --- arch/x86/kvm/i8254.c | 14 +- arch/x86/kvm/i8254.h | 2 -- 2 files changed, 9

[PATCH v3 15/16] KVM: x86: turn kvm_kpit_state.reinject into atomic_t

From: Radim Krčmář Document possible races between readers and concurrent update to the ioctl. Suggested-by: Paolo Bonzini Signed-off-by: Radim Krčmář --- v3: new arch/x86/kvm/i8254.c | 8 arch/x86/kvm/i8254.h | 2 +- 2

[PATCH v3 15/16] KVM: x86: turn kvm_kpit_state.reinject into atomic_t

From: Radim Krčmář Document possible races between readers and concurrent update to the ioctl. Suggested-by: Paolo Bonzini Signed-off-by: Radim Krčmář --- v3: new arch/x86/kvm/i8254.c | 8 arch/x86/kvm/i8254.h | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git

[PATCH v3 13/16] KVM: x86: don't assume layout of kvm_kpit_state

From: Radim Krčmář channels has offset 0 and correct size now, but that can change. Reviewed-by: Paolo Bonzini Signed-off-by: Radim Krčmář --- arch/x86/kvm/x86.c | 12 1 file changed, 8 insertions(+), 4 deletions(-)

[PATCH v3 13/16] KVM: x86: don't assume layout of kvm_kpit_state

From: Radim Krčmář channels has offset 0 and correct size now, but that can change. Reviewed-by: Paolo Bonzini Signed-off-by: Radim Krčmář --- arch/x86/kvm/x86.c | 12 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index

Re: [PATCH 02/41] clk: bcm: Remove CLK_IS_ROOT

Stephen Boyd writes: > This flag is a no-op now. Remove usage of the flag. I like that this flag is going away. It's a nice cleanup. Reviewed-by: Eric Anholt signature.asc Description: PGP signature

[PATCH v2 1/4] resource: Change __request_region to inherit from immediate parent

__request_region() sets 'flags' of a new resource from @parent as it inherits the parent's attribute. When a target resource has a conflict, this function inserts the new resource entry under the conflicted entry by updating @parent. In this case, the new resource entry needs to inherit

[PATCH v2 3/4] resource: Add device-managed insert/remove_resource()

insert_resource() and remove_resouce() are called by producers of resources, such as FW modules and bus drivers. These modules may be implemented as loadable modules. Add device-managed implementaions of insert_resource() and remove_resouce() functions. Signed-off-by: Toshi Kani

Re: [PATCH 02/41] clk: bcm: Remove CLK_IS_ROOT

Stephen Boyd writes: > This flag is a no-op now. Remove usage of the flag. I like that this flag is going away. It's a nice cleanup. Reviewed-by: Eric Anholt signature.asc Description: PGP signature

[PATCH v2 1/4] resource: Change __request_region to inherit from immediate parent

__request_region() sets 'flags' of a new resource from @parent as it inherits the parent's attribute. When a target resource has a conflict, this function inserts the new resource entry under the conflicted entry by updating @parent. In this case, the new resource entry needs to inherit

[PATCH v2 3/4] resource: Add device-managed insert/remove_resource()

insert_resource() and remove_resouce() are called by producers of resources, such as FW modules and bus drivers. These modules may be implemented as loadable modules. Add device-managed implementaions of insert_resource() and remove_resouce() functions. Signed-off-by: Toshi Kani Cc: Ingo

Re: [RFC PATCH] x86: Make sure verify_cpu has a good stack

On 03/02/16 13:46, Borislav Petkov wrote: > On Wed, Mar 02, 2016 at 01:35:09PM -0800, H. Peter Anvin wrote: >> You're not actually testing anything as the real issue is what happens >> with a relocating bootloader. > > Hmm, how would that relocation happen so that va - __START_KERNEL_map >

Re: [RFC PATCH] x86: Make sure verify_cpu has a good stack

On 03/02/16 13:46, Borislav Petkov wrote: > On Wed, Mar 02, 2016 at 01:35:09PM -0800, H. Peter Anvin wrote: >> You're not actually testing anything as the real issue is what happens >> with a relocating bootloader. > > Hmm, how would that relocation happen so that va - __START_KERNEL_map >

Re: [4.4-rc1][Regression] drm/i915: Check live status before reading edid

On 02/29/2016 04:33 AM, Jani Nikula wrote: > On Wed, 24 Feb 2016, Joseph Salisbury wrote: >> Hi Sonika, >> >> A kernel bug report was opened against Ubuntu [0]. After a kernel >> bisect, it was found that reverting the following commit resolved this bug: >> >>

[PATCH v3 07/16] KVM: x86: remove unnecessary uses of PIT state lock

From: Radim Krčmář - kvm_create_pit had to lock only because it exposed kvm->arch.vpit very early, but initialization doesn't use kvm->arch.vpit since the last patch, so we can drop locking. - kvm_free_pit is only run after there are no users of KVM and therefore is the

[PATCH v2 0/4] Support persistent memory as reserved type in e820/EFI

ACPI 6.0 defines persistent memory (PMEM) ranges in multiple firmware interfaces, e820, EFI, and ACPI NFIT table. This EFI change, however, leads to hit a bug in the grub bootloader, which treats EFI_PERSISTENT_MEMORY type as regular memory and corrupts stored user data [1]. Therefore, BIOS may

[PATCH v3 16/16] KVM: document KVM_REINJECT_CONTROL ioctl

From: Radim Krčmář Signed-off-by: Radim Krčmář --- v3: new, one result of a long discussion with Paolo Documentation/virtual/kvm/api.txt | 24 1 file changed, 24 insertions(+) diff --git a/Documentation/virtual/kvm/api.txt

[PATCH v3 14/16] KVM: x86: move PIT timer function initialization

From: Radim Krčmář We can do it just once. Reviewed-by: Paolo Bonzini Signed-off-by: Radim Krčmář --- arch/x86/kvm/i8254.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/x86/kvm/i8254.c

[PATCH v2 0/4] Support persistent memory as reserved type in e820/EFI

ACPI 6.0 defines persistent memory (PMEM) ranges in multiple firmware interfaces, e820, EFI, and ACPI NFIT table. This EFI change, however, leads to hit a bug in the grub bootloader, which treats EFI_PERSISTENT_MEMORY type as regular memory and corrupts stored user data [1]. Therefore, BIOS may

[PATCH v3 16/16] KVM: document KVM_REINJECT_CONTROL ioctl

From: Radim Krčmář Signed-off-by: Radim Krčmář --- v3: new, one result of a long discussion with Paolo Documentation/virtual/kvm/api.txt | 24 1 file changed, 24 insertions(+) diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt index

[PATCH v3 14/16] KVM: x86: move PIT timer function initialization

From: Radim Krčmář We can do it just once. Reviewed-by: Paolo Bonzini Signed-off-by: Radim Krčmář --- arch/x86/kvm/i8254.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/x86/kvm/i8254.c b/arch/x86/kvm/i8254.c index 964902b33eed..68af4445d51d 100644 ---

Re: [4.4-rc1][Regression] drm/i915: Check live status before reading edid

On 02/29/2016 04:33 AM, Jani Nikula wrote: > On Wed, 24 Feb 2016, Joseph Salisbury wrote: >> Hi Sonika, >> >> A kernel bug report was opened against Ubuntu [0]. After a kernel >> bisect, it was found that reverting the following commit resolved this bug: >> >> commit

[PATCH v3 07/16] KVM: x86: remove unnecessary uses of PIT state lock

From: Radim Krčmář - kvm_create_pit had to lock only because it exposed kvm->arch.vpit very early, but initialization doesn't use kvm->arch.vpit since the last patch, so we can drop locking. - kvm_free_pit is only run after there are no users of KVM and therefore is the sole actor. -

[PATCH v2 4/4] ACPI: Change NFIT driver to insert new resource

ACPI 6.0 defines persistent memory (PMEM) ranges in multiple firmware interfaces, e820, EFI, and ACPI NFIT table. This EFI change, however, leads to hit a bug in the grub bootloader, which treats EFI_PERSISTENT_MEMORY type as regular memory and corrupts stored user data [1]. Therefore, BIOS may

[PATCH v2 4/4] ACPI: Change NFIT driver to insert new resource

ACPI 6.0 defines persistent memory (PMEM) ranges in multiple firmware interfaces, e820, EFI, and ACPI NFIT table. This EFI change, however, leads to hit a bug in the grub bootloader, which treats EFI_PERSISTENT_MEMORY type as regular memory and corrupts stored user data [1]. Therefore, BIOS may

[PATCH v3 08/16] KVM: x86: remove notifiers from PIT discard policy

From: Radim Krčmář Discard policy doesn't rely on information from notifiers, so we don't need to register notifiers unconditionally. We kept correct counts in case userspace switched between policies during runtime, but that can be avoided by reseting the state.

[PATCH v2 2/4] resource: Add remove_resource interface

insert_resource() and insert_resource_conflict() are called by resource producers to insert a new resource. When there is any conflict, they move conflicting resources down to the children of the new resource. There is no destructor of these interfaces, however. Add remove_resource(), which

[PATCH v3 08/16] KVM: x86: remove notifiers from PIT discard policy

From: Radim Krčmář Discard policy doesn't rely on information from notifiers, so we don't need to register notifiers unconditionally. We kept correct counts in case userspace switched between policies during runtime, but that can be avoided by reseting the state. Signed-off-by: Radim Krčmář

[PATCH v2 2/4] resource: Add remove_resource interface

insert_resource() and insert_resource_conflict() are called by resource producers to insert a new resource. When there is any conflict, they move conflicting resources down to the children of the new resource. There is no destructor of these interfaces, however. Add remove_resource(), which

[PATCH v3 05/16] KVM: x86: tone down WARN_ON pit.state_lock

From: Radim Krčmář If the guest could hit this, it would hang the host kernel, bacause of sheer number of those reports. Internal callers have to be sensible anyway, so we now only check for it in an API function. Signed-off-by: Radim Krčmář ---

[PATCH v3 05/16] KVM: x86: tone down WARN_ON pit.state_lock

From: Radim Krčmář If the guest could hit this, it would hang the host kernel, bacause of sheer number of those reports. Internal callers have to be sensible anyway, so we now only check for it in an API function. Signed-off-by: Radim Krčmář --- arch/x86/kvm/i8254.c | 17 +++-- 1

[PATCH v3 03/16] KVM: x86: add kvm_pit_reset_reinject

From: Radim Krčmář pit_state.pending and pit_state.irq_ack are always reset at the same time. Create a function for them. Signed-off-by: Radim Krčmář --- arch/x86/kvm/i8254.c | 18 ++ 1 file changed, 10 insertions(+), 8 deletions(-)

[PATCH v3 06/16] KVM: x86: pass struct kvm_pit instead of kvm in PIT

From: Radim Krčmář This patch passes struct kvm_pit into internal PIT functions. Those functions used to get PIT through kvm->arch.vpit, even though most of them never used *kvm for other purposes. Another benefit is that we don't need to set kvm->arch.vpit during

[PATCH v3 00/16] KVM: x86: change PIT discard policy and untangle related code

From: Radim Krčmář v3 - mark patches reviewed by Paolo [1,9-14/16] - properly categorize reinject struct member [Paolo] [7/16] - use atomic_t to document reinject usage [Paolo] [15/16] - document PIT reinject modes [16/16] v2:

[PATCH v3 01/16] KVM: x86: change PIT discard tick policy

From: Radim Krčmář Discard policy uses ack_notifiers to prevent injection of PIT interrupts before EOI from the last one. This patch changes the policy to always try to deliver the interrupt, which makes a difference when its vector is in ISR. Old implementation would drop

[PATCH v3 00/16] KVM: x86: change PIT discard policy and untangle related code

From: Radim Krčmář v3 - mark patches reviewed by Paolo [1,9-14/16] - properly categorize reinject struct member [Paolo] [7/16] - use atomic_t to document reinject usage [Paolo] [15/16] - document PIT reinject modes [16/16] v2: http://www.spinics.net/lists/kvm/msg127927.html Radim Krčmář

[PATCH v3 01/16] KVM: x86: change PIT discard tick policy

From: Radim Krčmář Discard policy uses ack_notifiers to prevent injection of PIT interrupts before EOI from the last one. This patch changes the policy to always try to deliver the interrupt, which makes a difference when its vector is in ISR. Old implementation would drop the interrupt, but

[PATCH v3 03/16] KVM: x86: add kvm_pit_reset_reinject

From: Radim Krčmář pit_state.pending and pit_state.irq_ack are always reset at the same time. Create a function for them. Signed-off-by: Radim Krčmář --- arch/x86/kvm/i8254.c | 18 ++ 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/arch/x86/kvm/i8254.c

[PATCH v3 06/16] KVM: x86: pass struct kvm_pit instead of kvm in PIT

From: Radim Krčmář This patch passes struct kvm_pit into internal PIT functions. Those functions used to get PIT through kvm->arch.vpit, even though most of them never used *kvm for other purposes. Another benefit is that we don't need to set kvm->arch.vpit during initialization.

[PATCH v3 02/16] KVM: x86: simplify atomics in kvm_pit_ack_irq

From: Radim Krčmář We already have a helper that does the same thing. Signed-off-by: Radim Krčmář --- arch/x86/kvm/i8254.c | 12 +--- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/arch/x86/kvm/i8254.c b/arch/x86/kvm/i8254.c index

[PATCH v3 02/16] KVM: x86: simplify atomics in kvm_pit_ack_irq

From: Radim Krčmář We already have a helper that does the same thing. Signed-off-by: Radim Krčmář --- arch/x86/kvm/i8254.c | 12 +--- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/arch/x86/kvm/i8254.c b/arch/x86/kvm/i8254.c index ab5318727579..7d694ac7f4a4 100644 ---

Re: [PATCHv7 5/7] eeprom: at25: extend driver to plug into the NVMEM framework

Hi Andrew, On 26.02.2016 21:59, Andrew Lunn wrote: > Add a regmap for accessing the EEPROM, and then use that with the > NVMEM framework. Enable backwards compatibility in the NVMEM config, > so that the 'eeprom' file in sys is provided by the framework. > > Signed-off-by: Andrew Lunn

Re: [PATCHv7 5/7] eeprom: at25: extend driver to plug into the NVMEM framework

Hi Andrew, On 26.02.2016 21:59, Andrew Lunn wrote: > Add a regmap for accessing the EEPROM, and then use that with the > NVMEM framework. Enable backwards compatibility in the NVMEM config, > so that the 'eeprom' file in sys is provided by the framework. > > Signed-off-by: Andrew Lunn >

Re: [PATCH v5 5/5] lib/percpu-list: Add a config parameter for disabling per-cpu list

On 03/02/2016 03:41 AM, Ingo Molnar wrote: * Waiman Long wrote: As there is concern that the larger pcpu_list_node structure and the per-cpu overhead may be a waste of resource on small system. This patch adds a config parameter CONFIG_PERCPU_LIST to disable the per-cpu

Re: [PATCH v5 5/5] lib/percpu-list: Add a config parameter for disabling per-cpu list

On 03/02/2016 03:41 AM, Ingo Molnar wrote: * Waiman Long wrote: As there is concern that the larger pcpu_list_node structure and the per-cpu overhead may be a waste of resource on small system. This patch adds a config parameter CONFIG_PERCPU_LIST to disable the per-cpu list if the kernel

[PATCH] staging/android: add flags member to sync ioctl structs

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 arises. v2: check if flags are valid (zero, in this case) v3: return -EINVAL if flags are

[PATCH] staging/android: add flags member to sync ioctl structs

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 arises. v2: check if flags are valid (zero, in this case) v3: return -EINVAL if flags are not zero'ed v4: add padding for

Re: [PATCHv7 3/7] eeprom: at24: extend driver to plug into the NVMEM framework

On Wed, Mar 02, 2016 at 11:46:39PM +0200, Vladimir Zapolskiy wrote: > Hi Andrew, > > On 26.02.2016 21:59, Andrew Lunn wrote: > > Add a regmap for accessing the EEPROM, and then use that with the > > NVMEM framework. Set the NVMEM config structure to enable backward, so > > that the 'eeprom' file

Re: [PATCHv7 3/7] eeprom: at24: extend driver to plug into the NVMEM framework

On Wed, Mar 02, 2016 at 11:46:39PM +0200, Vladimir Zapolskiy wrote: > Hi Andrew, > > On 26.02.2016 21:59, Andrew Lunn wrote: > > Add a regmap for accessing the EEPROM, and then use that with the > > NVMEM framework. Set the NVMEM config structure to enable backward, so > > that the 'eeprom' file

Re: [PATCH 44/50] pinctrl: rockchip: Use devm_pinctrl_register() for pinctrl registration

Am Mittwoch, 24. Februar 2016, 18:46:09 schrieb Laxman Dewangan: > Use devm_pinctrl_register() for pin control registration. > > Signed-off-by: Laxman Dewangan > Cc: Heiko Stuebner > Cc: linux-rockc...@lists.infradead.org looks good to me Reviewed-by:

Re: [PATCH 44/50] pinctrl: rockchip: Use devm_pinctrl_register() for pinctrl registration

Am Mittwoch, 24. Februar 2016, 18:46:09 schrieb Laxman Dewangan: > Use devm_pinctrl_register() for pin control registration. > > Signed-off-by: Laxman Dewangan > Cc: Heiko Stuebner > Cc: linux-rockc...@lists.infradead.org looks good to me Reviewed-by: Heiko Stuebner

Re: [RFC PATCH] x86: Make sure verify_cpu has a good stack

On Wed, Mar 02, 2016 at 01:35:09PM -0800, H. Peter Anvin wrote: > You're not actually testing anything as the real issue is what happens > with a relocating bootloader. Hmm, how would that relocation happen so that va - __START_KERNEL_map doesn't give pa? Or do you mean something else with

Re: [RFC PATCH] x86: Make sure verify_cpu has a good stack

On Wed, Mar 02, 2016 at 01:35:09PM -0800, H. Peter Anvin wrote: > You're not actually testing anything as the real issue is what happens > with a relocating bootloader. Hmm, how would that relocation happen so that va - __START_KERNEL_map doesn't give pa? Or do you mean something else with

Re: [PATCH] arm64: dts: rockchip: remove broken-cd from emmc and sdio

Am Dienstag, 26. Januar 2016, 10:06:59 schrieb Shawn Lin: > Only one of "broken-cd" and "non-removable" should be supplied > according to Documentation/devicetree/bindings/mmc/mmc.txt. > Obviously emmc and sdio-wifi are non-removable devices, while > broken-cd is for removable device whose card

Re: [PATCH] arm: dts: rockchip: remove broken-cd from emmc and sdio

Am Dienstag, 26. Januar 2016, 10:06:43 schrieb Shawn Lin: > Only one of "broken-cd" and "non-removable" should be supplied > according to Documentation/devicetree/bindings/mmc/mmc.txt. > Obviously emmc and sdio-wifi are non-removable devices, while > broken-cd is for removable device whose card

Re: [PATCH] arm: dts: rockchip: remove broken-cd from emmc and sdio

Am Dienstag, 26. Januar 2016, 10:06:43 schrieb Shawn Lin: > Only one of "broken-cd" and "non-removable" should be supplied > according to Documentation/devicetree/bindings/mmc/mmc.txt. > Obviously emmc and sdio-wifi are non-removable devices, while > broken-cd is for removable device whose card

Re: [PATCH] arm64: dts: rockchip: remove broken-cd from emmc and sdio

Am Dienstag, 26. Januar 2016, 10:06:59 schrieb Shawn Lin: > Only one of "broken-cd" and "non-removable" should be supplied > according to Documentation/devicetree/bindings/mmc/mmc.txt. > Obviously emmc and sdio-wifi are non-removable devices, while > broken-cd is for removable device whose card

Re: [PATCHv7 3/7] eeprom: at24: extend driver to plug into the NVMEM framework

Hi Andrew, On 26.02.2016 21:59, Andrew Lunn wrote: > Add a regmap for accessing the EEPROM, and then use that with the > NVMEM framework. Set the NVMEM config structure to enable backward, so > that the 'eeprom' file in sys is provided by the framework. > > Signed-off-by: Andrew Lunn

Re: [PATCHv7 3/7] eeprom: at24: extend driver to plug into the NVMEM framework

Hi Andrew, On 26.02.2016 21:59, Andrew Lunn wrote: > Add a regmap for accessing the EEPROM, and then use that with the > NVMEM framework. Set the NVMEM config structure to enable backward, so > that the 'eeprom' file in sys is provided by the framework. > > Signed-off-by: Andrew Lunn >

Re: [PATCH v6 4/6] staging/android: align struct sync_merge_data to a multiple of 64-bits

2016-03-02 Gustavo Padovan : > From: Gustavo Padovan > > Change order of the field to avoid alignment issues with 64 bits > platforms. > > Signed-off-by: Gustavo Padovan > --- >

Re: [PATCH v6 4/6] staging/android: align struct sync_merge_data to a multiple of 64-bits

2016-03-02 Gustavo Padovan : > From: Gustavo Padovan > > Change order of the field to avoid alignment issues with 64 bits > platforms. > > Signed-off-by: Gustavo Padovan > --- > drivers/staging/android/uapi/sync.h | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) Please ignore

[PATCH] of: add 'const' for of_property_*_string*() parameter '*np'

From: David Rivshin The of_property_{read,count,match}_string* family of functions never modify the struct device_node pointer that is passed in, so there is no reason for it to be non-const. Equivalent functions for all other types already take a 'const struct device_node

[PATCH] of: add 'const' for of_property_*_string*() parameter '*np'

From: David Rivshin The of_property_{read,count,match}_string* family of functions never modify the struct device_node pointer that is passed in, so there is no reason for it to be non-const. Equivalent functions for all other types already take a 'const struct device_node *np'. Signed-off-by:

Re: [RFC PATCH] x86: Make sure verify_cpu has a good stack

On 03/02/16 11:50, Borislav Petkov wrote: > On Wed, Mar 02, 2016 at 10:39:05AM -0800, H. Peter Anvin wrote: >> Well, we definitely should use %rip-relative addressing if we can. > > Right you are. > >> However, even so I believe this breaks if the kernel is loaded anywhere >> but its default

Re: [RFC PATCH] x86: Make sure verify_cpu has a good stack

On 03/02/16 11:50, Borislav Petkov wrote: > On Wed, Mar 02, 2016 at 10:39:05AM -0800, H. Peter Anvin wrote: >> Well, we definitely should use %rip-relative addressing if we can. > > Right you are. > >> However, even so I believe this breaks if the kernel is loaded anywhere >> but its default

Re: [PATCH 3/6] x86/mbm: Intel Memory B/W Monitoring enumeration and init

On Wed, 2 Mar 2016, Vikas Shivappa wrote: On Wed, 2 Mar 2016, Thomas Gleixner wrote: Leaks mbm_local and mbm_total Will fix. Thanks for pointing out. I missed the ones which are done at the next level of calls from the init. Will do a check on all the globals as well. Vikas

Re: [PATCH 3/6] x86/mbm: Intel Memory B/W Monitoring enumeration and init

On Wed, 2 Mar 2016, Vikas Shivappa wrote: On Wed, 2 Mar 2016, Thomas Gleixner wrote: Leaks mbm_local and mbm_total Will fix. Thanks for pointing out. I missed the ones which are done at the next level of calls from the init. Will do a check on all the globals as well. Vikas

Re: [PATCH V2] ubifs: Add logging functions for ubifs_msg, ubifs_err and ubifs_warn

On Wed, 2016-03-02 at 22:24 +0100, Richard Weinberger wrote: > Am 02.03.2016 um 19:58 schrieb Joe Perches: [] > > For drivers/mtd/ubi, Artem is also a nominal maintainer, but > > last signed a patch in 2014. > > > > Likely the MAINTAINERS entry for UBI should be updated too. > > > > Maybe

Re: [PATCH V2] ubifs: Add logging functions for ubifs_msg, ubifs_err and ubifs_warn

On Wed, 2016-03-02 at 22:24 +0100, Richard Weinberger wrote: > Am 02.03.2016 um 19:58 schrieb Joe Perches: [] > > For drivers/mtd/ubi, Artem is also a nominal maintainer, but > > last signed a patch in 2014. > > > > Likely the MAINTAINERS entry for UBI should be updated too. > > > > Maybe

Re: [GIT PULL] at91: dt for 4.6 #2

On Wednesday 02 March 2016 22:07:50 Alexandre Belloni wrote: > On 02/03/2016 at 21:50:59 +0100, Arnd Bergmann wrote : > > I see that your gpg key has expired last week, you may want to do something > > about that, I think you can just update the date rather than creating a > > new key. > > > >

Re: [GIT PULL] at91: dt for 4.6 #2

On Wednesday 02 March 2016 22:07:50 Alexandre Belloni wrote: > On 02/03/2016 at 21:50:59 +0100, Arnd Bergmann wrote : > > I see that your gpg key has expired last week, you may want to do something > > about that, I think you can just update the date rather than creating a > > new key. > > > >

Re: [PATCH V2] ubifs: Add logging functions for ubifs_msg, ubifs_err and ubifs_warn

Joe, Am 02.03.2016 um 19:58 schrieb Joe Perches: > On Wed, 2016-03-02 at 19:46 +0100, Richard Weinberger wrote: >> Am 02.03.2016 7:19 nachm. schrieb Joe Perches : >>> On Tue, 2016-02-23 at 12:21 -0800, Joe Perches wrote: The existing logging macros are fairly large and

Re: [PATCH V2] ubifs: Add logging functions for ubifs_msg, ubifs_err and ubifs_warn

Joe, Am 02.03.2016 um 19:58 schrieb Joe Perches: > On Wed, 2016-03-02 at 19:46 +0100, Richard Weinberger wrote: >> Am 02.03.2016 7:19 nachm. schrieb Joe Perches : >>> On Tue, 2016-02-23 at 12:21 -0800, Joe Perches wrote: The existing logging macros are fairly large and converting the

<    3   4   5   6   7   8   9   10   11   12   >