Hi,
On 03/04/18 13:17, Vincent Guittot wrote:
> Hi Valentin,
>
[...]
>>
>> I believe ASYM_PACKING behaves better here because the workload is only
>> sysbench threads. As stated above, since task utilization is disregarded, I
>
> It behaves better because it doesn't wait for the task's utilizati
The local variable was newly introduced but is only accessed in one
place on x86_64, but not on 32-bit:
arch/x86/kvm/vmx.c: In function 'vmx_save_host_state':
arch/x86/kvm/vmx.c:2175:6: error: unused variable 'cpu'
[-Werror=unused-variable]
This puts it into another #ifdef.
Fixes: 35060ed6a1ff
On 30/03/18 00:00, Thor Thayer wrote:
> Hi,
>
> I'm working on an ARM64 architecture that needs to manipulate some
> protected registers that are only accessible in EL3. Linux is running at
> EL1 which doesn't have the proper permissions for these registers.
>
If the hardware/IP registers are des
-ci/linux/commits/Xidong-Wang/scsi-mvsas-fix-memory-leak/20180404-182132
base: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git for-next
config: i386-randconfig-x016-201813 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to
Al and Michal, are you OK with this patch?
>From bbc0d00935ebcb7e287403bae545fae9340830d9 Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Wed, 4 Apr 2018 12:19:42 +0900
Subject: [PATCH] mm,vmscan: Allow preallocating memory for register_shrinker().
syzbot is catching so many bugs triggered by
The newly introduced lock is only used when CONFIG_IRQ_REMAP is enabled:
drivers/iommu/amd_iommu.c:86:24: error: 'iommu_table_lock' defined but not used
[-Werror=unused-variable]
static DEFINE_SPINLOCK(iommu_table_lock);
This moves the definition next to the user, within the #ifdef protected
se
The last fix was still wrong, as we need the inline dummy functions
also for the case that CONFIG_HMM is enabled but CONFIG_HMM_MIRROR
is not:
kernel/fork.o: In function `__mmdrop':
fork.c:(.text+0x14f6): undefined reference to `hmm_mm_destroy'
This adds back the second copy of the dummy function
On Wed, Apr 4, 2018 at 11:49 AM, Arnd Bergmann wrote:
> A new set of warnings appeared in next-20180403 in some configurations
> when gcc cannot see that rbd_assert(0) leads to an unreachable code
> path:
>
> drivers/block/rbd.c: In function 'rbd_img_is_write':
> drivers/block/rbd.c:1397:1: error:
Hi Amd,
Thanks for your patch.
On 04/04/2018 06:23 PM, Arnd Bergmann wrote:
We get a build error when compiling the iommu driver without CONFIG_OF:
drivers/iommu/rockchip-iommu.c: In function 'rk_iommu_of_xlate':
drivers/iommu/rockchip-iommu.c:1101:2: error: implicit declaration of function
'
> > As far as I understand the code now, both instances can be master /
> > slave simultanously on the same bus?
>
> Correct.
Very nice! :)
signature.asc
Description: PGP signature
Hi Daniel,
Thanks for your reply.
On 04/04/2018 12:11 AM, Daniel Kurtz wrote:
Hi Jeffy,
Sorry for delayed response.
On Mon, Mar 26, 2018 at 1:58 AM JeffyChen wrote:
Hi Daniel,
Thanks for your reply.
On 03/26/2018 02:31 PM, Daniel Kurtz wrote:
+struct rk_iommudata {
+ struct rk
Modify timer register size in a common device tree for all Nuvoton
NPCM750 BMCs.
Signed-off-by: Tomer Maimon
---
arch/arm/boot/dts/nuvoton-npcm750.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/nuvoton-npcm750.dtsi
b/arch/arm/boot/dts/nuvoton-npcm750.
Modify clock binding in a common device tree for all Nuvoton
NPCM750 BMCs.
Modify NPCM750 modules clock numbers accourding the new
clock driver.
Signed-off-by: Tomer Maimon
---
arch/arm/boot/dts/nuvoton-npcm750.dtsi | 58 ++
1 file changed, 44 insertions(+), 14 d
Add watchdog device node to a common device tree for all Nuvoton
NPCM750 BMCs and a board specific device tree for the NPCM750 (Poleg)
evaluation board.
Signed-off-by: Tomer Maimon
---
arch/arm/boot/dts/nuvoton-npcm750-evb.dts | 4
arch/arm/boot/dts/nuvoton-npcm750.dtsi| 24 +++
Modify UART compatible name in a common device tree for all Nuvoton
NPCM750 BMCs.
Signed-off-by: Tomer Maimon
---
arch/arm/boot/dts/nuvoton-npcm750.dtsi | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/nuvoton-npcm750.dtsi
b/arch/arm/boot/dts/nuvoton
Modify Nuvoton NPCM7xx device tree structure by adding
nuvoton common nNPCM7xx device tree structure that
include all common modules.
Signed-off-by: Tomer Maimon
---
arch/arm/boot/dts/nuvoton-common-npcm7xx.dtsi | 187 ++
arch/arm/boot/dts/nuvoton-npcm750-evb.dts |
Signed-off-by: Tomer Maimon
---
arch/arm/boot/dts/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 8164c1294226..7e2424957809 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -307,
This patch set include modifications to the NPCM7xx
device tree according latest sent modules patches:
1. add watchdog device to NPCM750 device tree
- https://patchwork.kernel.org/patch/10269679/
2. modify UART compatible name in NPCM750 device tree
- https://patchwork.kernel.org/patch/10220251/
Hi Arnd,
On 04/04/18 11:23, Arnd Bergmann wrote:
We get a build error when compiling the iommu driver without CONFIG_OF:
drivers/iommu/rockchip-iommu.c: In function 'rk_iommu_of_xlate':
drivers/iommu/rockchip-iommu.c:1101:2: error: implicit declaration of function
'of_dev_put'; did you mean 'o
On Wed, Apr 04, 2018 at 02:34:52AM +, David Wang wrote:
> Those are new processors and main usage of CentaurHauls CPUs in recent
> years is for limited and/or embedded instead of distribution markets.
> So there is no plan or resource to create such document for public
> access. Is public spec
Hi Linus,
here is the major slew of GPIO changes for v4.17.
Some things to notice:
- I merged in v4.16-rc5 to get rid of a really nasty merge
conflict that was making it hard to rebuild linux-next, and
this happened due to a big fix in the Renesas R-Car driver
collding with ongoing develop
On Tue, Apr 03, 2018 at 09:15:11AM +0800, Hanjun Guo wrote:
> [+Cc Lorenzo]
>
> Hi Neil,
>
> On 2018/4/3 1:59, Neil Leeder wrote:
> > Hi Hanjun,
> >
> > On 4/2/2018 10:24 AM, Hanjun Guo wrote:
> >
> >>
> >> I think we need to wait for the new version of IORT spec,
> >> which includes the fix fo
On 04/04/2018 09:50 AM, Maxime Ripard wrote:
On Tue, Apr 03, 2018 at 06:44:46PM +0300, Sergey Suloev wrote:
There is no need to handle 3/4 empty interrupt as the maximum
supported transfer length in PIO mode is equal to FIFO depth,
i.e. 128 bytes for sun6i and 64 bytes for sun8i SoCs.
Changes i
On Wed, Apr 4, 2018 at 6:21 AM, Daniel Vetter wrote:
> On Wed, Apr 04, 2018 at 12:03:00PM +0200, Daniel Vetter wrote:
>> On Tue, Apr 03, 2018 at 06:42:23PM -0400, Rob Clark wrote:
>> > Add an atomic helper to implement dirtyfb support. This is needed to
>> > support DSI command-mode panels with x
On 14 March 2018 at 02:09, Mike Kravetz wrote:
> On 03/13/2018 04:42 AM, Anders Roxell wrote:
>> gcc warns about implicit declaration.
>>
>> gcc -D_FILE_OFFSET_BITS=64 -I../../../../include/uapi/
>> -I../../../../include/ -I../../../../usr/include/
>> memfd_test.c common.o -o memfd_test
>
On Wed, Apr 4, 2018 at 6:36 AM, Maarten Lankhorst
wrote:
> Op 04-04-18 om 12:21 schreef Daniel Vetter:
>> On Wed, Apr 04, 2018 at 12:03:00PM +0200, Daniel Vetter wrote:
>>> On Tue, Apr 03, 2018 at 06:42:23PM -0400, Rob Clark wrote:
Add an atomic helper to implement dirtyfb support. This is n
On Wed, Apr 4, 2018 at 5:56 AM, Daniel Vetter wrote:
> On Wed, Apr 04, 2018 at 11:10:08AM +0200, Thomas Hellstrom wrote:
>> On 04/04/2018 10:43 AM, Daniel Vetter wrote:
>> > On Wed, Apr 04, 2018 at 10:22:21AM +0200, Thomas Hellstrom wrote:
>> > > Hi,
>> > >
>> > > On 04/04/2018 08:58 AM, Daniel Ve
-ci/linux/commits/Xidong-Wang/scsi-mvsas-fix-memory-leak/20180404-182132
base: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git for-next
config: x86_64-randconfig-x010-201813 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to
On 04/04/18 13:17, Ulf Hansson wrote:
> On 4 April 2018 at 11:05, Chunyan Zhang wrote:
>> Hi Ulf,
>>
>> Do you have some comments on this patch-set?
>
> No objections from my side of the series, however I am relying on
> Adrian's ack before I pick any of the patches.
We don't have any drivers th
We want to work towards phasing out the at24_platform_data structure.
There are few users and its contents can be represented using generic
device properties. Using device properties only will allow us to
significantly simplify the at24 configuration code.
Remove the at24_platform_data structure a
We want to work towards phasing out the at24_platform_data structure.
There are few users and its contents can be represented using generic
device properties. Using device properties only will allow us to
significantly simplify the at24 configuration code.
Remove the at24_platform_data structure a
On 04/04/2018 12:28 PM, Thomas Hellstrom wrote:
On 04/04/2018 11:56 AM, Daniel Vetter wrote:
On Wed, Apr 04, 2018 at 11:10:08AM +0200, Thomas Hellstrom wrote:
On 04/04/2018 10:43 AM, Daniel Vetter wrote:
On Wed, Apr 04, 2018 at 10:22:21AM +0200, Thomas Hellstrom wrote:
Hi,
On 04/04/2018 08:5
Op 04-04-18 om 13:37 schreef Rob Clark:
> On Wed, Apr 4, 2018 at 6:36 AM, Maarten Lankhorst
> wrote:
>> Op 04-04-18 om 12:21 schreef Daniel Vetter:
>>> On Wed, Apr 04, 2018 at 12:03:00PM +0200, Daniel Vetter wrote:
On Tue, Apr 03, 2018 at 06:42:23PM -0400, Rob Clark wrote:
> Add an atomic
On Wed, Mar 28, 2018 at 12:38:33PM +0100, Gustavo Pimentel wrote:
Please always write a commit log even if it is trivial.
Thanks,
Lorenzo
> Signed-off-by: Gustavo Pimentel
> ---
> Documentation/devicetree/bindings/pci/designware-pcie.txt | 13 +
> 1 file changed, 13 insertions(+)
>
On 4 April 2018 at 13:43, Adrian Hunter wrote:
> On 04/04/18 13:17, Ulf Hansson wrote:
>> On 4 April 2018 at 11:05, Chunyan Zhang wrote:
>>> Hi Ulf,
>>>
>>> Do you have some comments on this patch-set?
>>
>> No objections from my side of the series, however I am relying on
>> Adrian's ack before
On 04.04.2018 12:44, Arnd Bergmann wrote:
> The local variable was newly introduced but is only accessed in one
> place on x86_64, but not on 32-bit:
>
> arch/x86/kvm/vmx.c: In function 'vmx_save_host_state':
> arch/x86/kvm/vmx.c:2175:6: error: unused variable 'cpu'
> [-Werror=unused-variable]
>
We want to work towards phasing out the at24_platform_data structure.
There are few users and its contents can be represented using generic
device properties. Using device properties only will allow us to
significantly simplify the at24 configuration code.
Remove the at24_platform_data structure a
After 03fe2debbb2771fb90881e merged during 4.17 marge window,
I start to see following warning during "make xmldocs"
./include/net/mac80211.h:2083: warning: bad line: >
Replace ">" with "*" fix the issue.
Signed-off-by: Masanari Iida
---
include/net/mac80211.h | 2 +-
1 file changed, 1 insert
> From: Jason Gunthorpe [mailto:j...@ziepe.ca]
> Sent: Tuesday, April 03, 2018 11:04 PM
>
> On Tue, Apr 03, 2018 at 07:42:28AM +, Kalderon, Michal wrote:
> > > From: Sinan Kaya [mailto:ok...@codeaurora.org]
> > > Sent: Tuesday, April 03, 2018 5:30 AM
> > > To: linux-r...@vger.kernel.org; ti...
On 04.04.2018 01:28, Wanpeng Li wrote:
> From: Wanpeng Li
>
> Introduce handle_ud() to handle invalid opcode, this function will be
> used by later patches.
>
> Reviewed-by: Konrad Rzeszutek Wilk
> Reviewed-by: Liran Alon
> Cc: Paolo Bonzini
> Cc: Radim Krčmář
> Cc: Andrew Cooper
> Cc: Konr
Since Linux v4.2 with commit 1b852bceb0d1 ("mnt: Refactor the logic for
mounting sysfs and proc in a user namespace"), new mounts of proc or
sysfs in non init userns are only allowed when there is at least one
fully-visible proc or sysfs mount.
This is to enforce that proc/sysfs files masked by a
Hi,
On Wed, Apr 04, 2018 at 12:27:19PM +0200, Arnd Bergmann wrote:
> Without gpiolib, the gpiod_get_array_value_cansleep() is an empty stub,
> so gcc notices that the resulting array is never initialized:
>
> drivers/phy/motorola/phy-mapphone-mdm6600.c: In function 'phy_mdm6600_status':
> drivers
Hi Lorenzo,
On 04/04/2018 12:50, Lorenzo Pieralisi wrote:
> On Wed, Mar 28, 2018 at 12:38:33PM +0100, Gustavo Pimentel wrote:
>
> Please always write a commit log even if it is trivial.
Ok, Kishon has also refered that. On next patch version it'll contain a log
description.
>
> Thanks,
> Loren
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 1eb495e..a55ecef 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -146,6 +146,9 @@ bool __read_mostly enable_vmware_backdoor = false;
> module_param(enable_vmware_backdoor, bool, S_IRUGO);
> EXPORT_SYMBOL_GPL(enable_
On Mon, Apr 2, 2018 at 4:28 AM, Jisheng Zhang
wrote:
> On Fri, 30 Mar 2018 15:59:32 +0200 Andrew Lunn wrote:
>
>> On Fri, Mar 30, 2018 at 11:02:11AM +0800, Jisheng Zhang wrote:
>> > Synaptics has acquired the Multimedia Solutions Business of Marvell[1].
>> > So change the berlin entry name and mov
Soon I'll not be available by my Intel email address, so switching to my
personal email address instead.
Signed-off-by: Yehezkel Bernat
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 4623caf8d72d..46721a7dd10e 100644
--- a/
On Wed, Apr 4, 2018 at 7:49 AM, Maarten Lankhorst
wrote:
> Op 04-04-18 om 13:37 schreef Rob Clark:
>> On Wed, Apr 4, 2018 at 6:36 AM, Maarten Lankhorst
>> wrote:
>>> Op 04-04-18 om 12:21 schreef Daniel Vetter:
On Wed, Apr 04, 2018 at 12:03:00PM +0200, Daniel Vetter wrote:
> On Tue, Apr 0
On Wed, Apr 04, 2018 at 10:23:25AM +0200, Miklos Szeredi wrote:
> On Fri, Mar 30, 2018 at 3:08 AM, Stephen Rothwell
> wrote:
> > Hi Miklos,
> >
> > Commit
> >
> > cbf293becfa4 ("ovl: cleanup setting OVL_INDEX")
> >
> > is missing a Signed-off-by from its author.
>
> Hi Steven,
>
> AFAIK for t
On 4 April 2018 12:47:06 BST, Bartosz Golaszewski wrote:
>We want to work towards phasing out the at24_platform_data structure.
>There are few users and its contents can be represented using generic
>device properties. Using device properties only will allow us to
>significantly simplify the at2
The __net_initdata section cannot currently be used for structures that
get cleaned up in an exitcall using unregister_pernet_operations:
WARNING: vmlinux.o(.text+0x868c34): Section mismatch in reference from the
function nsim_devlink_exit() to the (unknown reference) .init.data:(unknown)
The fun
On Wed, Apr 04, 2018 at 01:46:37PM +0200, Thomas Hellstrom wrote:
> On 04/04/2018 12:28 PM, Thomas Hellstrom wrote:
> > On 04/04/2018 11:56 AM, Daniel Vetter wrote:
> > > On Wed, Apr 04, 2018 at 11:10:08AM +0200, Thomas Hellstrom wrote:
> > > > On 04/04/2018 10:43 AM, Daniel Vetter wrote:
> > > > >
On Wed, Apr 04, 2018 at 07:40:32AM -0400, Rob Clark wrote:
> On Wed, Apr 4, 2018 at 5:56 AM, Daniel Vetter wrote:
> > On Wed, Apr 04, 2018 at 11:10:08AM +0200, Thomas Hellstrom wrote:
> >> On 04/04/2018 10:43 AM, Daniel Vetter wrote:
> >> > On Wed, Apr 04, 2018 at 10:22:21AM +0200, Thomas Hellstro
On Wed, Apr 04, 2018 at 07:35:58AM -0400, Rob Clark wrote:
> On Wed, Apr 4, 2018 at 6:21 AM, Daniel Vetter wrote:
> > On Wed, Apr 04, 2018 at 12:03:00PM +0200, Daniel Vetter wrote:
> >> On Tue, Apr 03, 2018 at 06:42:23PM -0400, Rob Clark wrote:
> >> > Add an atomic helper to implement dirtyfb supp
On Tue, Apr 3, 2018 at 11:20 PM, Michal Hocko wrote:
> On Tue 03-04-18 18:56:27, Steven Rostedt wrote:
> [...]
>> From your earlier email:
>>
>> > Except that it doesn't work. si_mem_available is not really suitable for
>> > any allocation estimations. Its only purpose is to provide a very rough
>
Yury, are you OK with this patch?
>From 7f21827cdfe9780b4949b22bcd19efa721b463d2 Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Wed, 4 Apr 2018 21:12:10 +0900
Subject: [PATCH] lib/bitmap: Rewrite __bitmap_parselist().
syzbot is catching stalls at __bitmap_parselist() [1]. The trigger is
u
The new axp288 extcon driver has no dependency on USB itself but
calls the usb role switch helper functions. This causes a link error
when USB_COMMON is disabled, as that subdirectory never gets entered:
drivers/extcon/extcon-axp288.o: In function `axp288_usb_role_work':
extcon-axp288.c:(.text+0x4
Op 04-04-18 om 14:05 schreef Rob Clark:
> On Wed, Apr 4, 2018 at 7:49 AM, Maarten Lankhorst
> wrote:
>> Op 04-04-18 om 13:37 schreef Rob Clark:
>>> On Wed, Apr 4, 2018 at 6:36 AM, Maarten Lankhorst
>>> wrote:
Op 04-04-18 om 12:21 schreef Daniel Vetter:
> On Wed, Apr 04, 2018 at 12:03:00P
On Wed, Apr 4, 2018 at 2:05 PM, Rob Clark wrote:
> On Wed, Apr 4, 2018 at 7:49 AM, Maarten Lankhorst
> wrote:
>> Op 04-04-18 om 13:37 schreef Rob Clark:
>>> On Wed, Apr 4, 2018 at 6:36 AM, Maarten Lankhorst
>>> wrote:
Op 04-04-18 om 12:21 schreef Daniel Vetter:
> On Wed, Apr 04, 2018 at
Op 04-04-18 om 14:26 schreef Daniel Vetter:
> On Wed, Apr 4, 2018 at 2:05 PM, Rob Clark wrote:
>> On Wed, Apr 4, 2018 at 7:49 AM, Maarten Lankhorst
>> wrote:
>>> Op 04-04-18 om 13:37 schreef Rob Clark:
On Wed, Apr 4, 2018 at 6:36 AM, Maarten Lankhorst
wrote:
> Op 04-04-18 om 12:21
On Wed, Apr 04, 2018 at 11:41:23AM +0100, Colin Ian King wrote:
> On 04/04/18 11:24, Dan Carpenter wrote:
> > On Tue, Apr 03, 2018 at 03:45:40PM +0200, Ladislav Michl wrote:
> >> On Fri, Mar 30, 2018 at 04:44:20PM +0100, Colin King wrote:
> >>> From: Colin Ian King
> >>
> >> Hello Colin,
> >>
> >>
gcc complains about fortify_panic() possibly returning:
arch/arm/boot/compressed/misc.c: In function 'fortify_panic':
arch/arm/boot/compressed/misc.c:167:1: error: 'noreturn' function does return
[-Werror]
This annotates the error() function as __noreturn, which lets gcc
see in all configuration
Hi Tom,
On Mon, 02 Apr 2018 12:09:33 -0500
Tom Zanussi wrote:
> after:
>
> # echo 'wakeup_latency u64 lat; pid_t pid' >>
> /sys/kernel/debug/tracing/synthetic_events
> # echo 'hist:keys=pid:ts0=common_timestamp.usecs if comm=="cyclictest"' >>
> /sys/kernel/debug/tracing/events/sched/sched
On Sun, 2018-04-01 at 20:31 +0200, Anton Gary Ceph wrote:
> After a few profiling and analysis, turned out that the ethertype field
> of the packets has the following distribution:
[...]
> 0.6% don't know/no opinion
Am I the only one finding the submission date and the above info
suspicious ?
On 2018-04-04 11:07, Laurent Pinchart wrote:
> Hi Daniel,
>
> On Wednesday, 4 April 2018 09:34:41 EEST Daniel Vetter wrote:
>> On Wed, Apr 4, 2018 at 12:28 AM, Laurent Pinchart wrote:
>>> On Wednesday, 28 March 2018 10:08:26 EEST Daniel Vetter wrote:
On Mon, Mar 26, 2018 at 11:24:42PM +0200,
Hi,
On Wed 04-04-18 10:24:48, Steven Whitehouse wrote:
> On 03/04/18 13:05, Jan Kara wrote:
> > Hello,
> >
> > On Sun 01-04-18 10:01:02, syzbot wrote:
> > > syzbot hit the following crash on upstream commit
> > > 10b84daddbec72c6b440216a69de9a9605127f7a (Sat Mar 31 17:59:00 2018 +)
> > > Merg
For PCIe devices the right policy is not a round robin but to use
the pcie device closer to the node. I did a prototype for that
long ago and the concept can work. Can you look into that and
also make that policy used automatically for PCIe devices?
I think that active/active makes sense for
We want to work towards phasing out the at24_platform_data structure.
There are few users and its contents can be represented using generic
device properties. Using device properties only will allow us to
significantly simplify the at24 configuration code.
Remove the at24_platform_data structure a
@@ -85,7 +121,14 @@ static blk_qc_t nvme_ns_head_make_request(struct
request_queue *q,
int srcu_idx;
srcu_idx = srcu_read_lock(&head->srcu);
- ns = nvme_find_path(head);
+ switch (head->mpath_policy) {
+ case NVME_MPATH_ROUND_ROBIN:
+ ns = nvme_fin
Linus,
please pull the latest printk changes from
git://git.kernel.org/pub/scm/linux/kernel/git/pmladek/printk.git for-linus
==
- Add info about loaded kdump kernel into the dump stack header
- Move dump-stack related code from printk.c to lib/dump_stack.c
- Write message about su
This patch series mainly deals with error handling and erased page
bitflip detection for QCOM NAND driver.
1. The error handling was missing for some of the cases so fixed
the same.
2. Add the support for taking ECC strength from ONFI parameter.
The earlier QCOM boards were coming with 4-bi
@@ -565,24 +565,24 @@ static u16 nvmet_rdma_map_sgl_keyed(struct nvmet_rdma_rsp
*rsp,
{
struct rdma_cm_id *cm_id = rsp->queue->cm_id;
u64 addr = le64_to_cpu(sgl->addr);
- u32 len = get_unaligned_le24(sgl->length);
u32 key = get_unaligned_le32(sgl->key);
i
Currently there is no error checking for raw read. For raw
reads, there won’t be any ECC failure but the operational
failures are possible so schedule the NAND_FLASH_STATUS read
after each codeword.
Signed-off-by: Abhishek Sahu
---
drivers/mtd/nand/qcom_nandc.c | 56 +
Currently the driver uses the ECC strength specified in
device tree. The ONFI or JEDEC device parameter page
contains the ‘ECC correctability’ field which indicates the
number of bits that the host should be able to correct per
512 bytes of data. The ecc correctability is assigned in
chip parameter
> I hear you. It is more complicated this way...having all these individual
> objects vs just a single "bundle" of them that represents a NIC. But, that's
> the way the DPAA2 hardware is, and we're implementing kernel support for
> the hardware as it is.
Hi Stuart
I see we are not making any pr
read_page and read_oob both calls the read_page_ecc function.
The QCOM NAND controller protect the OOB available bytes with
ECC so read errors should be checked for read_oob also. Now
this patch moves the error checking code inside read_page_ecc
so caller does not have to check explicitly for read
The BAM has 3 channels - tx, rx and command. command channel
is used for register read/writes, tx channel for data writes
and rx channel for data reads. Currently, the driver assumes the
transfer completion once it gets all the command descriptor
completed. Sometimes, there is race condition in dat
parse_read_errors can be called with only oob buf also in which
case data_buf will be NULL. If data_buf is NULL, then don’t
treat this page as completely erased in case of ECC uncorrectable
error.
Signed-off-by: Abhishek Sahu
---
drivers/mtd/nand/qcom_nandc.c | 7 +--
1 file changed, 5 inse
Add boolean function argument in parse_read_errors to identify
whether the read error has been called for complete page read or
only last codeword read. This will help in subsequent patches to
detect ECC errors in case of last codeword read.
Signed-off-by: Abhishek Sahu
---
drivers/mtd/nand/qcom
This patch does minor code reorganization for raw reads.
Currently the raw read is required for complete page but for
subsequent patches related with erased codeword bit flips
detection, only few CW should be read. So, this patch adds
helper function and introduces the read CW bitmask which
specifi
Some of the newer nand parts can have bit flips in an erased
page due to the process technology used. In this case, qpic
nand controller is not able to identify that page as an erased
page. Currently the driver calls nand_check_erased_ecc_chunk for
identifying the erased pages but this won’t work a
The NAND flash controller generates ECC uncorrectable error
first in case of completely erased page. Currently driver
applies the erased page detection logic for other operation
errors also so fix this and return EIO for other operational
errors.
Signed-off-by: Abhishek Sahu
---
drivers/mtd/nand
Reviewed-by: Sagi Grimberg
On 04/04/2018 05:21 AM, Xidong Wang wrote:
> In function jz4740_dma_probe(), the memory allocated by
> clk_get() is not released on the error path that ret, which holds
> the return value of dma_async_device_register(), is not NULL.
> This will result in a memory leak bug.
>
> Signed-off-by: Xidon
On Wed, 4 Apr 2018, Thomas Gleixner wrote:
> I'm aware how that hw-queue stuff works. But that only works if the
> spreading algorithm makes the interrupts affine to offline/not-present CPUs
> when the block device is initialized.
>
> In the example above:
>
> > > > irq 39, cpu list 0,4
>
On 26 March 2018 at 08:33, Tobin C. Harding wrote:
> The use of stack Variable Length Arrays needs to be avoided, as they
> can be a vector for stack exhaustion, which can be both a runtime bug
> (kernel Oops) or a security flaw (overwriting memory beyond the
> stack). Also, in general, as code ev
On 13 March 2018 at 15:26, Phil Edworthy wrote:
> On SD 2.00 cards we get lots of these messages:
> "mmc0: Got data interrupt 0x0002 even though no data operation was in
> progress"
> By applying the SDHCI_QUIRK2_STOP_WITH_TC quirk, the messages no longer
> happen.
>
> A single card claiming
On 3 April 2018 at 12:06, Yixun Lan wrote:
>The patches series try to enable basic eMMC support in the Meson-AXG
> platfrom.
>
>Currently HS200 mode is tested with clock running at 166MHz, since
> not all boards are stable to running 200MHz (due to tuning phase error),
> we will further i
On Wednesday 04 April 2018 12:17 PM, Sekhar Nori wrote:
> On Tuesday 03 April 2018 10:00 PM, David Lechner wrote:
>> On 04/03/2018 05:26 AM, Sekhar Nori wrote:
>>> On Friday 16 March 2018 08:22 AM, David Lechner wrote:
+static struct resource dm644x_pll1_resources[] = {
+ {
+
On 4 April 2018 at 11:05, Masahiro Yamada wrote:
> Hi.
>
> 2018-04-04 16:35 GMT+09:00 Ulf Hansson :
>> On 27 March 2018 at 11:29, Masahiro Yamada
>> wrote:
>>> Cadence sent out an errata report to their customers of this IP.
>>> This errata is not so severe, but the tune request should be sent
>>
On 27 February 2018 at 12:33, Harish Jenny K N
wrote:
> From: Andrew Gabbasov
>
> Since RPMB area is accessible via special ioctl only and boot areas
> are unlikely to contain any partitions, exclude them all from listing
> in /proc/partitions. This will hide them from various user-level
> softwa
On 29 March 2018 at 11:52, Shawn Lin wrote:
> On 2018/3/29 6:18, Alexander Kappner wrote:
>>
>> Upon module load, mmc_block allocates a bus with bus_register in
>> mmc_blk_init. This reference never gets freed during module unload.
>> Subsequent re-insertions of the module fail and BUG() is trigge
This Kconfig warning appeared after a fix to the Kconfig validation.
The GPIO_CS5535 driver depends on the MFD_CS5535 driver, but the former
is selected in places where the latter is not:
WARNING: unmet direct dependencies detected for GPIO_CS5535
Depends on [m]: GPIOLIB [=y] && (X86 [=y] || MIP
On Tue, Apr 03, 2018 at 10:43:14PM +0100, David Howells wrote:
> Alan Stern wrote:
>
> > + * Returns: 1 if @lock is locked, 0 otherwise.
> > + * However, on !CONFIG_SMP builds with !CONFIG_DEBUG_SPINLOCK,
> > + * the return value is always 0 (see include/linux/spinlock_up.h).
> > + * Therefore yo
On Thu, Mar 29, 2018 at 12:18 AM, Alexander Kappner wrote:
> Upon module load, mmc_block allocates a bus with bus_register in
> mmc_blk_init. This reference never gets freed during module unload.
> Subsequent re-insertions of the module fail and BUG() is triggered:
>
> [ 84.583342] sysfs: canno
On 20/03/18 11:48, Kishon Vijay Abraham I wrote:
> Hi Adrian,
>
> On Monday 19 March 2018 03:49 PM, Kishon Vijay Abraham I wrote:
>> Hi Adrian,
>>
>> On Monday 19 March 2018 03:30 PM, Adrian Hunter wrote:
>>> On 19/03/18 11:20, Kishon Vijay Abraham I wrote:
Hi Adrian,
On Friday 16 M
Implement preempting context switch out event as a part of
PERF_RECORD_SWITCH[_CPU_WIDE] record. The event is treated as preemption
one when task->state value of the thread being switched out is TASK_RUNNING;
Percentage of preempting and non-preempting context switches help
understanding the n
On Wed, Mar 28, 2018 at 7:27 PM, Laura Abbott wrote:
> On 03/28/2018 12:27 AM, Geert Uytterhoeven wrote:
>>
>> Hi Laura,
>>
>> On Sat, Mar 10, 2018 at 1:10 AM, Laura Abbott wrote:
>>>
>>> The new challenge is to remove VLAs from the kernel
>>> (see https://lkml.org/lkml/2018/3/7/621)
>>>
>>> This
A new set of warnings appeared in next-20180403 in some configurations
when gcc cannot see that rbd_assert(0) leads to an unreachable code
path:
drivers/block/rbd.c: In function 'rbd_img_is_write':
drivers/block/rbd.c:1397:1: error: control reaches end of non-void function
[-Werror=return-type]
d
On Wed, Apr 4, 2018 at 1:04 PM, Ilya Dryomov wrote:
> On Wed, Apr 4, 2018 at 11:49 AM, Arnd Bergmann wrote:
>> A new set of warnings appeared in next-20180403 in some configurations
>> when gcc cannot see that rbd_assert(0) leads to an unreachable code
>> path:
>>
>> drivers/block/rbd.c: In funct
Apply for a loan at 3% reply to this Email for more Info
201 - 300 of 917 matches
Mail list logo
