Hi all,
Changes since 20191017:
The clk tree gained a conflict against the imx-mxs tree.
The pm tree gained a conflict against the printk tree.
The tip tree gained a conflict against the net-next tree.
The char-misc tree gained a conflict against the char-misc.current tree.
The akpm tree gain
On Thu 2019-10-17 21:24:19, Alexei Starovoitov wrote:
> On Fri, Oct 18, 2019 at 11:18:48AM +0800, Kefeng Wang wrote:
> > For kernel logging macro, pr_warning is completely removed and
> > replaced by pr_warn, using pr_warn in tools lib bpf for symmetry
> > to kernel logging macro, then we could dro
Resolved: ERROR: else should follow close brace '}'
Signed-off-by: Chandra Annamaneni
---
Previous versions of these patches were not split into different
patches, did not have different patch numbers and did not have the
keyword staging. The previous version of this patch had the wrong
descrip
On 18/10/19 5:46 pm, Christophe Leroy wrote:
Le 17/10/2019 à 09:36, Andrew Donnellan a écrit :
On 10/9/19 7:16 pm, Christophe Leroy wrote:
+#if defined(CONFIG_VMAP_STACK) && CONFIG_THREAD_SHIFT < PAGE_SHIFT
+#define THREAD_SHIFT PAGE_SHIFT
+#else
#define THREAD_SHIFT CONFIG_TH
Hi Mika,
> On Sep 23, 2019, at 16:28, Mika Westerberg
> wrote:
>
> On Mon, Sep 23, 2019 at 11:12:42AM +0300, Mika Westerberg wrote:
>> Regarding suggestion of unbinding PCI drivers without
>> pci_lock_rescan_remove() hold, I haven't looked it too closely but I
>> think we need to take that lock
On 18.10.2019 06:30, Viresh Kumar wrote:
> On 17-10-19, 12:27, Marek Szyprowski wrote:
>> All the drivers, which use the OPP framework control regulators, which
>> are already enabled. Typically those regulators are also system critical,
>> due to providing power to CPU core or system buses. It t
On Fri, Oct 18, 2019 at 11:45:54AM +0800, Zhenzhong Duan wrote:
> If 'idle=nomwait' is specified or process matching what's in
> processor_idle_dmi_table, we should't use MWAIT at bootup stage before
> cpuidle driver loaded, even if it's preferred by default on Intel.
>
> Add a check so that HALT
add support for Amlogic A1 clock driver, the clock includes
three parts: peripheral clocks, pll clocks, CPU clocks.
sys pll and CPU clocks will be sent in next patch.
Changes since v1 at [1]:
-place A1 config alphabetically
-add actual reason for RO ops, CLK_IS_CRITICAL, CLK_IGNORE_UNUSED
-separa
The A1 PLL design is different with previous SoCs. The PLL
internal analog modules Power-on sequence is different
with previous, and thus requires a strict register sequence to
enable the PLL. Unlike the previous series, the maximum frequency
is 6G in G12A, for A1 the maximum is 1536M.
Signed-off-
The Amlogic A1 clock includes three drivers:
peripheral clocks, pll clocks, CPU clocks.
sys pll and CPU clocks will be sent in next patch.
Unlike the previous series, there is no EE/AO domain
in A1 CLK controllers.
Signed-off-by: Jian Hu
---
drivers/clk/meson/Kconfig | 10 +
drivers/clk/meso
On Thu, Oct 17, 2019 at 11:44:45PM +0200, Borislav Petkov wrote:
> On Thu, Oct 17, 2019 at 09:31:30PM +, Luck, Tony wrote:
> > That sounds like the right short term action.
> >
> > Depending on what we end up with from Srinivas ... we may want
> > to reconsider the severity. The basic premise
Add the documentation to support Amlogic A1 clock driver,
and add A1 clock controller bindings.
Signed-off-by: Jian Hu
---
.../devicetree/bindings/clock/amlogic,a1-clkc.yaml | 143 +
include/dt-bindings/clock/a1-clkc.h| 98 ++
include/dt-bindings/
On Thu, Oct 17, 2019 at 11:39:17AM -0700, Darrick J. Wong wrote:
> Looks ok, but need fixes tag. Also, might it be wise to split off the
> ext4 section into a separate patch so that it can be backported
> separately?
I'll let Dave handle all that. I've just pulled it in here as multiple
patches
On 2019-10-17 21:00, Stephen Boyd wrote:
Quoting Sai Prakash Ranjan (2019-10-11 06:40:13)
On 2019-10-11 19:04, Marc Zyngier wrote:
> On Fri, 11 Oct 2019 18:47:39 +0530
> Sai Prakash Ranjan wrote:
>
>> Hi Mark,
>>
>> Thanks a lot for the detailed explanations, I did have a look at
all
>> the v
On 2019.10.10 Rafael J. Wysocki wrote:
> There are a few issues related to the handling of disabled idle states in the
> TEO (Timer-Events-Oriented) cpuidle governor which are addressed by this
> series.
>
> The application of the entire series is exactly equivalent to the testing
> patch
> at ht
Adrian,
On 16/10/19 5:46 PM, Faiz Abbas wrote:
> Adrian,
>
> On 15/10/19 7:15 PM, Adrian Hunter wrote:
>> On 15/10/19 10:55 AM, Faiz Abbas wrote:
>>> Hi,
>>>
>>> On 15/10/19 12:08 AM, Faiz Abbas wrote:
Add a write memory barrier to make sure that descriptors are actually
written to memo
On Fri, Oct 18, 2019 at 6:44 AM Dan Robertson wrote:
>
> Add a IIO driver for the Bosch BMA400 3-axes ultra-low power accelerometer.
> The driver supports reading from the acceleration and temperature
> registers. The driver also supports reading and configuring the output data
> rate, oversamplin
On 18/10/19 10:22 AM, Faiz Abbas wrote:
> Adrian,
>
> On 16/10/19 5:46 PM, Faiz Abbas wrote:
>> Adrian,
>>
>> On 15/10/19 7:15 PM, Adrian Hunter wrote:
>>> On 15/10/19 10:55 AM, Faiz Abbas wrote:
Hi,
On 15/10/19 12:08 AM, Faiz Abbas wrote:
> Add a write memory barrier to make su
On Fri, Oct 18, 2019 at 8:02 AM Viresh Kumar wrote:
>
> On 18-10-19, 06:55, Sudeep Holla wrote:
> > On Thu, Oct 17, 2019 at 11:26:54PM +0200, Rafael J. Wysocki wrote:
> > > On Thu, Oct 17, 2019 at 9:36 PM Rafael J. Wysocki
> > > wrote:
> > > >
> > > > On Thu, Oct 17, 2019 at 6:35 PM Sudeep Holla
On Wed, Oct 16, 2019 at 6:35 PM James Bottomley
wrote:
> > The documentation says that krng is suitable for key generation.
> > Should the documentation changed to state that it is unsuitable?
>
> How do you get that from the argument above? The krng is about the
> best we have in terms of unpre
On Fri 18-10-19 06:32:22, Naoya Horiguchi wrote:
> On Fri, Oct 18, 2019 at 08:06:35AM +0200, Michal Hocko wrote:
> > On Fri 18-10-19 02:19:06, Naoya Horiguchi wrote:
> > > On Thu, Oct 17, 2019 at 08:27:59PM +0200, Michal Hocko wrote:
> > > > On Thu 17-10-19 14:07:13, Qian Cai wrote:
> > > > > On Th
Nvidia proprietary driver doesn't support runtime power management, so
when a user only wants to use the integrated GPU, it's a common practice
to let dGPU not to bind any driver, and let its upstream port to be
runtime suspended. At the end of runtime suspension the port uses
platform power manage
A driver may want to know the existence of _PR3, to choose different
runtime suspend behavior. A user will be add in next patch.
This is mostly the same as nouveau_pr3_present().
Reported-by: kbuild test robot
Signed-off-by: Kai-Heng Feng
---
v6:
- Only define the function when CONFIG_ACPI is s
On Wed 16-10-19 15:11:48, Dave Hansen wrote:
> We're starting to see systems with more and more kinds of memory such
> as Intel's implementation of persistent memory.
>
> Let's say you have a system with some DRAM and some persistent memory.
> Today, once DRAM fills up, reclaim will start and some
On 17/10/2019 16:11, Peter Zijlstra wrote:
> On Thu, Oct 17, 2019 at 12:11:16PM +0100, Quentin Perret wrote:
[...]
> It only boosts when 'rq->cfs.avg.util' increases while
> 'rq->cfs.avg.util_est.enqueued' remains unchanged (and util > util_est
> obv).
>
> This condition can be true for select_t
xenvif_connect_data() calls module_put() in case of error. This is
wrong as there is no related module_get().
Remove the superfluous module_put().
Fixes: 279f438e36c0a7 ("xen-netback: Don't destroy the netdev until the vif is
shut down")
Cc: # 3.12
Signed-off-by: Juergen Gross
Reviewed-by: Pau
Greetings
My name is Barrister Hans Erich.
I have a client who is interested to invest in your country, she is a well
known politician in her country and deserve a lucrative investment partnership
with you outside her country without any delay Please can you manage such
investment please Kin
On Thu, Oct 17, 2019 at 11:57:58PM -0500, Kangjie Lu wrote:
> The "wep" buffer is not initialized. To avoid memory disclosures,
> the fix initializes it, as peer functions like rtllib_ccmp_set_key
> do.
>
> Signed-off-by: Kangjie Lu
> ---
> drivers/staging/rtl8192e/rtllib_crypt_wep.c | 1 +
> 1
On Wed, Oct 9, 2019 at 2:01 PM Hans Verkuil wrote:
>
> On 10/8/19 3:40 PM, Maxime Jourdan wrote:
> > On 07/10/2019 18:39, Hans Verkuil wrote:
> >> On 10/7/19 6:24 PM, Maxime Jourdan wrote:
> >>> On 07/10/2019 17:12, Hans Verkuil wrote:
> On 10/7/19 4:59 PM, Maxime Jourdan wrote:
> > Hello
Per the BUG_ON(len != insn.length) in text_poke_loc_init(), tp->len
must indeed be the same as text_opcode_size(tp->opcode). Use this to
remove this field from the structure.
Sadly, due to 8 byte alignment, this only increases the structure
padding.
Signed-off-by: Peter Zijlstra (Intel)
---
arc
Instead of flipping text protection, use the patch_text infrastructure
that uses a fixmap alias where required.
This removes the last user of set_all_modules_text_*().
Signed-off-by: Peter Zijlstra (Intel)
Cc: ard.biesheu...@linaro.org
Cc: ra...@rab.in
Cc: Mark Rutland
Cc: Will Deacon
Cc: jame
Kprobes does something like:
register:
arch_arm_kprobe()
text_poke(INT3)
/* guarantees nothing, INT3 will become visible at some point, maybe
*/
kprobe_optimizer()
/* guarantees the bytes after INT3 are unused */
syncrhonize_rcu_tasks();
Adding another text_poke_bp_batch() user made me realize the interface
is all sorts of wrong. The text poke vector should be internal to the
implementation.
This then results in a trivial interface:
text_poke_queue() - which has the 'normal' text_poke_bp() interface
text_poke_finish() - whic
On Wed, Oct 16, 2019 at 11:02:03AM +, Mihail Atanassov wrote:
> On Wednesday, 16 October 2019 11:34:08 BST james qian wang (Arm Technology
> China) wrote:
> > Add a new helper function drm_color_ctm_s31_32_to_qm_n() for driver to
> > convert S31.32 sign-magnitude to Qm.n 2's complement that su
In preparation for static_call and variable size jump_label support,
teach text_poke_bp() to emulate instructions, namely:
JMP32, JMP8, CALL, NOP2, NOP_ATOMIC5, INT3
The current text_poke_bp() takes a @handler argument which is used as
a jump target when the temporary INT3 is hit by a different
On Fri, Oct 18, 2019 at 6:19 AM Kefeng Wang wrote:
>
> As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
> pr_warning"), removing pr_warning so all logging messages use a
> consistent _warn style. Let's do it.
Acked-by: Andy Shevchenko
> Cc: Corentin Chary
> Cc: Darren Hart
> C
Update the comment now that we've merged x86_32 support.
Signed-off-by: Peter Zijlstra (Intel)
---
arch/x86/include/asm/text-patching.h |3 +++
1 file changed, 3 insertions(+)
--- a/arch/x86/include/asm/text-patching.h
+++ b/arch/x86/include/asm/text-patching.h
@@ -85,6 +85,9 @@ static inli
On Fri, Oct 18, 2019 at 6:19 AM Kefeng Wang wrote:
>
> As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
> pr_warning"), removing pr_warning so all logging messages use a
> consistent _warn style. Let's do it.
Acked-by: Andy Shevchenko
> Cc: Corentin Chary
> Cc: Darren Hart
> C
Replace the ftrace_code_union with the generic text_gen_insn() helper,
which does exactly this.
Signed-off-by: Peter Zijlstra (Intel)
---
arch/x86/include/asm/text-patching.h | 25 -
arch/x86/kernel/alternative.c| 26 --
arch/x86/kernel
On Fri, Oct 18, 2019 at 6:19 AM Kefeng Wang wrote:
>
> As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
> pr_warning"), removing pr_warning so all logging messages use a
> consistent _warn style. Let's do it.
Acked-by: Andy Shevchenko
> Cc: Corentin Chary
> Cc: Darren Hart
> C
Dear Sir / Madam
Since ever we left your country back to Canada , we have gotten Government
approval and we have been busying planning for the less privilege Children
projects.
We are planning to release first batch of the funds $2,990,000.00 within 14
days for building an estate for motherl
Introduce a common helper to map *_INSN_OPCODE to *_INSN_SIZE.
Signed-off-by: Peter Zijlstra (Intel)
---
arch/x86/include/asm/text-patching.h | 43 +--
arch/x86/kernel/alternative.c| 12 -
2 files changed, 32 insertions(+), 23 deletions(-)
---
Provide a simple helper function to create common instruction
encodings.
Signed-off-by: Peter Zijlstra (Intel)
Cc: Steven Rostedt
Cc: Daniel Bristot de Oliveira
Cc: Masami Hiramatsu
---
arch/x86/include/asm/text-patching.h |2 +
arch/x86/kernel/alternative.c| 36
On Fri, Oct 18, 2019 at 7:38 AM Viresh Kumar wrote:
>
> On 17-10-19, 17:35, Sudeep Holla wrote:
> > dev_pm_qos_remove_request ends calling {max,min}_freq_req QoS notifiers
> > which schedule policy update work.
>
> I don't think that's correct. We remove the notifiers first and then
> only remove
With the last and only user of these functions gone (ftrace) remove
them as well to avoid ever growing new users.
Signed-off-by: Peter Zijlstra (Intel)
---
arch/x86/include/asm/set_memory.h |2 --
arch/x86/mm/init_32.c | 28
arch/x86/mm/init_64.c
Employ the fact that all text must be within a s32 displacement of one
another to shrink the text_poke_loc::addr field. Make it relative to
_stext.
This then shrinks struct text_poke_loc to 16 bytes, and consequently
increases TP_VEC_MAX from 170 to 256.
Signed-off-by: Peter Zijlstra (Intel)
---
Because of how some architectures used set_all_modules_text_*() there
was a dependency between the module state and its memory protection
state. This then required ftrace to be split into two functions, see
commit:
a949ae560a51 ("ftrace/module: Hardcode ftrace_module_init() call into
load_modul
Ftrace was one of the last W^X violators (and KLP it seems). These here patches
move it over to the generic text_poke() interface and thereby get rid of this
oddity.
The first 6 or so patches are more or less the same as in v3, except it has the
bugs fixed that Steve found:
- boot time function
Move ftrace over to using the generic x86 text_poke functions; this
avoids having a second/different copy of that code around.
This also avoids ftrace violating the (new) W^X rule and avoids
fragmenting the kernel text page-tables, due to no longer having to
toggle them RW.
Signed-off-by: Peter Z
Convert kprobes to the new text-poke naming.
Signed-off-by: Peter Zijlstra (Intel)
---
arch/x86/include/asm/kprobes.h | 14 +++
arch/x86/include/asm/text-patching.h |2 +
arch/x86/kernel/kprobes/core.c | 18 +++---
arch/x86/kernel/kprobes/opt.c| 44 +
Now that there are no users of set_all_modules_text_*() left, remove
it.
While it appears nds32 uses it, it does not have STRICT_MODULE_RWX and
therefore ends up with the NOP stubs.
Signed-off-by: Peter Zijlstra (Intel)
Cc: Jessica Yu
Cc: Greentime Hu
Cc: Vincent Chen
---
arch/nds32/kernel/f
Now that set_all_modules_text_*() is gone, nothing depends on the
relation between ->state = COMING and the protection state anymore.
This enables moving the protection changes later, such that the COMING
notifier callbacks can more easily modify the text.
Signed-off-by: Peter Zijlstra (Intel)
Cc
On 16/10/2019 22:49, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.197 release.
> There are 79 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 sh
From: Miklos Szeredi
This allows xattr ops on symlink/special files referenced by an O_PATH
descriptor without having to play games with /proc/self/fd/NN (which
doesn't work for symlinks anyway).
This capability is the same as would be given by introducing ...at()
variants with an AT_EMPTY_PATH
Hi Jeffrey,
> On the msm8998 mtp, the response to the baudrate change command is never
> received. On the Lenovo Miix 630, the response to the baudrate change
> command is corrupted - "Frame reassembly failed (-84)".
>
> Adding a 50ms delay before re-enabling flow to receive the baudrate change
On 16/10/2019 22:49, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.197 release.
> There are 92 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 sh
On 16/10/2019 22:50, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.150 release.
> There are 65 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 s
On 17-10-19, 08:26, Jeffrey Hugo wrote:
> bam_dma_terminate_all() will leak resources if any of the transactions are
> committed to the hardware (present in the desc fifo), and not complete.
> Since bam_dma_terminate_all() does not cause the hardware to be updated,
> the hardware will still operate
Guenter Roeck writes:
> On Sun, Sep 01, 2019 at 11:06:05AM +0300, Kalle Valo wrote:
>> Guenter Roeck writes:
>>
>> > Hi,
>> >
>> > On Sat, Aug 03, 2019 at 08:31:01PM -0400, Hui Peng wrote:
>> >> The `ar_usb` field of `ath10k_usb_pipe_usb_pipe` objects
>> >> are initialized to point to the conta
Hi Bjorn,
> Clean up the regulator usage in hci_qca and in particular don't
> regulator_set_voltage() for fixed voltages. It cleans up the driver, but more
> important it makes bluetooth work on my Lenovo Yoga C630, where the regulator
> for vddch0 is defined with a voltage range that doesn't over
On Fri, Oct 18, 2019 at 09:44:44AM +0200, Dietmar Eggemann wrote:
> On 17/10/2019 16:11, Peter Zijlstra wrote:
> > On Thu, Oct 17, 2019 at 12:11:16PM +0100, Quentin Perret wrote:
>
> [...]
>
> > It only boosts when 'rq->cfs.avg.util' increases while
> > 'rq->cfs.avg.util_est.enqueued' remains unc
On 16/10/2019 22:50, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.80 release.
> There are 81 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 sh
On 16/10/2019 22:49, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.3.7 release.
> There are 112 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 sho
On Tue, Oct 08, 2019 at 09:24:28AM +0100, Colin King wrote:
> From: Colin Ian King
>
> There is a spelling mistake in a dev_err message. Fix it. Add in missing
> newline.
>
> Signed-off-by: Colin Ian King
> ---
>
> V2: Add in newline \n
>
> ---
> drivers/crypto/inside-secure/safexcel_cipher.
On 14-10-19, 22:31, jassisinghb...@gmail.com wrote:
> From: Jassi Brar
>
> The following series adds AXI DMA (XDMAC) controller support on Milbeaut
> series.
> This controller is capable of only Mem<->MEM transfers. Number of channels is
> configurable {2,4,8}
Applied, thanks
--
~Vinod
On 14-10-19, 22:33, jassisinghb...@gmail.com wrote:
> From: Jassi Brar
>
> The following series adds AHB DMA (HDMAC) controller support on Milbeaut
> series.
> This controller is capable of Mem<->MEM and DEV<->MEM transfer. But only
> DEV<->MEM
> is currently supported.
Applied, thanks
--
~V
On 18-10-19, 09:32, Rafael J. Wysocki wrote:
> Well, the policy is going away, so the governor has been stopped for
> it already. Even if the limit is updated, it will not be used anyway,
> so why bother with updating it?
The hardware will be programmed to run on that frequency before the
policy
Hi,
On 18-10-2019 07:55, John Stultz wrote:
On Wed, Oct 16, 2019 at 12:27 AM Hans de Goede wrote:
On 10/15/19 7:39 AM, John Stultz wrote:
On Thu, Oct 3, 2019 at 1:51 PM Hans de Goede wrote:
On 03-10-2019 22:37, John Stultz wrote:
Fair point. I'm sort of taking a larger patchset and trying
Hi Thara,
On Thu, 17 Oct 2019 at 18:40, Thara Gopinath wrote:
>
> On 10/17/2019 04:44 AM, Vincent Guittot wrote:
> > Hi Thara,
> >
> > On Wed, 16 Oct 2019 at 23:22, Thara Gopinath
> > wrote:
> >>
> >> Hi Vincent,
> >>
> >> Thanks for the review
> >> On 10/14/2019 11:50 AM, Vincent Guittot wrote
On 18. 10. 19 8:54, Radhey Shyam Pandey wrote:
> xilinx axi_emac driver is supported on ZynqMP UltraScale platform(ARM64).
> So enable it in kconfig. Basic sanity testing is done on zu+ mpsoc zcu102
> evaluation board.
>
> Signed-off-by: Radhey Shyam Pandey
> ---
> drivers/net/ethernet/xilinx/Kc
Resolve most warnings from the 'sparse' static analysis tool for the
arch/riscv codebase. This makes life easier for us as maintainers,
and makes it easier for developers to use static analysis tools on
their own changes.
This third version drops the patch that adds one of the
__riscv_cmodel* pre
Add prototypes for assembly language functions defined in entry.S,
and include these prototypes into C source files that call those
functions.
This patch resolves the following warnings from sparse:
arch/riscv/kernel/signal.c:32:53: warning: incorrect type in initializer
(different address space
sparse identifies several missing prototypes caused by missing
preprocessor include directives:
arch/riscv/kernel/cpufeature.c:16:6: warning: symbol 'has_fpu' was not
declared. Should it be static?
arch/riscv/kernel/process.c:26:6: warning: symbol 'arch_cpu_idle' was not
declared. Should it be s
sparse complains loudly when string literals associated with
preprocessor directives are split into multiple, separately quoted
strings across different lines:
arch/riscv/mm/init.c:341:9: error: Expected ; at the end of type declaration
arch/riscv/mm/init.c:341:9: error: got "not use absolute addr
Add prototypes for assembly language functions defined in head.S,
and include these prototypes into C source files that call those
functions.
This patch resolves the following warnings from sparse:
arch/riscv/kernel/setup.c:39:10: warning: symbol 'hart_lottery' was not
declared. Should it be sta
Rather than adding prototypes for C functions called only by assembly
code, mark them as __visible. This avoids adding prototypes that will
never be used by the callers. Resolves the following sparse warnings:
arch/riscv/kernel/ptrace.c:151:6: warning: symbol 'do_syscall_trace_enter' was
not de
Several functions and arrays which are only used in the files in which
they are declared are missing "static" qualifiers. Warnings for these
symbols are reported by sparse:
arch/riscv/kernel/stacktrace.c:22:14: warning: symbol 'walk_stackframe' was not
declared. Should it be static?
arch/riscv/k
The __user annotations were removed from the {save,restore}_fp_state()
function signatures by commit 007f5c358957 ("Refactor FPU code in
signal setup/return procedures"), but should be present, and sparse
warns when they are not applied. Add them back in.
This change should have no functional imp
sparse identifies these missing prototypes when building arch/riscv:
arch/riscv/kernel/cpu.c:149:29: warning: symbol 'cpuinfo_op' was not declared.
Should it be static?
arch/riscv/kernel/irq.c:27:29: warning: symbol 'do_IRQ' was not declared.
Should it be static?
arch/riscv/kernel/irq.c:57:13: w
On Fri, Oct 18, 2019 at 09:44:44AM +0200, Dietmar Eggemann wrote:
> On 17/10/2019 16:11, Peter Zijlstra wrote:
> > On Thu, Oct 17, 2019 at 12:11:16PM +0100, Quentin Perret wrote:
>
> [...]
>
> > It only boosts when 'rq->cfs.avg.util' increases while
> > 'rq->cfs.avg.util_est.enqueued' remains unc
On Fri, Oct 18, 2019 at 1:32 AM Dave Hansen wrote:
>
> On 10/17/19 9:01 AM, Suleiman Souhlal wrote:
> > One problem that came up is that if you get into direct reclaim,
> > because persistent memory can have pretty low write throughput, you
> > can end up stalling users for a pretty long time whil
On 18.10.19 04:19, Naoya Horiguchi wrote:
On Thu, Oct 17, 2019 at 08:27:59PM +0200, Michal Hocko wrote:
On Thu 17-10-19 14:07:13, Qian Cai wrote:
On Thu, 2019-10-17 at 12:01 +0200, Michal Hocko wrote:
On Thu 17-10-19 09:34:10, Naoya Horiguchi wrote:
On Mon, Oct 14, 2019 at 10:39:14AM +0200, M
On Wed 16-10-19 16:14:52, David Hildenbrand wrote:
> On 16.10.19 16:03, Michal Hocko wrote:
[...]
> > But why cannot you keep the reference count at 1 (do get_page when
> > offlining the page)? In other words as long as the driver knows the page
> > has been returned to the host then it has ref cou
aic32x4_set_dai_sysclk misses a check for devm_clk_get and may miss the
failure.
Add a check to fix it.
Signed-off-by: Chuhong Yuan
---
sound/soc/codecs/tlv320aic32x4.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/sound/soc/codecs/tlv320aic32x4.c b/sound/soc/codecs/tlv320aic32x4.c
inde
Only uverbs_copy_to_struct_or_zero in uverbs_ioctl.c does not have a
check for uverbs_attr_get.
Although its usage in uverbs_response has a check for attr's validity,
UVERBS_HANDLER does not.
Therefore, it is better to add a check like other functions in
uverbs_ioctl.c.
Signed-off-by: Chuhong Yuan
On 17.10.19 16:21, Oscar Salvador wrote:
From: Naoya Horiguchi
Currently soft_offline_page() receives struct page, and its sibling
memory_failure() receives pfn. This discrepancy looks weird and makes
precheck on pfn validity tricky. So let's align them.
Signed-off-by: Naoya Horiguchi
Signed-
On Fri, 18 Oct 2019 09:38:47 +0200,
Kai-Heng Feng wrote:
>
> A driver may want to know the existence of _PR3, to choose different
> runtime suspend behavior. A user will be add in next patch.
>
> This is mostly the same as nouveau_pr3_present().
>
> Reported-by: kbuild test robot
It's confusin
On Wed, 9 Oct 2019, Atish Patra wrote:
> /proc/cpuinfo should just print all the isa string as an information
> instead of determining what is supported or not. ELF hwcap can be
> used by the userspace to figure out that.
>
> Simplify the isa string printing by removing the unsupported isa string
On Fri, Oct 18, 2019 at 10:03 AM Viresh Kumar wrote:
>
> On 18-10-19, 09:32, Rafael J. Wysocki wrote:
> > Well, the policy is going away, so the governor has been stopped for
> > it already. Even if the limit is updated, it will not be used anyway,
> > so why bother with updating it?
>
> The hard
On Fri, Oct 18, 2019 at 09:35:41AM +0200, Peter Zijlstra wrote:
> Because of how some architectures used set_all_modules_text_*() there
> was a dependency between the module state and its memory protection
> state. This then required ftrace to be split into two functions, see
> commit:
>
> a949a
From: Colin Ian King
There is a spelling mistake in a dev_dbg message. Fix it.
Signed-off-by: Colin Ian King
---
sound/soc/codecs/rt1011.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/codecs/rt1011.c b/sound/soc/codecs/rt1011.c
index ad049cfddcb0..dcd397a83cb4
On Fri 18-10-19 10:13:36, David Hildenbrand wrote:
[...]
> However, if the compound page spans multiple pageblocks
Although hugetlb pages spanning pageblocks are possible this shouldn't
matter in__test_page_isolated_in_pageblock because this function doesn't
really operate on pageblocks as the nam
On Fri, Oct 18, 2019 at 7:44 AM Viresh Kumar wrote:
>
> On 17-10-19, 18:34, Rafael J. Wysocki wrote:
> > [BTW, Viresh, it looks like cpufreq_set_policy() should still ensure
> > that the new min is less than the new max, because the QoS doesn't do
> > that.]
>
> The ->verify() callback does that f
On 18-10-19, 10:19, Rafael J. Wysocki wrote:
> On Fri, Oct 18, 2019 at 10:03 AM Viresh Kumar wrote:
> >
> > On 18-10-19, 09:32, Rafael J. Wysocki wrote:
> > > Well, the policy is going away, so the governor has been stopped for
> > > it already. Even if the limit is updated, it will not be used a
On 18-10-19, 10:24, Rafael J. Wysocki wrote:
> On Fri, Oct 18, 2019 at 7:44 AM Viresh Kumar wrote:
> >
> > On 17-10-19, 18:34, Rafael J. Wysocki wrote:
> > > [BTW, Viresh, it looks like cpufreq_set_policy() should still ensure
> > > that the new min is less than the new max, because the QoS doesn'
The commit below, adds a call to sysclk callback on shutdown.
This introduces a regression in stm32 SAI driver, as some clock
services are called twice, leading to unbalanced calls.
Move processing related to mclk from shutdown to sysclk callback.
When requested frequency is 0, assume shutdown and
handle_simple_irq() expect interrupts to be disabled. The USB
framework is using threaded interrupts, which implies that interrupts
are re-enabled as soon as it has run.
This reverts the changes from cc89c323a30e ("lan78xx: Use irq_domain
for phy interrupt from USB Int. EP").
[4.886203] 000:
On Fri, Sep 27, 2019 at 6:47 PM Masahiro Yamada
wrote:
>
> On Sun, Sep 22, 2019 at 8:36 PM Masahiro Yamada
> wrote:
> >
> > Since commit 54b8ae66ae1a ("kbuild: change *FLAGS_.o to
> > take the path relative to $(obj)"), sparc allmodconfig fails to build
> > as follows:
> >
> > CC arch/spar
while CONFIG_PARAVIRT=n, building fails:
arch/x86/kernel/cpu/mshyperv.c: In function ms_hyperv_init_platform:
arch/x86/kernel/cpu/mshyperv.c:219:2: error: pv_info undeclared (first use in
this function); did you mean pr_info?
pv_info.name = "Hyper-V";
^~~
Wrap it into a #ifdef to fix thi
> On Oct 18, 2019, at 16:18, Takashi Iwai wrote:
>
> On Fri, 18 Oct 2019 09:38:47 +0200,
> Kai-Heng Feng wrote:
>>
>> A driver may want to know the existence of _PR3, to choose different
>> runtime suspend behavior. A user will be add in next patch.
>>
>> This is mostly the same as nouveau_p
1 - 100 of 1349 matches
Mail list logo
