From: Dou Liyang
Linux finds the CPU which has the lowest vector allocation count to spread
out the non managed interrupt across the possible target CPUs.
This common CPU finding code will also be used in managed case,
So Split it out into a helper for preparation.
Signed-off-by: Dou Liyang
-
From: Dou Liyang
Linux has spread out the non managed interrupt across the possible
target CPUs to avoid vector space exhaustion.
But, the same situation may happen on the managed interrupts.
Spread managed interrupt on allocation as well.
Fixes: a0c9259dc4e1("irq/matrix: Spread interrupts on
On Sat, 8 Sep 2018, Thomas Gleixner wrote:
> If after changing the SMT to enable a normal hotplug operation happens
> then you need to update the MSR as well.
Ah, right you are, thanks. Will fix in v5.
--
Jiri Kosina
SUSE Labs
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Markus Stockhausen
commit dc30b96ab6d569060741572cf30517d3179429a8 upstream.
ondemand_readahead() checks bdi->io_pages to cap the maximum pages
that need to be processed. This works until the
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Markus Stockhausen
commit dc30b96ab6d569060741572cf30517d3179429a8 upstream.
ondemand_readahead() checks bdi->io_pages to cap the maximum pages
that need to be processed. This works until the
On Sat, Sep 08, 2018 at 10:53:22AM +0530, Harsh 'Shandilya wrote:
> On 8 September 2018 2:40:21 AM IST, Greg Kroah-Hartman
> wrote:
> >This is the start of the stable review cycle for the 3.18.122 release.
> >There are 29 patches in this series, all will be posted as a response
> >to this one. I
On Fri, Sep 07, 2018 at 03:37:37PM -0700, Nathan Chancellor wrote:
> On Fri, Sep 07, 2018 at 11:08:54PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.14.69 release.
> > There are 89 patches in this series, all will be posted as a response
> > to this on
kmemdup has implemented the function that kzalloc() + memcpy() will
do. and we prefer to kmemdup rather than the open coded implementation.
Signed-off-by: zhong jiang
---
sound/soc/intel/skylake/skl-topology.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/sound/soc/intel/
kmemdup has implemented the function that kzalloc() + memcpy() will
do. and we prefer to use the kmemdup rather than the open coded implementation.
Signed-off-by: zhong jiang
---
sound/soc/qcom/qdsp6/q6core.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/sound/soc/q
I find the issue with the help of Coccinelle.
zhong jiang (2):
sound: q6core: Use kmemdup to replace kzalloc + memcpy
sound: skl-topology: Use kmemdup to replace kzalloc + memcpy
sound/soc/intel/skylake/skl-topology.c | 3 +--
sound/soc/qcom/qdsp6/q6core.c | 8 ++--
2 files chan
kmemdup has implemented the function that kmalloc() + memcpy() will
do. and we prefer to use the kmemdup rather than the open coded implementation.
Signed-off-by: zhong jiang
---
drivers/s390/crypto/zcrypt_msgtype6.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/dr
On Sat, 8 Sep 2018, Thomas Gleixner wrote:
> On Fri, 7 Sep 2018, Jiri Kosina wrote:
> > So I will go through the whole codepath again, but I fear your suggestion
> > would not work -- see the check for cpu_smt_control in stibp_needed(). We
> > need to see the old (or new, depending on the directi
Commit-ID: bd7b1f7cbf9cb35dab8e1b99145d07afc5b7a132
Gitweb: https://git.kernel.org/tip/bd7b1f7cbf9cb35dab8e1b99145d07afc5b7a132
Author: Andy Lutomirski
AuthorDate: Mon, 3 Sep 2018 15:59:42 -0700
Committer: Thomas Gleixner
CommitDate: Sat, 8 Sep 2018 11:20:11 +0200
x86/entry/64: Documen
Commit-ID: 98f05b5138f0a9b56022295cc1387e635b25635d
Gitweb: https://git.kernel.org/tip/98f05b5138f0a9b56022295cc1387e635b25635d
Author: Andy Lutomirski
AuthorDate: Mon, 3 Sep 2018 15:59:43 -0700
Committer: Thomas Gleixner
CommitDate: Sat, 8 Sep 2018 11:20:11 +0200
x86/entry/64: Use the
Commit-ID: 344347941aba1ec906ff50b4cdb8178c906746f2
Gitweb: https://git.kernel.org/tip/344347941aba1ec906ff50b4cdb8178c906746f2
Author: Andy Lutomirski
AuthorDate: Mon, 3 Sep 2018 15:59:44 -0700
Committer: Thomas Gleixner
CommitDate: Sat, 8 Sep 2018 11:20:12 +0200
x86/pti/64: Remove th
On Fri, Sep 07, 2018 at 12:48:57PM -0700, Dave Hansen wrote:
> +static noinline void
> +__do_page_fault(struct pt_regs *regs, unsigned long hw_error_code,
> + unsigned long address)
> +{
> + prefetchw(¤t->mm->mmap_sem);
> +
> + if (unlikely(kmmio_fault(regs, address)))
> +
On Fri, Sep 7, 2018 at 3:15 PM Pascal PAILLET-LME wrote:
>
> From: pascal paillet
>
> The stpmic1 PMIC embeds several regulators and witches with
> different capabilities.
While fixing Kconfig, as Mark suggest, would you mind to fix also the
typo s/witches/switches/ in the commit message?
Anton
Hi, Thomas
Can you pick up the patch?
Thanks
zhong jiang
On 2018/8/1 0:21, zhong jiang wrote:
> kmem_cache_destroy/mempool_destroy has taken null check into account.
> so remove the redundant check.
>
> Signed-off-by: zhong jiang
> ---
> lib/sg_pool.c | 7 +++
> 1 file changed, 3 insertion
The defined constant RTL8190_CPU_START_OFFSET is not used in the code
so has been removed. This is a coding style change which should have
no impact on runtime code execution.
Signed-off-by: John Whitmore
---
drivers/staging/rtl8192u/r819xU_firmware.h | 1 -
1 file changed, 1 deletion(-)
diff -
The MACRO GET_COMMAND_PACKET_FRAG_THRESHOLD causes a number of
checkpatch issues so has been refactored to use braces around the
parameter 'v' to avoid precedence issues, and to add spaces around
operators.
These changes are coding style changes which should have no impact
on runtime code executio
Remove the typedef directive from enumerated type opt_rst_type_e,
this change clears the checkpatch issue with defining new types in
the code.
This is a coding style change which should not impact runtime
code execution.
Signed-off-by: John Whitmore
---
drivers/staging/rtl8192u/r819xU_firmware.
This short series of patches just clears simple checkpatch issues
with the header file r819xU_firmware.h.
John Whitmore (4):
staging:rtl8192u: Remove unused RTL8190_CPU_START_OFFSET - Style
staging:rtl8192u: Refactor GET_COMMAND_PACKET_FRAG_THRESHOLD - Style
staging:rtl8192u: Remove typedef
Remove the typedef directive from enumerated type firmware_init_step_e
this clears the checkpatch issue with adding new types to the code.
This is a coding style change which should have no impact on runtime
code execution.
Signed-off-by: John Whitmore
---
drivers/staging/rtl8192u/r819xU_firmwa
Linus,
The following changes since commit 57361846b52bc686112da6ca5368d11210796804:
Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm tags/for-linus
for you to fetch changes up to bdf7ffc89922a52a4f08a12f7421ea24bb7
On Sat, 8 Sep 2018, zhong jiang wrote:
> Hi, Thomas
>
> Can you pick up the patch?
I'm not picking up patches for lib/sg_pool. Why would I?
mempool_destroy has taken null pointer check into account. so remove the
redundant check.
Signed-off-by: zhong jiang
---
drivers/s390/scsi/zfcp_aux.c | 21 +++--
1 file changed, 7 insertions(+), 14 deletions(-)
diff --git a/drivers/s390/scsi/zfcp_aux.c b/drivers/s390/scsi/zfcp_a
On Sat, 8 Sep 2018, Dou Liyang wrote:
> +/* Find the best CPU which has the lowest vector allocation count */
> +static int matrix_find_best_cpu(struct irq_matrix *m,
> + const struct cpumask *msk, int *best_cpu)
> +{
> + unsigned int cpu, maxavl = 0;
> + struct
> Will feels strongly (and Linus agrees) that the LKMM should not require
> ordinary acquire and release to be any stronger than RCpc.
>
> The issue that Andrea raised has to do with qspinlock, qrwlock, and
> mcs_spinlock, which are implemented using smp_cond_load_acquire()
> instead of RMW-acqu
Commit-ID: 86635715ee4228ded59f662dab36e9732b9c978f
Gitweb: https://git.kernel.org/tip/86635715ee4228ded59f662dab36e9732b9c978f
Author: Andy Lutomirski
AuthorDate: Mon, 3 Sep 2018 15:59:44 -0700
Committer: Thomas Gleixner
CommitDate: Sat, 8 Sep 2018 11:53:16 +0200
x86/pti/64: Remove th
On 2018/9/8 17:46, Thomas Gleixner wrote:
> On Sat, 8 Sep 2018, zhong jiang wrote:
>> Hi, Thomas
>>
>> Can you pick up the patch?
> I'm not picking up patches for lib/sg_pool. Why would I?
>
I am sorry for that. I regard you as maintainer for lib/sg_pool mistakely.
but I can get maintainer inform
On Sat, 8 Sep 2018, Dou Liyang wrote:
> Spread managed interrupt on allocation as well.
>
> Fixes: a0c9259dc4e1("irq/matrix: Spread interrupts on allocation")
No. This is an enhancement and not a fix.
> - cpumask_and(vector_searchmask, vector_searchmask, affmsk);
> - cpu = cpumask_first(
On Sat, 8 Sep 2018, zhong jiang wrote:
> On 2018/9/8 17:46, Thomas Gleixner wrote:
> > On Sat, 8 Sep 2018, zhong jiang wrote:
> >> Hi, Thomas
> >>
> >> Can you pick up the patch?
> > I'm not picking up patches for lib/sg_pool. Why would I?
> >
> I am sorry for that. I regard you as maintainer for
On Fri, 31 Aug 2018, Joerg Roedel wrote:
> On Fri, Aug 31, 2018 at 07:12:44AM +0300, Meelis Roos wrote:
> > > Thanks for the report! I'll try to reproduce the problem tomorrow and
> > > investigate it. Can you please check if any of the kernel configurations
> > > that show the bug has CONFIG_X8
On 2018/9/8 18:21, Thomas Gleixner wrote:
> On Sat, 8 Sep 2018, zhong jiang wrote:
>
>> On 2018/9/8 17:46, Thomas Gleixner wrote:
>>> On Sat, 8 Sep 2018, zhong jiang wrote:
Hi, Thomas
Can you pick up the patch?
>>> I'm not picking up patches for lib/sg_pool. Why would I?
>>>
>> I am
Commit-ID: 9bc4f28af75a91aea0ae383f50b0a430c4509303
Gitweb: https://git.kernel.org/tip/9bc4f28af75a91aea0ae383f50b0a430c4509303
Author: Nadav Amit
AuthorDate: Sun, 2 Sep 2018 11:14:50 -0700
Committer: Thomas Gleixner
CommitDate: Sat, 8 Sep 2018 12:30:36 +0200
x86/mm: Use WRITE_ONCE() w
Commit-ID: 4a60aa05a0634241ce17f957bf9fb5ac1eed6576
Gitweb: https://git.kernel.org/tip/4a60aa05a0634241ce17f957bf9fb5ac1eed6576
Author: Allan Xavier
AuthorDate: Fri, 7 Sep 2018 08:12:01 -0500
Committer: Thomas Gleixner
CommitDate: Sat, 8 Sep 2018 12:33:01 +0200
objtool: Support per-fun
ARRAY_SIZE has implemented its function. we prefer to use the function
rather than the open code.
Signed-off-by: zhong jiang
---
drivers/s390/char/vmlogrdr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/s390/char/vmlogrdr.c b/drivers/s390/char/vmlogrdr.c
index 069b
I find the issue with the help of Coccinelle.
zhong jiang (2):
s390: vmlogrdr: Use ARRAY_SIZE instead of reimplementing its function
s390: qeth_core_mpc: Use ARRAY_SIZE instead of reimplementing its
function
drivers/s390/char/vmlogrdr.c | 2 +-
drivers/s390/net/qeth_core_mpc.c | 7 ++
ARRAY_SIZE has implemented its function. we prefer to use the function
rather than the open code.
Signed-off-by: zhong jiang
---
drivers/s390/net/qeth_core_mpc.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/s390/net/qeth_core_mpc.c b/drivers/s390/net/qeth_co
On Thu, 6 Sep 2018, Christoph Hellwig wrote:
> Just as before: NAK to entirely pointless abstractions. Please stop
> beating the dead horse.
I disagree. These interrupts very well fit into the percpu interupt
mechanics and that allows them to be handled by all the generic mechanisms
as any othe
On Mon, 3 Sep 2018, Eric W. Biederman wrote:
> SEND_SIG_FORCED has two functions. It forces a pid namespace init to
> receive a signal it would ordinarily ignore, and it causes a siginfo to
> not be allocated for a signal.
>
> This patchset makes __send_signal a little bit smarter so that it ca
From: Sean Wang
Certain SoC own multiple register base for accessing each pin groups,
it's easy to be done with extend struct mtk_pin_field_calc to support
the kind of SoC such as MT8183.
Signed-off-by: Sean Wang
---
drivers/pinctrl/mediatek/pinctrl-moore.c | 30 +++-
d
From: Sean Wang
Almost all MediaTek SoCs apply the exact same logic to build eint, so move
the common functions into pinctrl-mtk-common-v2.c to allow each new pinctrl
driver to reuse them. Also, add a protection checker on hw->soc->eint_hw to
avoid invalid memory access when there's certain SoC n
From: Sean Wang
Extend the advanced pull based on the legacy bias plus additional r0 and r1
to tweak the resistor level.
Signed-off-by: Zhiyong Tao
Signed-off-by: Sean Wang
---
drivers/pinctrl/mediatek/pinctrl-mtk-common-v2.c | 37
1 file changed, 32 insertions(+), 5
From: Zhiyong Tao
This patch provides the advanced pull for I2C used pins on MT8183.
Signed-off-by: Zhiyong Tao
Signed-off-by: Sean Wang
---
drivers/pinctrl/mediatek/pinctrl-mt8183.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers/pinctrl/mediatek/pinctrl
From: Sean Wang
v2 and changes since v1:
add new patches
* Add additional patch 17 to 22 to support MT8183 SoC
update the existing patches
* Patch 2: Removed unnecessary blank line and headers included.
* Patch 4: Extended the size eint number can hold since it's possible more than
254 pins in
From: Zhiyong Tao
Add pinctrl-paris core that implements vendor dt-binding which MediaTek
tablet, box and smartphone-based SoCs such as MT81xx, MT27xx, and MT67xx
SoCs really want to depend on. The driver is just completely rewritten
according to pinctrl-mtk-common.c but uses the new logic from
p
From: Zhiyong Tao
Add MT8183 pinctrl driver based on MediaTek pinctrl-paris core.
Signed-off-by: Zhiyong Tao
Signed-off-by: Sean Wang
---
drivers/pinctrl/mediatek/Kconfig |7 +
drivers/pinctrl/mediatek/Makefile |1 +
drivers/pinctrl/mediatek/pinctrl-mt8183.c
From: Sean Wang
all use pin descriptor instead in pinctrl-mtk-common-v2.c for the
consistency and extensibility.
Signed-off-by: Sean Wang
---
drivers/pinctrl/mediatek/pinctrl-moore.c | 66 +---
drivers/pinctrl/mediatek/pinctrl-mtk-common-v2.c | 76 +-
From: Sean Wang
Because the pincrl-mtk-common.c is an implementation for per-pin binding,
its pin descriptor includes more information than pinctrl-mtk-common-v2
so far can support. So, we complement these data before writing a driver
using pincrl-mtk-common-v2.c for per-pin binding. By the way,
From: Sean Wang
This patch adds members sz_reg fixed in struct mtk_pin_field_calc
- The 'fixed' is used to represent the consecutive pins share the same
bits within the same register with the 1st pin so that it can largely
reduce the entry size a bit.
- The 'sz_reg' is used to indicate the rang
From: Sean Wang
Just add eint support to MT8183 pinctrl driver as usual as
happens on the other SoCs.
Signed-off-by: Sean Wang
---
drivers/pinctrl/mediatek/pinctrl-mt8183.c | 8
drivers/pinctrl/mediatek/pinctrl-paris.c | 22 ++
2 files changed, 30 insertions(+)
From: Sean Wang
Adding MT7623 pinctrl driver based on generic pinctrl binding, that is
good example and demonstrates how to port any other MediaTek SoCs
pinctrl-moore core when people really would like to use the generic
pinctrl binding to support these MediaTek SoCs.
Signed-off-by: Ryder Lee
S
From: Sean Wang
It's usual and not an error for there's some register not supported by a
certain SoC or a pin so that in the case we have to adjust the message to
print and the error code to get rid of unnecessary false alarm.
Signed-off-by: Sean Wang
---
drivers/pinctrl/mediatek/pinctrl-mtk-c
The iterator in for_each_set_bit is never null, therefore, remove
the redundant conditional judgment.
Signed-off-by: zhong jiang
---
drivers/iio/humidity/am2315.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/iio/humidity/am2315.c b/drivers/iio/humidity/am2315.c
i
Hi , I have fixed error space required before the open parenthesis in
drivers/bluetooth/hci_serdev.c
>From 084feec211eb99e6658d9ad11152406348716ced Mon Sep 17 00:00:00 2001
From: Jagdish Tirumala
Date: Sat, 8 Sep 2018 03:36:34 -0700
Subject: [PATCH] fixed error space required before the open pare
The iterator in for_each_cache is never null, therefore, remove
the redundant null pointer check.
Signed-off-by: zhong jiang
---
drivers/md/bcache/super.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/md/bcache/super.c b/drivers/md/bcache/super.c
index 9
RE: Privileged and Confidential:
Here I brought a potential Business Proposal at your door step for
consideration.
I have a client that is interested to Invest in your Country and would like to
engage you and your company on this project. The Investment Amount is valued at
US$132 million.
If
On Tue, 4 Sep 2018, Fenghua Yu wrote:
>
> Signed-off-by: Xiaochen Shen
> Signed-off-by: Fenghua Yu
Sigh. Am I supposed to assume that this patch is authored by Xiaochen?
Come on, you are around long enough to do it proper.
Thanks,
tglx
On Wed, 29 Aug 2018, Baoquan He wrote:
> In memory KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate the
> initial size of the direct mapping region. This is right in the
> old code where __PHYSICAL_MASK_SHIFT was equal to MAX_PHYSMEM_BITS,
> 46bit, and only 4-level mode was supported.
>
> Later
Refactor switch cases in SwLedControlMode1() to reduce
indentation level. Also clears line over 80 characters
checkpatch warnings.
Suggested-by: Joe Perches
Signed-off-by: Michael Straube
---
drivers/staging/rtl8188eu/core/rtw_led.c | 223 ---
1 file changed, 113 insertions(
Wrap lines over 80 characters where appropriate to
clear checkpatch warnings.
Signed-off-by: Michael Straube
---
drivers/staging/rtl8188eu/core/rtw_led.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/rtl8188eu/core/rtw_led.c
b/drivers/staging/rtl81
Remove unnecessary parentheses from conditionals.
Also clears 'Alignment should match open parenthesis'
checkpatch issue.
Signed-off-by: Michael Straube
---
drivers/staging/rtl8188eu/core/rtw_led.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/rtl818
On Mon, 27 Aug 2018, Rob Herring wrote:
> In preparation to remove the node name pointer from struct device_node,
> convert printf users to use the %pOFn format specifier.
>
> Cc: Thomas Gleixner
> Cc: Jason Cooper
> Cc: Marc Zyngier
> Cc: linux-arm-ker...@lists.infradead.org
> Signed-off-by:
On Sat, Sep 08, 2018 at 06:57:36PM +0800, zhong jiang wrote:
> The iterator in for_each_set_bit is never null, therefore, remove
> the redundant conditional judgment.
>
> Signed-off-by: zhong jiang
> ---
> drivers/iio/humidity/am2315.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
On Sat, 8 Sep 2018 18:26:27 +0800, zhong jiang wrote:
> ARRAY_SIZE has implemented its function. we prefer to use the function
> rather than the open code.
>
> Signed-off-by: zhong jiang
> ---
> drivers/s390/char/vmlogrdr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
debugfs_remove has taken the IS_ERR_OR_NULL into account. Just
remove the unnecessary condition.
Signed-off-by: zhong jiang
---
drivers/md/bcache/super.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/md/bcache/super.c b/drivers/md/bcache/super.c
index 2d26f9e..a3d
On Sat, 8 Sep 2018 18:26:28 +0800, zhong jiang wrote:
> ARRAY_SIZE has implemented its function. we prefer to use the function
> rather than the open code.
>
> Signed-off-by: zhong jiang
> ---
> drivers/s390/net/qeth_core_mpc.c | 7 ++-
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
>
Hi everybody,
my router firmware concatenates two identical flash chips into a single
mtd using mtd_concat_create(), and sets up partitions in a way where one
of them crosses the chip boundary. When porting OpenWRT support for the
board from a mach-file based setup to a device-tree based one, I fo
Document virtual mtd-concat device bindings.
Signed-off-by: Bernhard Frauendienst
---
.../devicetree/bindings/mtd/mtd-concat.txt| 36 +++
1 file changed, 36 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mtd/mtd-concat.txt
diff --git a/Documentation/devi
Add function to retrieve a mtd device by its OF node. Since drivers can
assign arbitrary names to mtd devices in the absence of a label
property, there is no other reliable way to retrieve a mtd device for a
given OF node.
Signed-off-by: Bernhard Frauendienst
Reviewed-by: Miquel Raynal
---
driv
Hi Takashi,
> Takashi Iwai hat am 4. September 2018 um 17:58 geschrieben:
>
>
> Hi,
>
> since I had an opportunity to play with RPi3B+ recently, I took a look
> at the existing bcm2835-audio driver code and was amused very much :)
>
> So here is the result, a cleanup and fix patch series.
>
Some mtd drivers like physmap variants have support for concatenating
multiple mtd devices, but there is no generic way to define such a
concat device from within the device tree.
This is useful for some SoC boards that use multiple flash chips as
memory banks of a single mtd device, with partitio
Hi,
> Takashi Iwai hat am 4. September 2018 um 17:58 geschrieben:
>
>
> Only a few of them are really needed.
>
> Signed-off-by: Takashi Iwai
> ---
> .../vc04_services/bcm2835-audio/bcm2835-ctl.c | 15 ---
I think this patch and patch #23 could be merge in case a new series i
On 09/08/18 at 02:10pm, Thomas Gleixner wrote:
> On Wed, 29 Aug 2018, Baoquan He wrote:
>
> > In memory KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate the
> > initial size of the direct mapping region. This is right in the
> > old code where __PHYSICAL_MASK_SHIFT was equal to MAX_PHYSMEM_BITS,
On 2018/08/22 1:04, Johannes Weiner wrote:
> When the memcg OOM killer runs out of killable tasks, it currently
> prints a WARN with no further OOM context. This has caused some user
> confusion.
>
> Warnings indicate a kernel problem. In a reported case, however, the
> situation was triggered by
Hi,
> Takashi Iwai hat am 4. September 2018 um 17:58 geschrieben:
>
>
> The chip->audio_mutex is used basically for protecting the opened
> stream assignment, and the prepare callback is irrelevant with it.
>
> Signed-off-by: Takashi Iwai
> ---
> drivers/staging/vc04_services/bcm2835-audio/b
debugfs_remove_recursive has taken IS_ERR_OR_NULL into account. So just
remove the condition check before debugfs_remove_recursive.
Signed-off-by: zhong jiang
---
drivers/md/bcache/debug.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/md/bcache/debug.c b/drivers/m
On Thu, 6 Sep 2018 13:27:34 +
Manish Narani wrote:
> Hi Jonathan,
>
> Thanks for the review!
>
> > -Original Message-
> > From: Jonathan Cameron [mailto:ji...@kernel.org]
> > Sent: Sunday, September 2, 2018 11:45 PM
> > To: Manish Narani
> > Cc: knaac...@gmx.de; l...@metafoo.de; pm
This patch fixes some spelling typos found in printk messages.
Signed-off-by: Masanari Iida
---
drivers/dma/ep93xx_dma.c | 6 +++---
drivers/gpu/drm/amd/amdgpu/mxgpu_vi.c | 2 +-
drivers/gpu/drm/drm_kms_helper_common.c| 2 +-
drivers/gpu/drm/sel
On Thu, 6 Sep 2018 15:19:29 +
Manish Narani wrote:
> Hi Jonathan,
>
> Thanks a lot for the review. Please see my response inline.
Hi Manish,
Just one thing to think about. (and I'm not that great about this
myself :) Please look to crop out irrelevant text. It saves
time when people are
I, Mikhail Fridman have selected you specifically as one of my
beneficiaries for my Charitable Donation,
Check the link below for confirmation:
https://www.rt.com/business/343781-mikhail-fridman-will-charity/
I await your earliest response.
Best Regards,
Mikhail Fridman.
---
On Sat, Sep 08, 2018 at 10:36:06PM +0900, Tetsuo Handa wrote:
> On 2018/08/22 1:04, Johannes Weiner wrote:
> > When the memcg OOM killer runs out of killable tasks, it currently
> > prints a WARN with no further OOM context. This has caused some user
> > confusion.
> >
> > Warnings indicate a kern
debugfs_remove has taken the IS_ERR_OR_NULL into account. Just
remove the unnecessary condition.
Signed-off-by: zhong jiang
---
drivers/infiniband/hw/usnic/usnic_debugfs.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/infiniband/hw/usnic/usnic_debugfs.c
b/drivers
On 09/07/2018 02:10 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.122 release.
There are 29 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On Fri, Sep 07, 2018 at 10:58:16PM +0300, Alexey Dobriyan wrote:
> On Thu, Sep 06, 2018 at 03:48:49PM -0700, a...@linux-foundation.org wrote:
> > - {"kmalloc-1024", 1024}, {"kmalloc-2048", 2048},
> > - {"kmalloc-4096", 4096}, {"kmalloc-8192", 8192
On Tue, 04 Sep 2018 20:23:57 +0100
Afonso Bordado wrote:
> On Fri, 2018-08-31 at 17:35 +0200, Tomasz Duszynski wrote:
> > On Thu, Aug 30, 2018 at 10:18:22PM +0100, Afonso Bordado wrote:
> > > FXAS21002C is a 3 axis gyroscope with integrated temperature sensor
Just a quick hint to make my life
On Thu, 6 Sep 2018 14:04:52 -0700
Matthias Kaehlcke wrote:
> The documentation of Qualcomm's SPMI PMIC voltage ADC claims that the
> 'reg' property consists of two values, the SPMI address and the length
> of the controller's registers. However the SPMI bus to which it is added
> specifies "#siz
On Thu, 6 Sep 2018 14:22:06 -0700
Matthias Kaehlcke wrote:
> On Thu, Sep 06, 2018 at 02:10:43PM -0700, Doug Anderson wrote:
> > Hi,
> >
> > On Thu, Sep 6, 2018 at 2:04 PM, Matthias Kaehlcke
> > wrote:
> > > Add a channel node for the die temperature to the ADC.
> > >
> > > Signed-off-by: Mat
On 2018/09/08 22:57, Johannes Weiner wrote:
> On Sat, Sep 08, 2018 at 10:36:06PM +0900, Tetsuo Handa wrote:
>> Due to commit d75da004c708c9fc ("oom: improve oom disable handling") and
>> commit 3100dab2aa09dc6e ("mm: memcontrol: print proper OOM header when
>> no eligible victim left"), all
>>
>>
On Sat, 8 Sep 2018 17:59:13 +0530
Himanshu Jha wrote:
> On Sat, Sep 08, 2018 at 06:57:36PM +0800, zhong jiang wrote:
> > The iterator in for_each_set_bit is never null, therefore, remove
> > the redundant conditional judgment.
> >
> > Signed-off-by: zhong jiang
> > ---
> > drivers/iio/humidity
The two drivers implementing these both gained proper compat_ioctl()
handlers a long time ago with commits bb6c8d8fa9b5 ("HID: hiddev:
Add 32bit ioctl compatibilty") and ae5e49c79c05 ("HID: hidraw: add
compatibility ioctl() for 32-bit applications."), so the lists in
fs/compat_ioctl.c are no longer
The KD* family of ioctls is implemented in two drivers:
drivers/tty/vt and drivers/s390/char/tty3270.c. Both of them
have compat handlers for all their ioctl commands, so translation
in fs/compat_ioctl.c is never used.
Commit fb07a5f857ac ("compat_ioctl: remove all VT ioctl handling")
removed the
On Tue, 4 Sep 2018 17:11:31 +0300
Stefan Popa wrote:
> This patch restructures the existing adxl372 driver by adding a module for
> SPI and a header file, while the baseline module deals with the chip-logic.
>
> This is a necessary step, as this driver should support in the future
> a similar de
The SNDCTL_* and SOUND_* commands are the old OSS user interface.
I checked all the sound ioctl commands listed in fs/compat_ioctl.c
to see if we still need the translation handlers. Here is what I
found:
- sound/oss/ is (almost) gone from the kernel, this is what actually
needed all the transl
On Tue, 4 Sep 2018 17:12:32 +0300
Stefan Popa wrote:
> The adxl372 is designed to communicate in either SPI or I2C protocol. It
> autodetects the format being used, requiring no configuration control to
> select the format.
>
> Signed-off-by: Stefan Popa
Applied.
Thanks,
Jonathan
> ---
> MAI
Since commit 07d106d0a33d ("vfs: fix up ENOIOCTLCMD error handling"),
we don't warn about unhandled compat-ioctl command code any more, but
just return the same error that a native file descriptor returns when
there is no handler.
This means the IGNORE_IOCTL() annotations are completely useless an
On Tue, 4 Sep 2018 17:13:14 +0300
Stefan Popa wrote:
> The adxl372 is designed to communicate in either SPI or I2C protocol.
> This patch adds the documentation of device tree bindings for adxl372
> I2C.
>
> Signed-off-by: Stefan Popa
Applied.
Thanks,
Jonathan
> ---
> Documentation/devicetr
These are all handled by the random driver, so instead of listing
each ioctl, we can just use the same function to deal with both
native and compat commands.
Signed-off-by: Arnd Bergmann
---
drivers/char/random.c | 1 +
fs/compat_ioctl.c | 7 ---
2 files changed, 1 insertion(+), 7 deleti
The joystick driver already handles these just fine, so
the entries in the table are not needed any more.
Signed-off-by: Arnd Bergmann
---
fs/compat_ioctl.c | 8
1 file changed, 8 deletions(-)
diff --git a/fs/compat_ioctl.c b/fs/compat_ioctl.c
index eb29188d1dbb..23c0406d8b30 100644
--
1 - 100 of 175 matches
Mail list logo