Re: [RESEND 1/4] clk: imx7d: Add USB clock information

Quoting Abel Vesa (2018-03-27 23:46:35) > From: Peter Chen > > Add USB clock information, the pll_usb_main_clk is USB_PLL at CCM > which is the output of USBOTG2 PHY. > > Signed-off-by: Peter Chen > Signed-off-by: Irina Tirdea

Re: [RFC PATCH 3/4] acpi: apei: Do not panic() in NMI because of GHES messages

Hi Alex, On 04/04/18 20:49, Alex G. wrote: > On 04/04/2018 11:53 AM, James Morse wrote: How do we know we will survive this trip? >>> >>> We don't. >> >> Isn't that even worse than panic()ing? (No output, followed by a watchdog >> reboot >> if we're lucky) > On the contrary. No output,

[Question] patch posting process

Hi all, I bring my Apologise for wasting your time, but .. May I ask for some clarification.. When we're speaking of 'posting patches shortly' does it mean to send them in next few hours ? Or would it be more acceptable to post one version per day even for very small changes in between ?

[4.15 & 4.14 stable 02/12] x86/CPU: Add a microcode loader callback

From: Borislav Petkov commit 1008c52c09dcb23d93f8e0ea83a6246265d2cce0 upstream Add a callback function which the microcode loader calls when microcode has been updated to a newer revision. Do the callback only when no error was encountered during loading. Tested-by: Ashok Raj

Re: [PATCH v4] drm/i915/dp: Send DPCD ON for MST before phy_up

On Fri, 2018-04-06 at 14:52 -0400, Lyude Paul wrote: > When doing a modeset where the sink is transitioning from D3 to D0 , it > would sometimes be possible for the initial power_up_phy() to start > timing out. This would only be observed in the last action before the > sink went into D3 mode

[PATCH 1/4 v2] init, tracing: Add initcall trace events

From: "Steven Rostedt (VMware)" Being able to trace the start and stop of initcalls is useful to see where the timings are an issue. There is already an "initcall_debug" parameter, but that can cause a large overhead itself, as the printing of the information may take longer

Re: [PATCH 0/4 v2] init, tracing: Add initcall trace events

Bah, Saved the cover letter before putting back in the original subject. -- Steve

[PATCH 0/4 v2] init, tracing:

A while ago we had a boot tracer. But it was eventually removed: commit 30dbb20e68e6f ("tracing: Remove boot tracer"). The rationale was because there is already a initcall_debug boot option that causes printk()s of all the initcall functions. The problem with the initcall_debug option is that

Re: [PATCH net-next 00/12] fscache: Fixes, traces and development

Linus Torvalds wrote: > So if you have that [GIT PULL] in the subject line, the pulls will > often be a bit timelier. That's okay with all the patches as follow up emails? David

Re: [PATCH net-next 00/12] fscache: Fixes, traces and development

On Fri, Apr 6, 2018 at 12:28 PM, David Howells wrote: > > That's okay with all the patches as follow up emails? Actually, I generally just look at the git tree and don't need the individual patches at all, at least as long as they are only to a particular subsystem. So if

Re: [PATCH] mfd: twl-core: Fix clock initialization

On 04/05/2018 02:46 PM, Peter Ujfalusi wrote: > When looking up the clock we must use the client->dev as device since that > is the one which is probed via DT. > > Signed-off-by: Peter Ujfalusi > Cc: sta...@vger.kernel.org > Fixes: 7e2e6c5758de9 ("mfd: twl-core: Do not

Re: [PATCH] clk: qcom: Add MSM8998 Global Clock Control (GCC) driver

Quoting Bjorn Andersson (2018-03-27 08:25:18) > From: Joonwoo Park > > Add support for the global clock controller found on MSM8998 > based devices. This should allow most non-multimedia device > drivers to probe and control their clocks. > > Signed-off-by: Joonwoo Park

Re: [PATCH] clk: cs2000: set pm_ops in hibernate-compatible way

Quoting Nikita Yushchenko (2018-03-20 01:33:23) > Use SET_LATE_SYSTEM_SLEEP_PM_OPS() macro instead of direct assignment to > .resume_early field. > > This fixes initialization of CS2000 in restore from hibernation in case > of kernel used to load image did not initialize CS2000 while kernel >

Re: [RfC PATCH] Add udmabuf misc device

On Fri, Apr 06, 2018 at 03:36:03PM +0300, Oleksandr Andrushchenko wrote: > On 04/06/2018 02:57 PM, Gerd Hoffmann wrote: > > Hi, > > > >>>I fail to see any common ground for xen-zcopy and udmabuf ... > >>Does the above mean you can assume that xen-zcopy and udmabuf > >>can co-exist as two

s390: defective uses of va_arg in __debug_sprintf_event

debug_sprintf_event calls __debug_sprintf_event with a format and arguments. There various types of arguments used in these call, but __debug_sprintf_event uses va_arg with only long as the type argument so random errors could occur because the type and argument are supposed to match.

[PATCH] powerpc: add __printf verification to prom_printf

__printf is useful to verify format and arguments. Fix arg mismatch reported by gcc, remove the following warnings (with W=1): arch/powerpc/kernel/prom_init.c:1467:31: error: format ‘%x’ expects argument of type ‘unsigned int’, but argument 2 has type ‘long unsigned int’ [-Werror=format=]

Re: [PATCH 4.15 00/72] 4.15.16-stable review

On Fri, Apr 06, 2018 at 03:23:35PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.15.16 release. > There are 72 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

[PATCH 1/4] perf, tools, mem: Allow all record/report options

From: Andi Kleen For perf mem report / perf mem record, pass all unknown options through to the underlying report/record commands. This makes things like perf mem record -a sleep 1 work. Matches how c2c and other tools work. Signed-off-by: Andi Kleen

Some minor fixes for perf user tools

This patchkit fixes some random minor issues in the perf user tools -Andi

Re: [PATCH 02/10] locking/qspinlock: Remove unbounded cmpxchg loop from locking slowpath

On 04/05/2018 12:58 PM, Will Deacon wrote: > The qspinlock locking slowpath utilises a "pending" bit as a simple form > of an embedded test-and-set lock that can avoid the overhead of explicit > queuing in cases where the lock is held but uncontended. This bit is > managed using a cmpxchg loop

[PATCH 09/11] x86/pti: enable global pages for shared areas

From: Dave Hansen The entry/exit text and cpu_entry_area are mapped into userspace and the kernel. But, they are not _PAGE_GLOBAL. This creates unnecessary TLB misses. Add the _PAGE_GLOBAL flag for these areas. Signed-off-by: Dave Hansen

[PATCH 05/11] x86/mm: do not auto-massage page protections

From: Dave Hansen A PTE is constructed from a physical address and a pgprotval_t. __PAGE_KERNEL, for instance, is a pgprot_t and must be converted into a pgprotval_t before it can be used to create a PTE. This is done implicitly within functions like pfn_pte() by

[PATCH 08/11] x86/mm: do not forbid _PAGE_RW before init for __ro_after_init

From: Dave Hansen __ro_after_init data gets stuck in the .rodata section. That's normally fine because the kernel itself manages the R/W properties. But, if we run __change_page_attr() on an area which is __ro_after_init, the .rodata checks will trigger and force

[PATCH 10/11] x86/pti: never implicitly clear _PAGE_GLOBAL for kernel image

From: Dave Hansen Summary: In current kernels, with PTI enabled, no pages are marked Global. This potentially increases TLB misses. But, the mechanism by which the Global bit is set and cleared is rather haphazard. This patch makes the process more explicit. In

[PATCH 06/11] x86/mm: remove extra filtering in pageattr code

From: Dave Hansen The pageattr code has a mode where it can set or clear PTE bits in existing PTEs, so the page protections of the *new* PTEs come from one of two places: 1. The set/clear masks: cpa->mask_clr / cpa->mask_set 2. The existing PTE We filter

Re: [PATCH v4 1/3] locking: Document the semantics of spin_is_locked()

On Fri, Apr 06, 2018 at 09:47:39PM +0200, Andrea Parri wrote: > There appeared to be a certain, recurrent uncertainty concerning the > semantics of spin_is_locked(), likely a consequence of the fact that > this semantics remains undocumented or that it has been historically > linked to the

[PATCH] openrisc: define mb() as its mandatory

Following Peter Z's patch ("asm-generic: Disallow no-op mb() for SMP systems") which makes mb() mandatory for SMP architectures we define it as l.msync. On OpenRISC this will flush the current cores write buffer and trigger remote cores to invalidate their caches of the written memory.

[PATCH] Input: leds - fix out of bound access

UI_SET_LEDBIT ioctl() causes the following KASAN splat when used with led > LED_CHARGING: [ 1274.663418] BUG: KASAN: slab-out-of-bounds in input_leds_connect+0x611/0x730 [input_leds] [ 1274.663426] Write of size 8 at addr 88003377b2c0 by task ckb-next-daemon/5128 This happens because we

Re: [PATCH v3 1/4] Ktest: add email support

On Mon, 26 Mar 2018 13:08:01 -0700 Tim Tianyang Chen wrote: > Users can define optional variables to get email notifications. > Ktest can send emails when the script: > * was started > * failed with fatal errors and called dodie() > * completed all testing > > Users

[PATCH v2] writeback: safer lock nesting

lock_page_memcg()/unlock_page_memcg() use spin_lock_irqsave/restore() if the page's memcg is undergoing move accounting, which occurs when a process leaves its memcg for a new one that has memory.move_charge_at_immigrate set. unlocked_inode_to_wb_begin,end() use spin_lock_irq/spin_unlock_irq() if

[PATCH 2/4 v2] init, tracing: instrument security and console initcall trace events

From: Abderrahmane Benbachir Trace events have been added around the initcall functions defined in init/main.c. But console and security have their own initcalls. This adds the trace events associated for those initcall functions. Link:

[PATCH 3/4 v2] init, tracing: Have printk come through the trace events for initcall_debug

From: "Steven Rostedt (VMware)" With trace events set before and after the initcall function calls, instead of having a separate routine for printing out the initcalls when initcall_debug is specified on the kernel command line, have the code register a callback to the

Re: [PATCH v4] drm/i915/dp: Send DPCD ON for MST before phy_up

On Fri, 2018-04-06 at 12:48 -0700, Laura Abbott wrote: > On 04/06/2018 11:52 AM, Lyude Paul wrote: > > When doing a modeset where the sink is transitioning from D3 to D0 , it > > would sometimes be possible for the initial power_up_phy() to start > > timing out. This would only be observed in the

Re: [PATCH v10 05/10] livepatch: Support separate list for replaced patches.

On Mon, Mar 26, 2018 at 12:11:07PM +0200, Petr Mladek wrote: > On Fri 2018-03-23 17:44:10, Josh Poimboeuf wrote: > > On Fri, Mar 23, 2018 at 10:45:07AM +0100, Petr Mladek wrote: > > > On Tue 2018-03-20 15:15:02, Josh Poimboeuf wrote: > > > > On Tue, Mar 20, 2018 at 01:25:38PM +0100, Petr Mladek

[GIT PULL] fscache: Fixes, traces and development

branch 'userns-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace (2018-04-03 19:15:32 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/fscache-next-20180406 for you to fetch changes up

Re: [Question] patch posting process

Hi Willy, Thank you for your opinion, it's very helpful. WBR, Vadim On Fri, Apr 06, 2018 at 09:21:46PM +0200, Willy Tarreau wrote: > Hi Vadim, > > On Fri, Apr 06, 2018 at 11:29:16AM -0700, Vadim Lomovtsev wrote: > > Hi all, > > > > I bring my Apologise for wasting your time, but .. > >

[PATCH] backing: silence compiler warning using __printf

__printf marker was added in commit d2cc4dde9206 ("bdi_register: add __printf verification, fix arg mismatch") for function `bdi_register` since it is useful to verify format and arguments. Apply equivalent gcc attribute to `bdi_register_va`. Remove warning triggered with W=1:

Re: [PATCH] i8042: Enable MUX on Sony VAIO VGN-CS series to fix touchpad

On Fri, Apr 06, 2018 at 10:16:19PM +0200, Ondrej Zary wrote: >On Friday 06 April 2018 22:05:59 Sasha Levin wrote: >> Hi, >> >> [This is an automated email] >> >> This commit has been processed by the -stable helper bot and determined >> to be a high probability candidate for -stable trees. (score:

Re: [PATCH v5 3/8] clk: davinci: add a reset lookup table for psc0

Quoting Bartosz Golaszewski (2018-03-30 08:28:51) > From: Bartosz Golaszewski > > In order to be able to use the reset framework in legacy boot mode as > well, add the reset lookup table to the psc driver for da850 variant. > > Signed-off-by: Bartosz Golaszewski

[PATCH 4/4] perf, tools, record: Remove suggestion to enable APIC

From: Andi Kleen perf record suggests to enable the APIC on errors. APIC is practically always used today and the problem is usually somewhere else. Just remove the outdated suggestion. Signed-off-by: Andi Kleen --- tools/perf/util/evsel.c | 3 +--

[PATCH 3/4] perf, tools, record: Remove misleading error suggestion

From: Andi Kleen When perf record encounters an error setting up an event it suggests to enable CONFIG_PERF_EVENTS. This is misleading because: - Usually it is enabled (it is really hard to disable on x86) - The problem is usually somewhere else, e.g. the CPU is not

[PATCH 2/4] perf, tools: Clarify browser help

From: Andi Kleen Clarify in the browser help that ESC in tui mode may go back to the previous screen instead of just exiting (was not clear to me) Signed-off-by: Andi Kleen --- tools/perf/ui/browsers/hists.c | 2 +- 1 file changed, 1 insertion(+), 1

Re: [PATCH v2] powerpc, pkey: make protection key 0 less special

Ram Pai writes: > On Wed, Apr 04, 2018 at 06:41:01PM -0300, Thiago Jung Bauermann wrote: >> >> Hello Ram, >> >> Ram Pai writes: >> >> > Applications need the ability to associate an address-range with some >> > key and latter revert to its initial

Re: [PATCH 3/6] clk: stm32mp1: fix SAI3 & SAI4 clocks

Quoting gabriel.fernan...@st.com (2018-04-05 23:39:30) > From: Gabriel Fernandez > > fix bad copy / paste. > SAI3 & SAI4 used gate of SAI2 instead SAI3 & SAI4 > > Signed-off-by: Gabriel Fernandez > --- Applied to clk-next

Re: [PATCH 6/6] clk: stm32mp1: remove ck_apb_dbg clock

Quoting gabriel.fernan...@st.com (2018-04-05 23:39:33) > From: Gabriel Fernandez > > It's recommended to use only clk_sys_dbg clock instead to activate > debug IP. > > Signed-off-by: Gabriel Fernandez > --- Applied to clk-next

Re: [PATCH 5/6] clk: stm32mp1: set stgen_k clock as critical

Quoting gabriel.fernan...@st.com (2018-04-05 23:39:32) > From: Gabriel Fernandez > > stgen_k should be declared as critical to avoid blocking console > when ck_hsi is not used. > > Signed-off-by: Gabriel Fernandez > --- Applied to clk-next

Re: [PATCH 4/6] clk: stm32mp1: add missing tzc2 clock

Quoting gabriel.fernan...@st.com (2018-04-05 23:39:31) > From: Gabriel Fernandez > > This patch adds tzc2 clock and rename tzc clock into tzc1 > > Signed-off-by: Gabriel Fernandez > --- Applied to clk-next

Re: [PATCH 2/6] clk: stm32mp1: remove unused dfsdm_src[] const

Quoting gabriel.fernan...@st.com (2018-04-05 23:39:29) > From: Gabriel Fernandez > > This patch remove unused constant. > > Signed-off-by: Gabriel Fernandez > --- Applied to clk-next

[PATCH 11/11] x86/pti: leave kernel text global for !PCID

Note: This has changed since the last version. It now clones the kernel text PMDs at a much later point and also disables this functionality on AMD K8 processors. Details in the patch. -- I'm sticking this at the end of the series because it's a bit weird. It can be dropped and the rest of

[PATCH 03/11] x86/mm: introduce "default" kernel PTE mask

From: Dave Hansen The __PAGE_KERNEL_* page permissions are "raw". They contain bits that may or may not be supported on the current processor. They need to be filtered by a mask (currently __supported_pte_mask) to turn them into a value that we can actually set in

[PATCH] staging: pi433: break long lines in rf69.c

Breaks long lines in rf69.c, fixing checkpatch.pl warnings: "WARNING: line over 80 characters" Signed-off-by: Simon Sandström --- drivers/staging/pi433/rf69.c | 182 ++- 1 file changed, 129 insertions(+), 53 deletions(-) diff --git

Re: [PATCH v2] isofs compress: Remove VLA usage

On Thu, 2018-04-05 at 11:17 -0700, Kyle Spiers wrote: > As part of the effort to remove VLAs from the kernel[1], this changes > the allocation of the bhs and pages arrays from being on the stack to being > kcalloc()ed. This also allows for the removal of the explicit zeroing > of bhs. > >

Re: [RESEND 2/4] clk: imx7d: Correct dram pll type

Quoting Abel Vesa (2018-03-27 23:46:37) > From: Anson Huang > > DRAM PLL is a audio/video type PLL, need to correct > it to get correct ops of PLL. > > There is a test_div placed before DRAM PLL's gate, so > add this test div clk. > > Signed-off-by: Anson Huang

Re: [RESEND 4/4] clk: imx7d: Move clks_init_on before any clock operations

Quoting Abel Vesa (2018-03-27 23:46:39) > From: Dong Aisheng > > For init on clocks we should move it at the first place in imx7d_clocks_init() > before any clock operations, else the clock operation may fail in case the > clock > is still not on. > > Acked-by: Ranjani

Re: [RESEND 3/4] clk: imx7d: Correct ahb clk parent select

Quoting Abel Vesa (2018-03-27 23:46:38) > From: Anson Huang > > Design team change the ahb's clk parent options but > did NOT update the DOC accordingly in time, so the > AHB/IPG's clk rate in clk tree is incorrect, AHB is > 67.5MHz and IPG is 33.75MHz, but using scope to >

[4.15 & 4.14 stable 09/12] x86/microcode: Request microcode on the BSP

From: Borislav Petkov commit cfb52a5a09c8ae3a1dafb44ce549fde5b69e8117 upstream ... so that any newer version can land in the cache and can later be fished out by the application functions. Do that before grabbing the hotplug lock. Signed-off-by: Borislav Petkov

[4.15 & 4.14 stable 04/12] x86/microcode: Get rid of struct apply_microcode_ctx

From: Borislav Petkov commit 854857f5944c59a881ff607b37ed9ed41d031a3b upstream It is a useless remnant from earlier times. Use the ucode_state enum directly. No functional change. Signed-off-by: Borislav Petkov Signed-off-by: Thomas Gleixner

[4.15 & 4.14 stable 07/12] x86/microcode: Do not upload microcode if CPUs are offline

commit 30ec26da9967d0d785abc24073129a34c3211777 upstream Avoid loading microcode if any of the CPUs are offline, and issue a warning. Having different microcode revisions on the system at any time is outright dangerous. [ Borislav: Massage changelog. ] Signed-off-by: Ashok Raj

[4.15 & 4.14 stable 08/12] x86/microcode/intel: Look into the patch cache first

From: Borislav Petkov commit d8c3b52c00a05036e0a6b315b4b17921a7b67997 upstream The cache might contain a newer patch - look in there first. A follow-on change will make sure newest patches are loaded into the cache of microcode patches. Signed-off-by: Borislav Petkov

[GIT PULL] PCI changes for v4.17

PCI changes: - move pci_uevent_ers() out of pci.h (Michael Ellerman) - skip ASPM common clock warning if BIOS already configured it (Sinan Kaya) - fix ASPM Coverity warning about threshold_ns (Gustavo A. R. Silva) - remove last user of pci_get_bus_and_slot() and the function itself

Re: [PATCH] usbip: vhci_hcd: check rhport before using in vhci_hub_control()

On 04/06/2018 02:01 AM, Sergei Shtylyov wrote: > Hello! > > On 4/6/2018 1:31 AM, Shuah Khan wrote: > >> Validate !rhport < 0 before using it to access port_status array. > >    Why '!'? > I should have explained it better in the commit log. rhport is set based on input wIndex which could be

Re: [PATCH 3.18 00/93] 3.18.103-stable review

On 6 April 2018 6:52:29 PM IST, Greg Kroah-Hartman wrote: >This is the start of the stable review cycle for the 3.18.103 release. >There are 93 patches in this series, all will be posted as a response >to this one. If anyone has any issues with these being applied,

Re: [PATCH] swap: divide-by-zero when zero length swap file on ssd

On Fri, 6 Apr 2018 09:52:50 -0700 Randy Dunlap wrote: > [adding linux-mm and akpm] Thanks. > ... The patch is a huge mess, with leading and trailing whitespace. I fixed all that up, but we'd like to receive Tom's signed-off-by:, please.

Re: [PATCH 0/4 v2] init, tracing: Add initcall trace events

On Fri, 6 Apr 2018 21:34:24 +0200 Peter Zijlstra wrote: > On Fri, Apr 06, 2018 at 03:19:23PM -0400, Steven Rostedt wrote: > > > > Peter, Andrew, > > > > This keeps initcall_debug printing printk()s, but adds the feature of > > those locations also being trace events. Are

Re: [PATCH v4 1/3] locking: Document the semantics of spin_is_locked()

On 04/06/2018 12:47 PM, Andrea Parri wrote: > There appeared to be a certain, recurrent uncertainty concerning the > semantics of spin_is_locked(), likely a consequence of the fact that > this semantics remains undocumented or that it has been historically > linked to the (likewise unclear)

[PATCH 00/11] [v5] Use global pages with PTI

Changes from v4 * Fix compile error reported by Tom Lendacky * Avoid setting _PAGE_GLOBAL on non-present entries Changes from v3: * Fix whitespace issue noticed by willy * Clarify comments about X86_FEATURE_PGE checks * Clarify commit message around the necessity of _PAGE_GLOBAL filtering

Re: INFO: rcu detected stall in snd_pcm_oss_write3 (2)

syzbot has found reproducer for the following crash on upstream commit 38c23685b273cfb4ccf31a199feccce3bdcb5d83 (Fri Apr 6 04:29:35 2018 +) Merge tag 'armsoc-drivers' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc syzbot dashboard link:

Re: [PATCH v3 2/2] MIPS: io: add a barrier after register read in readX()

On Fri, Apr 06, 2018 at 02:15:57PM -0400, Sinan Kaya wrote: > On 4/5/2018 9:34 PM, Sinan Kaya wrote: > > Can we get these merged to 4.17? > > > > There was a consensus to fix the architectures having API violation issues. > > https://www.mail-archive.com/netdev@vger.kernel.org/msg225971.html > >

Re: [PATCH v3 2/2] MIPS: io: add a barrier after register read in readX()

On 4/5/2018 9:34 PM, Sinan Kaya wrote: > On 4/3/2018 8:55 AM, Sinan Kaya wrote: >> While a barrier is present in writeX() function before the register write, >> a similar barrier is missing in the readX() function after the register >> read. This could allow memory accesses following readX() to

[4.15 & 4.14 stable 01/12] x86/microcode: Propagate return value from updating functions

From: Borislav Petkov commit 3f1f576a195aa266813cbd4ca70291deb61e0129 upstream ... so that callers can know when microcode was updated and act accordingly. Tested-by: Ashok Raj Signed-off-by: Borislav Petkov Reviewed-by: Ashok Raj

[4.15 & 4.14 stable 12/12] x86/microcode: Fix CPU synchronization routine

From: Borislav Petkov commit bb8c13d61a629276a162c1d2b1a20a815cbcfbb7 upstream Emanuel reported an issue with a hang during microcode update because my dumb idea to use one atomic synchronization variable for both rendezvous - before and after update - was simply bollocks:

Re: [PATCH net-next 00/12] fscache: Fixes, traces and development

On Fri, Apr 6, 2018 at 11:21 AM, Linus Torvalds wrote: > > No, but if you can redo the pull request part so that the diffstat I > get will match the diffstat I see in the pull request, that would be > good. Oh, and can you please make sure there is a "[GIT PULL]"

[4.15 & 4.14 stable 03/12] x86/CPU: Check CPU feature bits after microcode upgrade

From: Borislav Petkov commit 42ca8082e260dcfd8afa2afa6ec1940b9d41724c upstream With some microcode upgrades, new CPUID features can become visible on the CPU. Check what the kernel has mirrored now and issue a warning hinting at possible things the user/admin can do to make use of

[4.15 & 4.14 stable 11/12] x86/microcode: Attempt late loading only when new microcode is present

From: Borislav Petkov commit 2613f36ed965d0e5a595a1d931fd3b480e82d6fd upstream Return UCODE_NEW from the scanning functions to denote that new microcode was found and only then attempt the expensive synchronization dance. Reported-by: Emanuel Czirai

[PATCH v4] drm/i915/dp: Send DPCD ON for MST before phy_up

When doing a modeset where the sink is transitioning from D3 to D0 , it would sometimes be possible for the initial power_up_phy() to start timing out. This would only be observed in the last action before the sink went into D3 mode was intel_dp_sink_dpms(DRM_MODE_DPMS_OFF). We originally thought

Re: [PATCH 0/4 v2] init, tracing: Add initcall trace events

Peter, Andrew, This keeps initcall_debug printing printk()s, but adds the feature of those locations also being trace events. Are you OK if I add this? Works with and without TRACEPOINTS enabled. -- Steve On Fri, 06 Apr 2018 15:08:54 -0400 Steven Rostedt wrote: > A

Re: [PATCH for-4.16 2/3] drivers: change struct device_driver::coredump() return type to void

Op vr 6 apr. 2018 4:46 PM schreef Greg Kroah-Hartman : > > On Fri, Apr 06, 2018 at 12:13:38PM +0200, Arend van Spriel wrote: > > On Sat, Mar 24, 2018 at 10:04 AM, Greg Kroah-Hartman > > wrote: > > > On Sat, Mar 24, 2018 at 09:50:05AM +0100,

Re: [PATCH 0/4 v2] init, tracing: Add initcall trace events

On Fri, Apr 06, 2018 at 03:19:23PM -0400, Steven Rostedt wrote: > > Peter, Andrew, > > This keeps initcall_debug printing printk()s, but adds the feature of > those locations also being trace events. Are you OK if I add this? Yeah, I don't see any real problems with it.

[PATCH v4 1/3] locking: Document the semantics of spin_is_locked()

There appeared to be a certain, recurrent uncertainty concerning the semantics of spin_is_locked(), likely a consequence of the fact that this semantics remains undocumented or that it has been historically linked to the (likewise unclear) semantics of spin_unlock_wait(). A recent auditing [1] of

Re: [PATCH 4.14 00/67] 4.14.33-stable review

On Fri, Apr 06, 2018 at 03:23:30PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.33 release. > There are 67 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

Re: [PATCH v3 4/6] clk: meson-axg: Add AO Clock and Reset controller driver

Quoting Yixun Lan (2018-03-27 19:50:48) > + [CLKID_AO_SAR_ADC_CLK] = _saradc_gate, > +}; > + > +static struct clk_hw_onecell_data axg_aoclk_onecell_data = { const? > + .hws = { > + [CLKID_AO_REMOTE] = _ao.hw, > + [CLKID_AO_I2C_MASTER] =

[PATCH] staging: pi433: break long lines

Breaks long lines in rf69.h, fixing checkpatch.pl warnings: "WARNING: line over 80 characters" Signed-off-by: Simon Sandström --- drivers/staging/pi433/rf69.h | 28 +++- 1 file changed, 19 insertions(+), 9 deletions(-) diff --git

Re: [PATCH 1/6] clk: stm32mp1: add missing static

Quoting gabriel.fernan...@st.com (2018-04-05 23:39:28) > From: Gabriel Fernandez > > Add missing static for const parent names and clock ops. > > Signed-off-by: Gabriel Fernandez > --- Applied to clk-next

Re: atomic file replacing status?

On 02/11/2018 10:40 PM, Andrew Kelley wrote: > Whatever happened to this patch? > > https://patchwork.kernel.org/patch/9636735/ > > It looks fine and addresses a legitimate issue. > > Please CC me on replies as I am not subscribed to the LKML. > > Kind regards, > Andrew Kelley There was some

Re: [PATCH net-next 00/12] fscache: Fixes, traces and development

kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > tags/fscache-next-20180406 > > Do you want me to repost the patchset? No, but if you can redo the pull request part so that the diffstat I get will match the diffstat I see in the pull request, that would be good. Thanks, Linus

Re: [PATCH] clk: imx: Set CLK_SET_RATE_GATE for gate and divider clocks

Quoting Abel Vesa (2018-03-23 06:33:26) > Add flag CLK_SET_RATE_GATE for i.MX gate and divider clocks on which the > client drivers usually make clk_set_rate() call, so that the call will fail > when clock is still on instead of standing the risk of running into glitch > issue. Rate cannot be

Re: [PATCH v3 1/6] clk: meson: aoclk: refactor common code into dedicated file

Quoting Yixun Lan (2018-03-27 19:50:45) > diff --git a/drivers/clk/meson/gxbb-aoclk.c b/drivers/clk/meson/gxbb-aoclk.c > index 9ec23ae9a219..5a922639a264 100644 > --- a/drivers/clk/meson/gxbb-aoclk.c > +++ b/drivers/clk/meson/gxbb-aoclk.c > @@ -165,38 +135,39 @@ static int gxbb_aoclkc_probe(struct

[PATCH 4/4 v2] init: Have initcall_debug still work without CONFIG_TRACEPOINTS

From: "Steven Rostedt (VMware)" Add macros around the initcall_debug tracepoint code to have the code to default back to the old method if CONFIG_TRACEPOINTS is not enabled. Signed-off-by: Steven Rostedt (VMware) --- init/main.c | 24

[PATCH v4] net: thunderx: rework mac addresses list to u64 array

From: Vadim Lomovtsev It is too expensive to pass u64 values via linked list, instead allocate array for them by overall number of mac addresses from netdev. This eventually removes multiple kmalloc() calls, aviod memory fragmentation and allow to put single null

Re: Problem with commit 31e77c93e432 "sched/fair: Update blocked load when newly idle"

Am 06.04.2018 um 18:03 schrieb Vincent Guittot: > Hi Heiner, > > On 30 March 2018 at 10:37, Heiner Kallweit wrote: >> Am 30.03.2018 um 08:50 schrieb Vincent Guittot: >>> On 29 March 2018 at 19:40, Heiner Kallweit wrote: Am 29.03.2018 um 09:41

Re: [PATCH v1]: perf/x86: store user space frame-pointer value on a sample

On Fri, Apr 06, 2018 at 10:06:26PM +0300, Alexey Budankov wrote: > On 06.04.2018 18:31, Andi Kleen wrote: > >> diff --git a/arch/x86/kernel/perf_regs.c b/arch/x86/kernel/perf_regs.c > >> index e47b2dbbdef3..9284048cf5b0 100644 > >> --- a/arch/x86/kernel/perf_regs.c > >> +++

[PATCH] fs: Add MODULE_SOFTDEP declarations for hard-coded crypto drivers

This helps initramfs builders and other tools to find the full dependencies of a module. Debian on powerpc (ppc32) still uses yaboot as default boot loader. Using a default installation (debian-installer) 64bit and metadata_csum feature are not setup in ext4. This is discussed in more details at:

Re: [PATCH] drm/sti: Depend on OF rather than selecting it

Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: cc6b741c6f63 drm: sti: remove useless fields from vtg structure. The bot has also determined it's probably a bug fixing patch. (score: 96.6729) The bot has tested the following

Re: [PATCH] blk-mq: Directly schedule q->timeout_work when aborting a request

Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: 358f70da49d7 blk-mq: make blk_abort_request() trigger timeout path. The bot has also determined it's probably a bug fixing patch. (score: 98.7780) The bot has tested the

Re: [PATCH] i8042: Enable MUX on Sony VAIO VGN-CS series to fix touchpad

Hi, [This is an automated email] This commit has been processed by the -stable helper bot and determined to be a high probability candidate for -stable trees. (score: 24.5527) The bot has tested the following trees: v4.16, v4.15.15, v4.14.32, v4.9.92, v4.4.126. v4.16: Build OK! v4.15.15:

Re: [PATCH] i8042: Enable MUX on Sony VAIO VGN-CS series to fix touchpad

On Friday 06 April 2018 22:05:59 Sasha Levin wrote: > Hi, > > [This is an automated email] > > This commit has been processed by the -stable helper bot and determined > to be a high probability candidate for -stable trees. (score: 24.5527) > > The bot has tested the following trees: v4.16,

Re: [PATCH 2/2] clk: spear: fix WDT clock definition on SPEAr600

Quoting Quentin Schulz (2018-04-06 00:50:45) > There is no SPEAr600 device named "wdt". Instead, the description of the > WDT (watchdog) was recently added to the Device Tree, and the device > name is "fc88.wdt", so we should associate the WDT fixed rate clock > to this device name. > >

[PATCH] staging: pi433: break long lines in pi433_if.c

Breaks long lines in pi433_if.c, fixing checkpatch.pl warnings: "WARNING: line over 80 characters" Signed-off-by: Simon Sandström --- drivers/staging/pi433/pi433_if.c | 19 ++- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git

[PATCH 07/11] x86/mm: comment _PAGE_GLOBAL mystery

From: Dave Hansen I was mystified as to where the _PAGE_GLOBAL in the kernel page tables for kernel text came from. I audited all the places I could find, but I missed one: head_64.S. The page tables that we create in here live for a long time, and they also have

[PATCH 01/11] x86/mm: factor out pageattr _PAGE_GLOBAL setting

From: Dave Hansen The pageattr code has a pattern repeated where it sets _PAGE_GLOBAL for present PTEs but clears it for non-present PTEs. The intention is to keep _PAGE_GLOBAL from getting confused with _PAGE_PROTNONE since _PAGE_GLOBAL is for present PTEs and

  1   2   3   4   5   6   7   8   9   10   >