When loading or unloading module, it should wait for the reset task
done before it un-initializes the client, otherwise the reset task
may cause a NULL pointer reference.
Signed-off-by: Huazhong Tan
Signed-off-by: Peng Li
---
.../ethernet/hisilicon/hns3/hns3pf/hclge_main.c| 40 +
Hi Shijith,
...
> Observed good improvement for some APIs with the patch.
>
Looks good. Thanks for testing the set, I will add your tag to my patches.
> Tested-by: Shijith Thotton
>
> Thanks,
> Shijith
>
--
Regards,
Vincenzo
On 19.06.2019 17:54, Maxime Chevallier wrote:
The Header Parser allows identifying various fields in the packet
headers, used for for various kind of filtering and classification
One "for" is enough. :-)
steps.
This is a re-entrant process, where the offset in the packet header
depends o
On 20/06/19 10:55, Xiaoyao Li wrote:
>
>> However I may be wrong because I didn't review the code very closely:
>> the old code is obvious and so there is no point in changing it.
>
> you mean this part about XSS_EXIT_BITMAP? how about the other part in
> vmx_set/get_msr() in this patch?
Yes, on
From: Wanpeng Li
Raise #GP when guest read/write forbidden IA32_XSS.
Fixes: 203000993de5 (kvm: vmx: add MSR logic for XSAVES)
Reported-by: Xiaoyao Li
Reported-by: Tao Xu
Cc: Cc: Paolo Bonzini
Cc: Radim Krčmář
Cc: sta...@vger.kernel.org
Signed-off-by: Wanpeng Li
---
arch/x86/kvm/vmx/vmx.
On 19/06/2019 16:34, Douglas Gilbert wrote:
> On 2019-06-19 5:42 a.m., Marc Gonzalez wrote:
>
>> I assume sg3_utils requires CHR_DEV_SG. Is it the case?
>>
>> If so, we would just need to enable SCSI_PROC_FS when CHR_DEV_SG is enabled.
>>
>> diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfi
On Thu, 20 Jun 2019 at 16:59, Paolo Bonzini wrote:
>
> On 20/06/19 10:55, Xiaoyao Li wrote:
> >
> >> However I may be wrong because I didn't review the code very closely:
> >> the old code is obvious and so there is no point in changing it.
> >
> > you mean this part about XSS_EXIT_BITMAP? how abo
Hi Mark,
V14 patch including:
1) Patch RPC-IF back to SPI mode only instead of MFD & SPI
by MFD maintainer, Lee Jones comments.
2) Patch pm_runtime control in spi transfer.
v13 patch including:
1) rename mfd to ddata for SPI driver.
2) Patch RPC-IF devicetree for SPI and HyperFlash.
v12 patc
Add a driver for Renesas R-Car Gen3 RPC-IF SPI controller.
Signed-off-by: Mason Yang
Signed-off-by: Sergei Shtylyov
---
drivers/spi/Kconfig | 6 +
drivers/spi/Makefile | 1 +
drivers/spi/spi-renesas-rpc.c | 760 ++
3 files changed,
Dcument the bindings used by the Renesas R-Car Gen3 RPC-IF controller.
Signed-off-by: Mason Yang
---
.../devicetree/bindings/spi/spi-renesas-rpc.txt| 43 ++
1 file changed, 43 insertions(+)
create mode 100644 Documentation/devicetree/bindings/spi/spi-renesas-rpc.txt
dif
(resend because the e-mail client added HTML formatting to my last reply)
Hi Wolfram,
On Wed, 19 Jun 2019 19:18:06, Wolfram Sang wrote:
> Subject: [PATCH] mfd: da9063: occupy second I2C address, too
>
> Even though we don't use it yet, we should mark the second I2C address
> this device is list
On Wed 19-06-19 16:11:36, Sasha Levin wrote:
> On Mon, Jun 10, 2019 at 11:00:13AM +0200, Jan Kara wrote:
> > On Sat 08-06-19 07:39:14, Sasha Levin wrote:
> > > From: Jan Kara
> > >
> > > [ Upstream commit 33ec3e53e7b1869d7851e59e126bdb0fe0bd1982 ]
> >
> > Please don't push this to stable kernels
prepare_percpu_nmi() acquires lock first by irq_get_desc_lock(),
no matter whether preempt enabled or not, acquiring lock forces preempt off.
This simplifies the usage of prepare_percpu_nmi() and we don't need to
acquire extra lock or explicitly call preempt_[disable,enable]().
Signed-off-by: Lec
Hi all,
After merging the net-next tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/net/ethernet/cadence/macb_main.c:48:16: error: field 'hw' has
incomplete type
struct clk_hw hw;
^~
drivers/net/ethernet/cadence/macb_main.c:4003:21: error: variabl
On 13/06/2019 16:46:52-0600, Rob Herring wrote:
> On Sat, Jun 01, 2019 at 11:40:50PM +0200, Alexandre Belloni wrote:
> > On 17/05/2019 10:39:11-0500, Rob Herring wrote:
> > > Convert Atmel SoC bindings to DT schema format using json-schema.
> > >
> > > Cc: Mark Rutland
> > > Cc: Nicolas Ferre
>
On Mon, Jun 17, 2019 at 3:41 PM Arnd Bergmann wrote:
>
> We cannot cast a 64-bit integer to a pointer on 32-bit architectures
> without a warning:
>
> drivers/misc/habanalabs/habanalabs_ioctl.c: In function 'debug_coresight':
> drivers/misc/habanalabs/habanalabs_ioctl.c:143:23: error: cast to poin
Dear Sir,
How are you?
We are a professional factory of roller bearings in shandong province . We have
enough stock & competitive price for a range of bearing as below:
Deep groove ball bearing
Cylindrical roller bearing
Spherical roller bearing,
Angular contact ball bearing
Tapered roller bearing
gcc warns that a mising "flash" phandle node leads to undefined
behavior later:
drivers/soc/aspeed/aspeed-lpc-ctrl.c: In function 'aspeed_lpc_ctrl_probe':
drivers/soc/aspeed/aspeed-lpc-ctrl.c:201:18: error: '*((void *)&resm+8)' may be
used uninitialized in this function [-Werror=maybe-uninitializ
This patch changes the channel configuration member of the device
structure from a fixed size array to a dynamic allocated one with a size
equal to the number of channels specified in the device tree. This will
ensure a more flexibility for compatible devices.
Ex. ad7124-4 - can have 4 differentia
This patch adds the option to enable the buffered mode for positive and
negative inputs. Each option can be enabled independently.
In buffered mode, the input channel feeds into a high impedance input stage
of the buffer amplifier. Therefore, the input can tolerate significant
source impedances an
The driver limits the user to use only 4/8 differential inputs, but this
device has the option to use pseudo-differential channels. This will
increase the number of channels to be equal with the number of inputs so 8
channels for ad7124-4 and 16 for ad7124-8.
This patch removes the check between c
Convert AD7124 bindings documentation to YAML format.
Signed-off-by: Mircea Caprioru
---
.../bindings/iio/adc/adi,ad7124.yaml | 146 ++
1 file changed, 146 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7124.yaml
diff --git a/Documenta
Le 20/06/2019 à 06:12, Alastair D'Silva a écrit :
From: Alastair D'Silva
If an OpenCAPI context is to be used directly by a kernel driver, there
may not be a suitable mm to use.
The patch makes the mm parameter to ocxl_context_attach optional.
Signed-off-by: Alastair D'Silva
---
Thanks
> Is this a safety clause? What I mean is, shouldn't the hardware design make
> sure there are not two devices located on the same I2C bus with the same slave
> address?
It is more about preventing userspace to accidently access this address,
and thus the registers behind it.
signature.asc
Des
Hi Greg,
This is a pull request containing fixes to be merged to 5.2-rc6.
It contains a single minor bug fix. See the tag comment for more details.
Thanks,
Oded
The following changes since commit 6ad805b82dc5fc0ffd2de1d1f0de47214a050278:
doc: fix documentation about UIO_MEM_LOGICAL using (20
On Mon, Jun 03, 2019 at 04:30:04PM +0800, peng@nxp.com wrote:
> From: Peng Fan
>
> The ARM SMC mailbox binding describes a firmware interface to trigger
> actions in software layers running in the EL2 or EL3 exception levels.
> The term "ARM" here relates to the SMC instruction as part of the
On Thu 20-06-19 17:40:40, Minchan Kim wrote:
> > > > Pushing out a shared page cache
> > > > is possible even now but this interface gives a much easier tool to
> > > > evict shared state and perform all sorts of timing attacks. Unless I am
> > > > missing something we should be doing something sim
On Mon, Jun 03, 2019 at 04:30:05PM +0800, peng@nxp.com wrote:
> From: Peng Fan
>
> This mailbox driver implements a mailbox which signals transmitted data
> via an ARM smc (secure monitor call) instruction. The mailbox receiver
> is implemented in firmware and can synchronously return data whe
On Tuesday 18 June 2019 04:39 PM, Bitan Biswas wrote:
The usage of BUG() macro is generally discouraged in kernel, unless
it's a problem that results in a physical damage or loss of data.
This patch removes unnecessary BUG() macros and replaces the rest
with warning.
Signed-off-by: Bitan Bisw
Hi Greg,
>> First of all this is a known issue and it seems a fix is in the works,
>> but what I do not understand is why the commit causing this has not
>> simply been reverted until the fix is done, esp. for the 5.0.x
>> stable series where this was introduced in 5.0.15.
>>
>> The problem I'm t
On Wed 19-06-19 11:21:54, Ross Zwisler wrote:
> In the spirit of filemap_fdatawait_range() and
> filemap_fdatawait_keep_errors(), introduce
> filemap_fdatawait_range_keep_errors() which both takes a range upon
> which to wait and does not clear errors from the address space.
>
> Signed-off-by: Ros
On Wed, Jun 19, 2019 at 07:48:11PM +0800, Cheng-yi Chiang wrote:
> On Tue, Jun 18, 2019 at 8:12 PM Daniel Vetter wrote:
> >
> > On Tue, Jun 18, 2019 at 07:48:06PM +0800, Cheng-yi Chiang wrote:
> > > On Tue, Jun 11, 2019 at 8:35 PM Daniel Vetter wrote:
> > > >
> > > > On Tue, Jun 11, 2019 at 08:10
Hi Dan,
After merging the nvdimm tree, today's linux-next build (i386 defconfig)
failed like this:
drivers/md/dm-table.c: In function 'device_synchronous':
drivers/md/dm-table.c:897:9: error: implicit declaration of function
'dax_synchronous'; did you mean 'device_synchronous'?
[-Werror=implici
syzbot has found a reproducer for the following crash on:
HEAD commit:9939f56e usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=100c063aa0
kernel config: https://syzkaller.ap
Hi Chanwoo Choi, Saravana Kannan and Sibi Sankar,
I've also tested Sibi Sankar's patch[1] locally with mt8183-cci, and
it works fine too!
It'd be great if Sibi Sankar or anyone who is familiar with the
original design can finish this implementation. But if no one has time
to do that, I think I can
The driver limits the user to use only 4/8 differential inputs, but this
device has the option to use pseudo-differential channels. This will
increase the number of channels to be equal with the number of inputs so 8
channels for ad7124-4 and 16 for ad7124-8.
This patch removes the check between c
Hi,
On 22/05/2019 09:36:57+, Philippe Mazenauer wrote:
> Include corresponding headerfile for
> function at91_suspend_entering_slow_clock().
>
> ../arch/arm/mach-at91/pm.c:279:5: warning: no previous prototype for
> ‘at91_suspend_entering_slow_clock’ [-Wmissing-prototypes]
> int at91_suspe
On Wed, Jun 19, 2019 at 05:21:21PM +0530, Sameer Pujar wrote:
> Add DT nodes for following devices on Tegra186 and Tegra194
> * ACONNECT
> * ADMA
> * AGIC
>
> Signed-off-by: Sameer Pujar
> ---
> changes in current revision
>* updated ranges property for aconnect
>* renamed agic node
>
On Wed, Jun 19, 2019 at 05:21:22PM +0530, Sameer Pujar wrote:
> Enable ACONNECT, ADMA and AGIC devices for following platforms
> * Jetson TX2
> * Jetson Xavier
>
> Verified driver probe path and devices get registered fine.
>
> Signed-off-by: Sameer Pujar
> ---
> changes in current revision
Hi Lecopzer,
On 20/06/2019 10:12, Lecopzer Chen wrote:
> prepare_percpu_nmi() acquires lock first by irq_get_desc_lock(),
> no matter whether preempt enabled or not, acquiring lock forces preempt off.
>
> This simplifies the usage of prepare_percpu_nmi() and we don't need to
> acquire extra lock
Commit 0e56acae4b4dd4a9 ("mm: initialize MAX_ORDER_NR_PAGES at a time
instead of doing larger sections") is causing a regression on some
systems when the kernel is booted as Xen dom0.
The system will just hang in early boot.
Reason is an endless loop in get_page_from_freelist() in case the first
The range of max_hops is 0~15 and gap_count_table size is 16,
so the condition is always true, just remove it.
Signed-off-by: Ding Xiang
---
drivers/firewire/core-card.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/firewire/core-card.c b/drivers/firewire/core-car
Hey Hsin-Yi, Chanwoo
On 2019-06-20 15:02, Hsin-Yi Wang wrote:
Hi Chanwoo Choi, Saravana Kannan and Sibi Sankar,
I've also tested Sibi Sankar's patch[1] locally with mt8183-cci, and
it works fine too!
It'd be great if Sibi Sankar or anyone who is familiar with the
original design can finish this
The Header Parser allows identifying various fields in the packet
headers, used for various kind of filtering and classification
steps.
This is a re-entrant process, where the offset in the packet header
depends on the previous lookup results. This offset is represented in
the SRAM results of the
This patch adds the option to enable the buffered mode for positive and
negative inputs. Each option can be enabled independently.
In buffered mode, the input channel feeds into a high impedance input stage
of the buffer amplifier. Therefore, the input can tolerate significant
source impedances an
The driver limits the user to use only 4/8 differential inputs, but this
device has the option to use pseudo-differential channels. This will
increase the number of channels to be equal with the number of inputs so 8
channels for ad7124-4 and 16 for ad7124-8.
This patch removes the check between c
This patch changes the channel configuration member of the device
structure from a fixed size array to a dynamic allocated one with a size
equal to the number of channels specified in the device tree. This will
ensure a more flexibility for compatible devices.
Ex. ad7124-4 - can have 4 differentia
ping?
On Thu, Jun 06, 2019 at 12:26:18PM +0200, Christoph Hellwig wrote:
> Hi all,
>
> below are a couple of cleanups I came up with when trying to understand
> the blk-cgroup code.
---end quoted text---
Hi all,
After merging the akpm-current tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/base/memory.c: In function 'find_memory_block':
drivers/base/memory.c:621:43: error: 'hint' undeclared (first use in this
function); did you mean 'uint'?
return find_memory
Convert AD7124 bindings documentation to YAML format.
Signed-off-by: Mircea Caprioru
---
.../bindings/iio/adc/adi,ad7124.yaml | 146 ++
1 file changed, 146 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7124.yaml
diff --git a/Documenta
Thanks!
On Thu, Jun 20, 2019 at 5:41 PM Sibi Sankar wrote:
>
> Hey Hsin-Yi, Chanwoo
>
> On 2019-06-20 15:02, Hsin-Yi Wang wrote:
> > Hi Chanwoo Choi, Saravana Kannan and Sibi Sankar,
> >
> > I've also tested Sibi Sankar's patch[1] locally with mt8183-cci, and
> > it works fine too!
> > It'd be gr
Hi Lecopzer,
On 20/06/2019 10:12, Lecopzer Chen wrote:
> prepare_percpu_nmi() acquires lock first by irq_get_desc_lock(),
> no matter whether preempt enabled or not, acquiring lock forces preempt off.
>
> This simplifies the usage of prepare_percpu_nmi() and we don't need to
> acquire extra lock
As stated in coding-styles.rst multiline comments should be structured in a way,
that the actual comment starts on the second line of the commented portion. E.g:
/*
* Multiline comments
* should look like
* this.
*/
The comments in this file were of a format, that looked like this:
/* Multil
Since our last attempt of a few enormous commits, we ditched our changes
and started over again, this time with a lot smaller changes per patch
adressing one small thing at a time.
Sorry for the inconvenience last time!
Christian Müller (1):
drivers/staging/rtl8129u: adjust block comments
dri
On Thu, 2019-06-20 at 16:46 +0800, Tao Xu wrote:
> UMWAIT and TPAUSE instructions use IA32_UMWAIT_CONTROL at MSR index E1H
> to determines the maximum time in TSC-quanta that the processor can reside
> in either C0.1 or C0.2.
>
> This patch emulates MSR IA32_UMWAIT_CONTROL in guest and differentia
On 19/06/2019 17.04, Rob Herring wrote:
> On Fri, Jun 14, 2019 at 7:42 AM Peter Ujfalusi wrote:
>>
>>
>> On 14/06/2019 16.20, Rob Herring wrote:
>>> On Thu, Jun 13, 2019 at 2:33 PM Peter Ujfalusi
>>> wrote:
Rob,
On 13/06/2019 21.16, Rob Herring wrote:
>> +Remote PSI-L
Commit-ID: c603a309cc75f3dd018ddb20ee44c05047918cbf
Gitweb: https://git.kernel.org/tip/c603a309cc75f3dd018ddb20ee44c05047918cbf
Author: Thomas Lendacky
AuthorDate: Wed, 19 Jun 2019 18:40:57 +
Committer: Borislav Petkov
CommitDate: Thu, 20 Jun 2019 09:22:47 +0200
x86/mm: Identify th
Commit-ID: e1bfa87399e372446454ecbaeba2800f0a385733
Gitweb: https://git.kernel.org/tip/e1bfa87399e372446454ecbaeba2800f0a385733
Author: Thomas Lendacky
AuthorDate: Wed, 19 Jun 2019 18:40:59 +
Committer: Borislav Petkov
CommitDate: Thu, 20 Jun 2019 09:44:26 +0200
x86/mm: Create a wo
Hi all,
Today's linux-next merge of the akpm tree got a conflict in:
drivers/s390/char/sclp_async.c
between commit:
191fa92b3448 ("s390/sclp: remove call home support")
from the s390 tree and patch:
proc/sysctl: add shared variables for range check
from the akpm tree.
I fixed it up (
Commit-ID: ae9e13d621d6795ec1ad6bf10bd2549c6c3feca4
Gitweb: https://git.kernel.org/tip/ae9e13d621d6795ec1ad6bf10bd2549c6c3feca4
Author: Lianbo Jiang
AuthorDate: Tue, 23 Apr 2019 09:30:05 +0800
Committer: Borislav Petkov
CommitDate: Thu, 20 Jun 2019 09:54:31 +0200
x86/e820, ioport: Add
Commit-ID: 5da04cc86d1215fd9fe0e5c88ead6e8428a75e56
Gitweb: https://git.kernel.org/tip/5da04cc86d1215fd9fe0e5c88ead6e8428a75e56
Author: Lianbo Jiang
AuthorDate: Tue, 23 Apr 2019 09:30:06 +0800
Committer: Borislav Petkov
CommitDate: Thu, 20 Jun 2019 09:58:07 +0200
x86/mm: Rework ioremap
On 20/06/2019 10:39, Thierry Reding wrote:
> On Wed, Jun 19, 2019 at 05:21:21PM +0530, Sameer Pujar wrote:
>> Add DT nodes for following devices on Tegra186 and Tegra194
>> * ACONNECT
>> * ADMA
>> * AGIC
>>
>> Signed-off-by: Sameer Pujar
>> ---
>> changes in current revision
>>* updated
Commit-ID: 980621daf368f2b9aa69c7ea01baa654edb7577b
Gitweb: https://git.kernel.org/tip/980621daf368f2b9aa69c7ea01baa654edb7577b
Author: Lianbo Jiang
AuthorDate: Tue, 23 Apr 2019 09:30:07 +0800
Committer: Borislav Petkov
CommitDate: Thu, 20 Jun 2019 10:05:06 +0200
x86/crash: Add e820 re
Commit-ID: 1a79c1b8a04153c4c387518967ce851f89e22733
Gitweb: https://git.kernel.org/tip/1a79c1b8a04153c4c387518967ce851f89e22733
Author: Lianbo Jiang
AuthorDate: Tue, 30 Apr 2019 15:44:19 +0800
Committer: Borislav Petkov
CommitDate: Thu, 20 Jun 2019 10:06:46 +0200
x86/kexec: Do not map
On 2019/6/20 2:39, Stanislav Fomichev wrote:
> On 06/20, YueHaibing wrote:
>> We build vlan on top of bonding interface, which vlan offload
>> is off, bond mode is 802.3ad (LACP) and xmit_hash_policy is
>> BOND_XMIT_POLICY_ENCAP34.
>>
>> __skb_flow_dissect() fails to get information from protocol h
On 2019/06/20 14:55, Yafang Shao wrote:
> When sys_hung_task_warnings reaches 0, the hang task messages will not
> be reported any more.
It is a common mistake that sys_hung_task_warnings is already 0 when
a real problem which should be reported occurred.
>
> If the user want to get more hung ta
Commit-ID: 85784d16c2cf172cf1ebaf2390d6b7c4045d659c
Gitweb: https://git.kernel.org/tip/85784d16c2cf172cf1ebaf2390d6b7c4045d659c
Author: Lianbo Jiang
AuthorDate: Tue, 30 Apr 2019 15:44:20 +0800
Committer: Borislav Petkov
CommitDate: Thu, 20 Jun 2019 10:07:12 +0200
x86/kexec: Set the C-b
Commit-ID: 4eb5fec31e613105668a1472d5876f3d0558e5d8
Gitweb: https://git.kernel.org/tip/4eb5fec31e613105668a1472d5876f3d0558e5d8
Author: Lianbo Jiang
AuthorDate: Tue, 30 Apr 2019 15:44:21 +0800
Committer: Borislav Petkov
CommitDate: Thu, 20 Jun 2019 10:07:49 +0200
fs/proc/vmcore: Enable
On Thu, Jun 20, 2019 at 6:03 PM Tetsuo Handa
wrote:
>
> On 2019/06/20 14:55, Yafang Shao wrote:
> > When sys_hung_task_warnings reaches 0, the hang task messages will not
> > be reported any more.
>
> It is a common mistake that sys_hung_task_warnings is already 0 when
> a real problem which shoul
Fix a static code checker warning:
drivers/fmc/fmc-debug.c:155
fmc_debug_init() warn: passing zero to 'PTR_ERR'
Signed-off-by: Ding Xiang
---
drivers/fmc/fmc-debug.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/fmc/fmc-debug.c b/drivers/fmc/fmc-debug.c
inde
Hi Robert,
On Mon, Jun 03, 2019 at 10:01:55PM +0200, Robert Jarzmik wrote:
> In the patch refactoring the fw-node, the mt9m111 was broken for all
> platform_data based platforms, which were the first aim of this
> driver. Only the devicetree platform are still functional, probably
> because the te
On 20.06.19 11:42, Stephen Rothwell wrote:
> Hi all,
>
> After merging the akpm-current tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> drivers/base/memory.c: In function 'find_memory_block':
> drivers/base/memory.c:621:43: error: 'hint' undeclared (first use in t
On Wed, Jun 19, 2019 at 02:54:36PM +0200, Arnd Bergmann wrote:
> When either CONFIG_IPV6 or CONFIG_SYN_COOKIES are disabled, the kernel
> fails to build:
>
> include/linux/netfilter_ipv6.h:180:9: error: implicit declaration of function
> '__cookie_v6_init_sequence'
> [-Werror,-Wimplicit-fun
Hi Sudeep,
> Subject: Re: [PATCH V2 2/2] mailbox: introduce ARM SMC based mailbox
>
> On Mon, Jun 03, 2019 at 04:30:05PM +0800, peng@nxp.com wrote:
> > From: Peng Fan
> >
> > This mailbox driver implements a mailbox which signals transmitted
> > data via an ARM smc (secure monitor call) inst
On 2019/06/20 19:10, Yafang Shao wrote:
>>> With this patch, hung task warnings will be reset with
>>> sys_hung_task_warnings setting in evenry check interval.
>>
>> Since it is uncommon that the messages are printed for more than 10
>> times for one check_hung_uninterruptible_tasks() call, this pa
On Wed, Jun 19, 2019 at 12:45:25PM -0400, Jeff Layton wrote:
> v2: drop bogus EXPORT_SYMBOL of static function
>
> The only real difference between this set and the one I sent originally
> is the removal of a spurious EXPORT_SYMBOL in the snprintf patch.
>
> I'm mostly sending this with a wider c
From: Christian Lamparter
This patch adds a firmware check for the uPD720201K8-711-BAC-A
and uPD720202K8-711-BAA-A variant. Both of these chips are listed
in Renesas' R19UH0078EJ0500 Rev.5.00 "User's Manual: Hardware" as
devices which need a firmware in order to work as they do not have
support t
This series add support for Renesas USB controllers uPD720201 and uPD720202.
These require firmware to be loaded and in case devices have ROM those can
also be programmed if empty. If ROM is porgrammed, it runs from ROM as well.
This includes two patches from Christian which supported these contro
From: Christian Lamparter
This patch adds a firmware loader for the uPD720201K8-711-BAC-A
and uPD720202K8-711-BAA-A variant. Both of these chips are listed
in Renesas' R19UH0078EJ0500 Rev.5.00 "User's Manual: Hardware" as
devices which need the firmware loader on page 2 in order to
work as they "
Allow multiple firmware file versions in table and load them in
increasing order as we find them in the file system.
Signed-off-by: Vinod Koul
Cc: Yoshihiro Shimoda
Cc: Christian Lamparter
---
drivers/usb/host/xhci-pci.c | 39 +
1 file changed, 39 insertions
Instead of using register values and fields lets define them and
use in the driver.
Signed-off-by: Vinod Koul
Cc: Yoshihiro Shimoda
Cc: Christian Lamparter
---
drivers/usb/host/xhci-pci.c | 68 +
1 file changed, 47 insertions(+), 21 deletions(-)
diff --git
uPD720201 supports ROM and allows software to program the ROM and boot
from it. Add support for detecting if ROM is present, if so load the ROM
if not programmed earlier.
Signed-off-by: Vinod Koul
Cc: Yoshihiro Shimoda
Cc: Christian Lamparter
---
drivers/usb/host/xhci-pci.c | 358 +
Hi Enric,
For extcon part,
Acked-by: Chanwoo Choi
Best Regards,
Chanwoo choi
On 19. 6. 15. 오전 1:36, Enric Balletbo i Serra wrote:
> There is a bit of mess between cros-ec mfd includes and platform
> includes. For example, we have a linux/mfd/cros_ec.h include that
> exports the interface implem
On 6/18/2019 10:03 AM, Vinod Koul wrote:
On 17-06-19, 12:37, Sameer Pujar wrote:
On 6/13/2019 10:13 AM, Vinod Koul wrote:
On 06-06-19, 09:19, Sameer Pujar wrote:
you are really going other way around about the whole picture. FWIW that
is how *other* folks do audio with dmaengine!
I discuss
> Hi Dan,
>
> After merging the nvdimm tree, today's linux-next build (i386 defconfig)
> failed like this:
>
> drivers/md/dm-table.c: In function 'device_synchronous':
> drivers/md/dm-table.c:897:9: error: implicit declaration of function
> 'dax_synchronous'; did you mean 'device_synchronous'?
On Tue, Jun 18, 2019 at 04:09:42AM -0700, Bitan Biswas wrote:
> The usage of BUG() macro is generally discouraged in kernel, unless
> it's a problem that results in a physical damage or loss of data.
> This patch removes unnecessary BUG() macros and replaces the rest
> with warning.
>
> Signed-off
On Thu, Jun 20, 2019 at 06:11:44AM +0300, Dmitry V. Levin wrote:
> Initialize pidfd to an invalid descriptor, to fail gracefully on
> those kernels that do not implement CLONE_PIDFD and leave pidfd
> unchanged.
>
> Signed-off-by: Dmitry V. Levin
> ---
> samples/pidfd/pidfd-metadata.c | 8 ++-
On 19.06.19 07:52, Dan Williams wrote:
> Prepare the memory hot-{add,remove} paths for handling sub-section
> ranges by plumbing the starting page frame and number of pages being
> handled through arch_{add,remove}_memory() to
> sparse_{add,remove}_one_section().
>
> This is simply plumbing, small
Hi,
On 18.06.2019 12:55, Alexandre Belloni wrote:
> On 13/06/2019 15:37:06+, claudiu.bez...@microchip.com wrote:
>> From: Claudiu Beznea
>>
>> Hi,
>>
>> This series tries to improve error path for slow clock registrations
>> by adding functions to free resources and using them on failures.
>>
On Thu, 2019-06-20 at 12:19 +0300, Mircea Caprioru wrote:
> The driver limits the user to use only 4/8 differential inputs, but
> this
> device has the option to use pseudo-differential channels. This will
> increase the number of channels to be equal with the number of inputs
> so 8
> channels for
On Thu, Jun 20, 2019 at 11:22:09AM +0200, Michal Hocko wrote:
> On Thu 20-06-19 17:40:40, Minchan Kim wrote:
> > > > > Pushing out a shared page cache
> > > > > is possible even now but this interface gives a much easier tool to
> > > > > evict shared state and perform all sorts of timing attacks.
The original driver author seemed to be under the impression that a driver
cannot be removed if it does not have a .remove method. Or maybe if it is
a built-in platform driver.
This is not true. This crash can be created:
root@ubuntu:/sys/bus/platform/drivers/hisi-lpc# echo HISI0191\:00 > unbind
The traversing of io_range_list with list_for_each_entry_rcu()
is not properly protected by rcu_read_lock(), so add it.
In addition, the list traversing used in logic_pio_register_range()
does not need to use the rcu variant.
Fixes: 031e3601869c ("lib: Add generic PIO mapping method")
Signed-off-
Since the only LOGIC_PIO_INDIRECT host (hisi-lpc) now sets the ops prior
to registration, enforce this check at registration instead of in the IO
port accessors to simplify and marginally optimise the code.
A slight misalignment is also tidied.
Suggested-by: Bjorn Helgaas
Signed-off-by: John Gar
Add a function to unregister a logical PIO range.
The method used to allocate LOGIC_PIO_CPU_MMIO regions during registration
is slightly modified to ensure that we get no overlap when regions are
unregistered. This is needed because the allocation scheme assumed that no
regions are ever unregister
As reported in [1], the hisi-lpc driver has certain issues in handling
logical PIO regions, specifically unregistering regions.
This series add a method to unregister a logical PIO region, and fixes up
the driver to use them.
RCU usage in logical PIO code looks to always have been broken, so that
If, after registering a logical PIO range, the driver probe later fails,
the logical PIO range memory will be released automatically.
This causes an issue, in that the logical PIO range is not unregistered
and the released range memory may be later referenced.
Fix by unregistering the logical PIO
No longer needed, let's remove it. Also, drop the "hint" parameter
completely from "find_memory_block_by_id", as nobody needs it anymore.
Cc: Greg Kroah-Hartman
Cc: "Rafael J. Wysocki"
Cc: Andrew Morton
Cc: Stephen Rothwell
Cc: Pavel Tatashin
Cc: "mike.tra...@hpe.com"
Signed-off-by: David Hi
@Andrew: Only patch 1 and 6 changed. The patches are based on the
same state as the previous patches (replace the old ones if possible).
Some further cleanups around memory block devices. Especially, clean up
and simplify walk_memory_range(). Including some other minor cleanups.
Compiled + tested
101 - 200 of 1283 matches
Mail list logo
