Re: [PATCH] smpboot: correctly update number of booted cores

At 02/22/2018 04:50 AM, Samuel Neves wrote: Without this fix, /proc/cpuinfo will display an incorrect amount of CPU cores, after bringing them offline and online again, as exemplified below: $ cat /proc/cpuinfo | grep cores cpu cores : 4 cpu cores : 8 cpu cores : 8 cpu cores

Re: [PATCH] PCI: Add quirk for Cavium Thunder-X2 PCIe erratum #173

On Wed, Feb 21, 2018 at 05:20:40PM -0600, Bjorn Helgaas wrote: > On Wed, Feb 21, 2018 at 04:25:08PM +0530, George Cherian wrote: > > I have found another configuration where this fails. > > Following is the configuration > > 1) Connected a PCIe Intel i40 card under the root port. > > 2) unbind the

Re: [PATCH 13/13] i2c: img-scb: Drop METAG dependency

On Thu, Feb 22, 2018 at 09:10:18AM +0100, Wolfram Sang wrote: > On Wed, Feb 21, 2018 at 11:38:25PM +, James Hogan wrote: > > Now that arch/metag/ has been removed, remove the METAG dependency from > > the IMG SCB I2C device driver. The hardware is also present on MIPS SoCs > > so the driver

Re: [PATCH] MAINTAINERS: Update ASPEED entry with details

Dear Andrew & Joel, Since you are ASPEED BMC experts, any time and interest in eSPI code review ? I've sent it before, but no more response. Intel recommends eSPI bus than LPC as I know. I just kept the minimal eSPI code which is approved to work well in our real server boards for two

Re: [PATCH 5/6] Pmalloc: self-test

On 22/02/18 00:24, Kees Cook wrote: > On Tue, Feb 20, 2018 at 8:40 AM, Igor Stoppa wrote: [...] >> sorry for being dense ... are you proposing that I do something to >> lkdtm_rodata.c ? An example would probably help me understand. > > It would likely live in

Re: [PATCH v7 6/6] drm/msm: iommu: Replace runtime calls with runtime suppliers

On Fri, Feb 16, 2018 at 9:13 AM, Tomasz Figa wrote: > On Fri, Feb 16, 2018 at 2:14 AM, Robin Murphy wrote: >> On 15/02/18 04:17, Tomasz Figa wrote: >> [...] Could you elaborate on what kind of locking you are concerned about? As I

Re: [RFC PATCH] mmc: sdhci-of-arasan: Add auto tuning support for ZynqMP Platform

On 21/02/18 17:00, Manish Narani wrote: > Hi Adrian, > >> -Original Message- >> From: Manish Narani >> Sent: Wednesday, February 21, 2018 11:39 AM >> To: Adrian Hunter ; michal.si...@xilinx.com; >> ulf.hans...@linaro.org; linux-arm-ker...@lists.infradead.org;

Re: [PATCH 4.14, 4.9] crypto: talitos - fix Kernel Oops on hashing an empty file

On 2/22/2018 9:08 AM, Christophe Leroy wrote: > Upstream 87a81dce53b1ea61acaeefa5191a0376a2d1d721 > > Performing the hash of an empty file leads to a kernel Oops > > [ 44.504600] Unable to handle kernel paging request for data at address > 0x000c > [ 44.512819] Faulting instruction

Re: [PATCH v5 1/3] sched: Stop nohz stats when decayed

On 21 February 2018 at 14:13, Valentin Schneider wrote: > On 02/16/2018 01:44 PM, Vincent Guittot wrote: >> On 16 February 2018 at 13:13, Valentin Schneider >> wrote: >>> On 02/14/2018 03:26 PM, Vincent Guittot wrote: Stopped the

Re: [PATCH] MAINTAINERS: Update ASPEED entry with details

On Thu, 22 Feb 2018, at 15:33, Joel Stanley wrote: > I am interested in all ASPEED drivers, and the previous match wasn't > grabbing files in nested directories. Use N instead. > > Add the arm kernel mailing list so that patches get reviewed there, and > the linux-aspeed list which exists only

Re: [PATCH v2 4/9] staging: android: ion: Avoid NULL point in error path

Hi Greg, Sorry for late responds for I was on vacation. On 2018/2/17 0:27, Greg KH wrote: > On Mon, Feb 12, 2018 at 06:43:09PM +0800, Yisheng Xie wrote: >> If we failed to create debugfs for ion at ion_device_create, the >> debug_root of ion_device will be NULL, and then when try to create debug

Re: [RFC PATCH v16 0/6] mm: security: ro protection for dynamic data

On 21/02/18 23:36, Dave Chinner wrote: > On Wed, Feb 21, 2018 at 11:56:22AM +0200, Igor Stoppa wrote: [...] > It seems lots of people get confused when discussing concepts vs > implementation... :) IMHO, if possible, it's better to use unambiguous terms at every point. __ro_after_init is

[PATCH v2 3/3] mm/sparse: Optimize memmap allocation during sparse_init()

In sparse_init(), two temporary pointer arrays, usemap_map and map_map are allocated with the size of NR_MEM_SECTIONS. They are used to store each memory section's usemap and mem map if marked as present. With the help of these two arrays, continuous memory chunk is allocated for usemap and memmap

[PATCH v2 2/3] mm/sparsemem: Defer the ms->section_mem_map clearing

In sparse_init(), if CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER=y, system will allocate one continuous memory chunk for mem maps on one node and populate the relevant page tables to map memory section one by one. If fail to populate for a certain mem section, print warning and its ->section_mem_map

[PATCH v2 1/3] mm/sparse: Add a static variable nr_present_sections

It's used to record how many memory sections are marked as present during system boot up, and will be used in the later patch. Signed-off-by: Baoquan He --- mm/sparse.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/mm/sparse.c b/mm/sparse.c index

Re: [PATCH] x86/asm: improve how GEN_*_SUFFIXED_RMWcc() specify clobbers

>>> On 21.02.18 at 22:39, wrote: > On Mon, Feb 19, 2018 at 6:49 AM, Jan Beulich wrote: >> Commit df3405245a ("x86/asm: Add suffix macro for GEN_*_RMWcc()") >> introduced "suffix" RMWcc operations, adding bogus clobber specifiers: >> For one, on x86

Re: [PATCH 4.15 000/163] 4.15.5-stable review

On Wed, Feb 21, 2018 at 02:25:18PM -0600, Dan Rue wrote: > On Wed, Feb 21, 2018 at 01:47:09PM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.15.5 release. > > There are 163 patches in this series, all will be posted as a response > > to this one. If

Re: [PATCH 13/13] i2c: img-scb: Drop METAG dependency

On Wed, Feb 21, 2018 at 11:38:25PM +, James Hogan wrote: > Now that arch/metag/ has been removed, remove the METAG dependency from > the IMG SCB I2C device driver. The hardware is also present on MIPS SoCs > so the driver still has value. > > Signed-off-by: James Hogan

Re: [PATCH v2] iio:dummy: Replace S_IWUSR by 0200

On 22/02/2018 04:01, Julia Lawall wrote: On Wed, 21 Feb 2018, Rodrigo Siqueira wrote: This patch fixes the checkpatch.pl warning: drivers/iio/dummy/iio_dummy_evgen.c:151: WARNING: Symbolic permissions 'S_IWUSR' are not preferred. Consider using octal permissions '0200'. I haven't studied up

[PATCH 1/2] drm/amd: remove inclusion of non-existing scheduler directory

The scheduler directory was removed via commit 1b1f42d8fde4 ("drm: move amd_gpu_scheduler into common location") Remove it from include path. Signed-off-by: Corentin Labbe --- drivers/gpu/drm/amd/amdgpu/Makefile | 1 - 1 file changed, 1 deletion(-) diff --git

[PATCH 2/2] drm/amd: Remove inclusion of non-existing include directories

This patch fix the following build warnings: CC [M] drivers/gpu/drm/amd/amdgpu/amdgpu_drv.o cc1: warning: ../display/: No such file or directory [-Wmissing-include-dirs] cc1: warning: ../display/include: No such file or directory [-Wmissing-include-dirs] CC [M]

Re: [PATCH] m68k: time: stop validating rtc_time in .read_time

Hi Alexandre, On Wed, Feb 21, 2018 at 10:37 PM, Alexandre Belloni wrote: > The RTC core is always calling rtc_valid_tm after the read_time callback. > It is not necessary to call it just before returning from the callback. > > Signed-off-by: Alexandre Belloni

Re: [PATCH 2/2] drm/amd: Remove inclusion of non-existing include directories

Am 22.02.2018 um 09:21 schrieb Corentin Labbe: This patch fix the following build warnings: CC [M] drivers/gpu/drm/amd/amdgpu/amdgpu_drv.o cc1: warning: ../display/: No such file or directory [-Wmissing-include-dirs] cc1: warning: ../display/include: No such file or directory

Re: [PATCH v2 13/17] tracing: probeevent: Add $argN for accessing function args

On Thu, 22 Feb 2018 00:00:31 +0900 Masami Hiramatsu wrote: > Add $argN special fetch variable for accessing function > arguments. This allows user to trace the Nth argument easily > at the function entry. > > Note that this returns most probably assignment of registers >

Re: [PATCH 3/4] fs/dcache: Avoid the try_lock loop in d_delete()

On 2018-02-22, Al Viro wrote: >> @@ -2378,22 +2420,36 @@ void d_delete(struct dentry * dentry) >> /* >> * Are we the only user? >> */ >> -again: >> spin_lock(>d_lock); >> +again: >> inode = dentry->d_inode; >> isdir =

Re: [PATCH v2 0/3] new driver for Valve Steam Controller

2018-02-22 1:13 GMT+01:00 Pierre-Loup A. Griffais : > > On 02/21/2018 12:21 PM, Rodrigo Rivas Costa wrote: >> >> Related to that, Benjamin Tissoires replied to 1/3: --- a/drivers/hid/hid-quirks.c +++ b/drivers/hid/hid-quirks.c @@ -629,6 +629,10 @@

Re: [PATCH v2 4/9] staging: android: ion: Avoid NULL point in error path

On Thu, Feb 22, 2018 at 04:59:27PM +0800, Yisheng Xie wrote: > Hi Greg, > > Sorry for late responds for I was on vacation. > > On 2018/2/17 0:27, Greg KH wrote: > > On Mon, Feb 12, 2018 at 06:43:09PM +0800, Yisheng Xie wrote: > >> If we failed to create debugfs for ion at ion_device_create, the

[PATCH v2 0/3] mm/sparse: Optimize memmap allocation during sparse_init()

This is v2 post. V1 can be found here: https://www.spinics.net/lists/linux-mm/msg144486.html In sparse_init(), two temporary pointer arrays, usemap_map and map_map are allocated with the size of NR_MEM_SECTIONS. They are used to store each memory section's usemap and mem map if marked as present.

[PATCH] staging: media: atomisp: Remove inclusion of non-existing directories

This patch fix the following build warnings: CC [M] drivers/staging/media/atomisp/pci/atomisp2/atomisp_drvfs.o cc1: warning: drivers/staging/media/atomisp/pci/atomisp2/css2400/isp/kernels/bayer_ls/bayer_ls_1.0/: No such file or directory [-Wmissing-include-dirs] cc1: warning:

Re: [PATCH 1/2] drm/amd: remove inclusion of non-existing scheduler directory

Am 22.02.2018 um 09:21 schrieb Corentin Labbe: The scheduler directory was removed via commit 1b1f42d8fde4 ("drm: move amd_gpu_scheduler into common location") Remove it from include path. Signed-off-by: Corentin Labbe Reviewed-by: Christian König

Re: [PATCH v2] iio:dummy: Replace S_IWUSR by 0200

> > Also who cares?  The commit message is perfectly clear. > > I do care about newcomers really learning on how to write a proper > commit message. > > The commit messsage should really say why the patch is needed, no what the > patch does. > It fixes a checkpatch warning. The warning was

Re: [PATCH] KVM: arm/arm64: No need to zero CNTVOFF in kvm_timer_vcpu_put() for VHE

Hi Shanker, On Mon, Feb 19, 2018 at 09:38:07AM -0600, Shanker Donthineni wrote: > In AArch64/AArch32, the virtual counter uses a fixed virtual offset > of zero in the following situations as per ARMv8 specifications: > > 1) HCR_EL2.E2H is 1, and CNTVCT_EL0/CNTVCT are read from EL2. > 2)

[PATCH] x86/documentation: Document the correct function name

topology_sibling_cpumask() is the correct thread-related topology information in the kernel. S/topology_sibling_mask/topology_sibling_cpumask Signed-off-by: Dou Liyang --- Documentation/x86/topology.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: [patches] [PATCH v4 0/6] Add dynamic ftrace support for RISC-V platforms

On Thu, Feb 22, 2018 at 12:05:11AM +0800, Palmer Dabbelt wrote: > On Mon, 12 Feb 2018 21:13:15 PST (-0800), alan...@andestech.com wrote: > > This patch set includes the building blocks of dynamic ftrace features > > for RISC-V machines. > > > > Changes in v4: > > - Organize code structure

Re: [PATCH 2/2] vfio: platform: Add generic DT reset support

Hi Philipp, On Wed, Feb 21, 2018 at 5:51 PM, Philipp Zabel wrote: > I have a suggestion to avoid having to use the IS_ERR_OR_NULL macro, see > below: > > On Tue, 2018-02-13 at 17:36 +0100, Geert Uytterhoeven wrote: >> Vfio-platform requires reset support, provided either

Re: [PATCH] KVM: arm/arm64: No need to zero CNTVOFF in kvm_timer_vcpu_put() for VHE

On Thu, 22 Feb 2018 08:42:31 +, Christoffer Dall wrote: > > Hi Shanker, > > On Mon, Feb 19, 2018 at 09:38:07AM -0600, Shanker Donthineni wrote: > > In AArch64/AArch32, the virtual counter uses a fixed virtual offset > > of zero in the following situations as per ARMv8 specifications: > > >

Re: [PATCH v5 19/20] cpufreq: add support for CPU DVFS based on SCMI message protocol

Hi Sudeep, On Monday 12 Feb 2018 at 18:45:23 (+), Sudeep Holla wrote: [...] > +/* > + * perf_ops->freq_set is not a synchronous, the actual OPP change will > + * happen asynchronously and can get notified if the events are > + * subscribed for by the SCMI firmware > + */ > +static int >

Re: [PATCH v2 0/3] new driver for Valve Steam Controller

On Thu, Feb 22, 2018 at 1:13 AM, Pierre-Loup A. Griffais wrote: > > > On 02/21/2018 12:21 PM, Rodrigo Rivas Costa wrote: >> >> On Tue, Feb 20, 2018 at 04:09:39PM -0800, Pierre-Loup A. Griffais wrote: >>> >>> On 02/20/2018 03:20 PM, Rodrigo Rivas Costa wrote:

Re: [PATCH 2/6] genalloc: selftest

On 22/02/18 00:28, Kees Cook wrote: > On Tue, Feb 20, 2018 at 8:59 AM, Igor Stoppa wrote: >> >> >> On 13/02/18 01:50, Kees Cook wrote: >>> On Mon, Feb 12, 2018 at 8:52 AM, Igor Stoppa wrote: [...] + genalloc_selftest(); >>> >>> I

Re: [PATCH 2/2] vfio: platform: Add generic DT reset support

Hi Geert, On Thu, 2018-02-22 at 09:50 +0100, Geert Uytterhoeven wrote: [...] > > > @@ -127,8 +134,15 @@ static int vfio_platform_get_reset(struct > > > vfio_platform_device *vdev) > > > vdev->of_reset = vfio_platform_lookup_reset(vdev->compat, > > >

Re: [PATCH 5/6] mfd: cros_ec_dev: Check communication with ec at resume

Hi Gwendal, On 22/02/18 03:20, Gwendal Grignou wrote: > On Mon, Feb 19, 2018 at 2:41 PM, Enric Balletbo i Serra > wrote: >> From: Gwendal Grignou > This patch is not needed anymore. It was added to >> >> Send dummy command to EC at resume

Re: WARNING: refcount bug in sock_wfree

On Wed, Feb 21, 2018 at 9:59 PM, syzbot wrote: > Hello, > > syzbot hit the following crash on upstream commit > 79c0ef3e85c015b0921a8fd5dd539d1480e9cd6c (Mon Feb 19 19:58:19 2018 +) > Merge

[PATCH] cpufreq: tegra186: Break after initialization is done for policy->cpu

There are two clusters (2 + 4 CPUs) on this platform and a separate cpufreq policy is available for each of the CPUs. The loop in tegra186_cpufreq_init() tries to find the structure for the right CPU and finish initialization. But it is missing a `break` statement at the end, which forces it to

[PATCH] arm64: rename the function arm64_is_ras_serror() to avoid confusion

The RAS SError Syndrome can be Implementation-Defined, arm64_is_ras_serror() is used to judge whether it is RAS SError, but arm64_is_ras_serror() does not include this judgement. In order to avoid function name confusion, we rename the arm64_is_ras_serror() to arm64_is_categorized_ras_serror(),

[PATCH][next] HID: fix spelling mistake, "registred" -> "registered"

From: Colin Ian King Trivial fix to spelling mistake in hid_err error message text. Signed-off-by: Colin Ian King --- drivers/hid/hid-elan.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/hid/hid-elan.c

Re: [PATCH 08/20] lightnvm: complete geo structure with maxoc*

Javier > On 22 Feb 2018, at 11.00, Matias Bjørling wrote: > > On 02/22/2018 10:52 AM, Javier Gonzalez wrote: >>> On 22 Feb 2018, at 10.45, Matias Bjørling wrote: >>> >>> On 02/22/2018 08:55 AM, Javier Gonzalez wrote: > On 22 Feb 2018, at 08.45, Matias

Re: [PATCH v14 0/9] LPC: legacy ISA I/O support

On 21/02/2018 23:15, dann frazier wrote: On Tue, Feb 20, 2018 at 01:48:31AM +0800, John Garry wrote: This patchset supports the IPMI-bt device attached to the Low-Pin-Count interface implemented on Hisilicon Hip06/Hip07 SoC. --- | LPC

Re: [PATCH 06/13] clocksource: Remove metag generic timer driver

On 22/02/2018 00:38, James Hogan wrote: > Now that arch/metag/ has been removed, remove the metag generic > per-thread timer driver. It is of no value without the architecture > code. > > Signed-off-by: James Hogan > Cc: Daniel Lezcano > Cc: Thomas

RE: [PATCH] staging: typec: handle vendor defined part and modify drp toggling flow

Hi, > -Original Message- > From: linux-usb-ow...@vger.kernel.org > [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of ShuFanLee > Sent: 2018年2月21日 23:02 > To: heikki.kroge...@linux.intel.com; li...@roeck-us.net; g...@kroah.com > Cc: shufan_...@richtek.com; cy_hu...@richtek.com; >

[PATCH 2/2] media: ov2680: Add Omnivision OV2680 sensor driver

This patch adds V4L2 sub-device driver for OV2680 image sensor. The OV2680 is a 1/5" CMOS color sensor from Omnivision. Supports output format: 10-bit Raw RGB. The OV2680 has a single lane MIPI interface. The driver exposes following V4L2 controls: - auto/manual exposure, - exposure, -

Re: [PATCH v4 00/16] R-Car DU: Convert LVDS code to bridge driver

Hi Frank, On Thursday, 22 February 2018 08:07:14 EET Frank Rowand wrote: > On 02/20/18 15:10, Laurent Pinchart wrote: > > Hello, > > > > This patch series addresses a design mistake that dates back from the > > initial DU support. Support for the LVDS encoders, which are IP cores > > separate

[PATCH 1/2] media: ov2680: dt: Add bindings for OV2680

Add device tree binding documentation for the OV5640 camera sensor. CC: devicet...@vger.kernel.org Signed-off-by: Rui Miguel Silva --- .../devicetree/bindings/media/i2c/ov2680.txt | 34 ++ 1 file changed, 34 insertions(+) create mode 100644

Re: [PATCH v2] perf cgroup: simplify arguments if track multiple events for a cgroup

2018-01-31 17:22 GMT+08:00 Jiri Olsa : > On Mon, Jan 29, 2018 at 11:48:09PM +0800, weiping zhang wrote: >> if use -G with one cgroup and -e with multiple events, only the first >> event has correct cgroup setting, all events from the second will track >> system-wide events. >> >>

Re: [PATCH 00/13] Remove metag architecture

On 22 February 2018 at 09:48, James Hogan wrote: > On Thu, Feb 22, 2018 at 10:26:54AM +0100, Peter Zijlstra wrote: >> On Wed, Feb 21, 2018 at 11:38:12PM +, James Hogan wrote: >> > So lets call it a day and drop the Meta architecture port from the >> > kernel. RIP Meta. >>

Re: [PATCH RFC tools/lkmm 10/12] tools/memory-model: Add a S lock-based external-view litmus test

On Thu, Feb 22, 2018 at 11:15:04AM +0100, Peter Zijlstra wrote: > On Thu, Feb 22, 2018 at 02:58:47PM +0800, Boqun Feng wrote: > > > And yes, if we go with a purely RCpc interpretation of acquire and > > > release, then I don't believe the writes in the previous critical > > > section would be

[PATCH] x86/boot/compressed/64: fix warning for 32-bit trampoline copy

gcc-8 warns that we copy TRAMPOLINE_32BIT_CODE_SIZE bytes from the pointer to the function into actual trampoline, when that pointer is only 8 bytes: In file included from arch/x86/boot/compressed/pgtable_64.c:3: arch/x86/boot/compressed/pgtable_64.c: In function 'paging_prepare':

Re: [PATCH] x86/boot/compressed/64: fix warning for 32-bit trampoline copy

On Thu, Feb 22, 2018 at 11:40:41AM +0100, Arnd Bergmann wrote: > gcc-8 warns that we copy TRAMPOLINE_32BIT_CODE_SIZE bytes from the pointer > to the function into actual trampoline, when that pointer is only 8 bytes: > > In file included from arch/x86/boot/compressed/pgtable_64.c:3: >

Re: [PATCH 00/31 v2] PTI support for x86_32

On Wed, Feb 21, 2018 at 05:59:34PM +0100, Arnd Bergmann wrote: > On Wed, Feb 21, 2018 at 11:26 AM, Lorenzo Colitti wrote: > > On Wed, Feb 14, 2018 at 5:54 PM, Greg KH wrote: > >> > > IPSEC doesn't work with a 64bit kernel and 32bit userspace right

Re: [PATCH 00/31 v2] PTI support for x86_32

On Thu, Feb 22, 2018 at 12:10 PM, Greg KH wrote: > On Wed, Feb 21, 2018 at 05:59:34PM +0100, Arnd Bergmann wrote: >> On Wed, Feb 21, 2018 at 11:26 AM, Lorenzo Colitti wrote: >> > On Wed, Feb 14, 2018 at 5:54 PM, Greg KH

Re: [PATCH 13/20] lightnvm: add support for 2.0 address format

On 02/21/2018 10:26 AM, Javier González wrote: Add support for 2.0 address format. Also, align address bits for 1.2 and 2.0 to be able to operate on channel and luns without requiring a format conversion. Use a generic address format for this purpose. Signed-off-by: Javier González

[PATCH 1/2] locking/xchg/alpha: Use smp_mb() in place of __ASM__MB

Replace each occurrence of __ASM__MB with a (trailing) smp_mb() in xchg(), cmpxchg(), and remove the now unused __ASM__MB definitions; this improves readability, with no additional synchronization cost. Suggested-by: Will Deacon Signed-off-by: Andrea Parri

[PATCH 2/2] locking/xchg/alpha: Add leading smp_mb() to xchg(), cmpxchg()

Successful RMW operations are supposed to be fully ordered, but Alpha's xchg() and cmpxchg() do not align to this requirement. Will reported that: > So MP using xchg: > > WRITE_ONCE(x, 1) > xchg(y, 1) > > smp_load_acquire(y) == 1 > READ_ONCE(x) == 0 > > would be allowed. (thus violating the

Re: [RFCv4 01/21] media: add request API core and UAPI

On Wed, Feb 21, 2018 at 4:29 PM, Hans Verkuil wrote: > On 02/21/2018 07:01 AM, Alexandre Courbot wrote: >> Hi Hans, >> >> On Tue, Feb 20, 2018 at 7:36 PM, Hans Verkuil wrote: >>> On 02/20/18 05:44, Alexandre Courbot wrote: > > > +#define

Re: [PATCH net v2 2/2] tuntap: correctly add the missing xdp flush

On 2018年02月22日 15:54, Sergei Shtylyov wrote: Hello! On 2/22/2018 9:24 AM, Jason Wang wrote: Commit 762c330d670e ("tuntap: add missing xdp flush") tries to fix the devmap stall caused by missed xdp flush by counting the pending xdp redirected packets and flush when it exceeds

Re: [PATCH 2/3] KVM: nVMX: fix wrong condition for SPEC_CTRL and PRED_CMD MSRs

On 22/02/2018 01:07, Jim Mattson wrote: > On Wed, Feb 21, 2018 at 1:41 PM, Paolo Bonzini wrote: >> We need to change the default all-1s bitmap if the MSRs are _not_ >> intercepted. However, the code was disabling the intercept when it was >> _enabled_ in the VMCS01. This is

Re: [PATCH 03/20] lightnvm: fix capabilities for 2.0 sysfs

On 02/22/2018 08:47 AM, Javier Gonzalez wrote: On 22 Feb 2018, at 08.28, Matias Bjørling wrote: On 02/21/2018 10:26 AM, Javier González wrote: Both 1.2 and 2.0 specs define a field for media and controller capabilities. Also, 1.2 defines a separate field dedicated to device

Re: [PATCH v2] fork: Unconditionally clear stack on fork

On Wed, Feb 21, 2018 at 12:59:14PM -0800, Andrew Morton wrote: > On Wed, 21 Feb 2018 11:29:33 +0100 Michal Hocko wrote: > > > On Tue 20-02-18 18:16:59, Kees Cook wrote: > > > One of the classes of kernel stack content leaks[1] is exposing the > > > contents of prior heap or

[PATCH] media: stm32-dcmi: fix unnecessary parentheses

Fix unnecessary parentheses in if conditions. Detected by checkpatch.pl --strict. Signed-off-by: Hugues Fruchet --- drivers/media/platform/stm32/stm32-dcmi.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git

[PATCH] media: stm32-dcmi: add JPEG support

Add DCMI JPEG support. Signed-off-by: Hugues Fruchet --- drivers/media/platform/stm32/stm32-dcmi.c | 195 +++--- 1 file changed, 148 insertions(+), 47 deletions(-) diff --git a/drivers/media/platform/stm32/stm32-dcmi.c

Re: [PATCH v10 03/10] media: platform: Add Renesas CEU driver

On 02/21/18 18:47, Jacopo Mondi wrote: > Add driver for Renesas Capture Engine Unit (CEU). > > The CEU interface supports capturing 'data' (YUV422) and 'images' > (NV[12|21|16|61]). > > This driver aims to replace the soc_camera-based sh_mobile_ceu one. > > Tested with ov7670 camera sensor,

Re: [PATCH v5 1/3] sched: Stop nohz stats when decayed

On 02/22/2018 08:37 AM, Vincent Guittot wrote: > On 21 February 2018 at 14:13, Valentin Schneider > wrote: >> On 02/16/2018 01:44 PM, Vincent Guittot wrote: >>> On 16 February 2018 at 13:13, Valentin Schneider >>> wrote: On 02/14/2018

Re: [PATCH v3 01/25] dt-bindings: soc: qcom: Add bindings for APR bus

On 22/02/18 00:14, Rob Herring wrote: On Tue, Feb 20, 2018 at 3:33 AM, Srinivas Kandagatla wrote: Thanks for your review comments, On 18/02/18 23:04, Rob Herring wrote: On Wed, Feb 14, 2018 at 09:13:23AM +, Srinivas Kandagatla wrote: Thanks for the

Re: [PATCH v2] x86: consider effective protection attributes in W+X check

>>> On 21.02.18 at 17:53, wrote: > * Jan Beulich wrote: > >> Using just the leaf page table entry flags would cause a false warning >> in case _PAGE_RW is clear or _PAGE_NX is set in a higher level entry. >> Hand through both the current entry's flags as

Re: [PATCH v6 1/5] fuse: Remove the buggy retranslation of pids in fuse_dev_do_read

On Wed, Feb 21, 2018 at 9:29 PM, Eric W. Biederman wrote: > At the point of fuse_dev_do_read the user space process that initiated the > action on the fuse filesystem may no longer exist. The process have been > killed or may have fired an asynchronous request and exited.

Re: [PATCH v5 6/8] i2c: demux: Use changeset helpers for clarity

Hi Geert, On Thursday, 22 February 2018 11:26:44 EET Geert Uytterhoeven wrote: > On Thu, Feb 22, 2018 at 1:05 AM, Laurent Pinchart wrote: > > From: Pantelis Antoniou > > > > The changeset helpers are easier to use, use them instead of > > using the static

[PATCH] platform/x86: silead_dmi: Add DMI match for the I.T.Works TW701 tablet

The I.T.Works TW701 7" tablet is a differently branded version of the same generic 7" Windows tablet as the Trekstor ST70416-6. Add a DMI match-table entry for it pointing to the Trekstor's touchscreen info. Signed-off-by: Hans de Goede --- drivers/platform/x86/silead_dmi.c

[PATCH 0/2] media: Introduce Omnivision OV2680 driver

Add driver and bindings for the OV2680 2 megapixel CMOS 1/5" sensor, which has a single MIPI lane interface and output format of 10-bit Raw RGB. Features supported are described in PATCH 2/2. Cheers, Rui Rui Miguel Silva (2): media: ov2680: dt: Add bindings for OV2680 media: ov2680: Add

Re: [PATCH v6 2/5] fuse: Fail all requests with invalid uids or gids

On Wed, Feb 21, 2018 at 9:29 PM, Eric W. Biederman wrote: > Upon a cursory examinination the uid and gid of a fuse request are > necessary for correct operation. Failing a fuse request where those > values are not reliable seems a straight forward and reliable means of >

[PATCH v11 01/10] dt-bindings: media: Add Renesas CEU bindings

Add bindings documentation for Renesas Capture Engine Unit (CEU). Signed-off-by: Jacopo Mondi Reviewed-by: Rob Herring Reviewed-by: Laurent Pinchart Acked-by: Hans Verkuil ---

Re: [1/2] ARM: irqchip: stm32: Optimizes and cleans up stm32-exti irq_domain

Hi Radek I've tested your change on stm32h743i-eval.dts board and gpio-keys tests are not functional. No interrupt occurs when we push or release button (cat /proc/interrupt). Board: stm32h743i-eval.dts Test description: gpio-keys (gpioc 13 => exti 13), with gpio or interrupt property.

Re: [PATCH 03/20] lightnvm: fix capabilities for 2.0 sysfs

On 02/22/2018 11:25 AM, Javier Gonzalez wrote: On 22 Feb 2018, at 10.39, Matias Bjørling wrote: On 02/22/2018 08:47 AM, Javier Gonzalez wrote: On 22 Feb 2018, at 08.28, Matias Bjørling wrote: On 02/21/2018 10:26 AM, Javier González wrote: Both 1.2 and

[PATCH v8 02/13] kexec_file: make an use of purgatory optional

On arm64, no trampline code between old kernel and new kernel will be required in kexec_file implementation. This patch introduces a new configuration, ARCH_HAS_KEXEC_PURGATORY, and allows related code to be compiled in only if necessary. Signed-off-by: AKASHI Takahiro

[PATCH v8 00/13] arm64: kexec: add kexec_file_load() support

This is the eighth round of implementing kexec_file_load() support on arm64.[1] Most of the code is based on kexec-tools (along with some kernel code from x86, which also came from kexec-tools). This patch series enables us to * load the kernel by specifying its file descriptor, instead of

[PATCH v8 04/13] x86: kexec_file: factor out elf core header related functions

exclude_mem_range() and prepare_elf64_headers() can be re-used on other architectures, including arm64, as well. So let them factored out so as to move them to generic side in the next patch. fill_up_crash_elf_data() can potentially be commonalized for most architectures who want to go through io

[PATCH v8 01/13] resource: add walk_system_ram_res_rev()

This function, being a variant of walk_system_ram_res() introduced in commit 8c86e70acead ("resource: provide new functions to walk through resources"), walks through a list of all the resources of System RAM in reversed order, i.e., from higher to lower. It will be used in kexec_file

[PATCH 0/2] locking/xchg/alpha: Additional fixes

Hi, A couple of two more fixes, on top of tip:locking/urgent, to Alpha's implementations of xchg() and cmpxchg(): - The first, suggested by Will, removing the macro '__ASM__MB' in favour of smp_mb(); - The second, reported by Will, adding a leading smp_mb(). Compile tested only.

Re: [PATCH v5 6/8] i2c: demux: Use changeset helpers for clarity

Hi Laurent, On Thu, Feb 22, 2018 at 1:05 AM, Laurent Pinchart wrote: > From: Pantelis Antoniou > > The changeset helpers are easier to use, use them instead of > using the static property. > > Signed-off-by: Pantelis

Re: [PATCH v3 6/7] arm: dts: sun8i: a83t: Fix undefined offset with virtual timer

Hi Marc, Thank you for the review! On Tue, 20 Feb 2018 18:07:54 + Marc Zyngier wrote: > Hi Mylène, > > On 19/02/18 08:18, Mylène Josserand wrote: > > The ARM architected timers use an offset between their physical and > > virtual counters. That offset should be

Re: [PATCH 4.9 34/77] powerpc: fix build errors in stable tree

On Thu, 2018-02-22 at 12:01 +1100, Michael Ellerman wrote: > So I guess this patch is OK for now, but we do need a full back port of > 222f20f to 4.9. Hi, in the light of this, do you know the full status of protections against Meltdown on powerpc/ppc64el architecures on 4.9? Regards, --

Re: [PATCH 09/20] lightnvm: use generic identify structure

On 02/22/2018 08:49 AM, Javier González wrote: On 22 Feb 2018, at 08.47, Matias Bjørling wrote: On 02/21/2018 10:26 AM, Javier González wrote: Create a generic identify structure to collect the identify information before knowing the spec. version. This forces different

Re: [PATCH v5 19/20] cpufreq: add support for CPU DVFS based on SCMI message protocol

On 22/02/18 09:04, Quentin Perret wrote: > Hi Sudeep, > > On Monday 12 Feb 2018 at 18:45:23 (+), Sudeep Holla wrote: > [...] >> +/* >> + * perf_ops->freq_set is not a synchronous, the actual OPP change will >> + * happen asynchronously and can get notified if the events are >> + *

Re: [PATCH] fork: Allow stack to be wiped on fork

On Wed, Feb 21, 2018 at 01:56:33AM +, Andrew Lutomirski wrote: > > It would be much nicer to be able to control this at runtime rather > > than compile-time. Why not a /proc tunable? We could always use more > > of those ;) > >

Re: [PATCH 08/20] lightnvm: complete geo structure with maxoc*

> On 22 Feb 2018, at 10.45, Matias Bjørling wrote: > > On 02/22/2018 08:55 AM, Javier Gonzalez wrote: >>> On 22 Feb 2018, at 08.45, Matias Bjørling wrote: >>> >>> On 02/21/2018 10:26 AM, Javier González wrote: Complete the generic geometry structure

[PATCH v2] media: stm32-dcmi: rework overrun/error case

Do not stop/restart dma on overrun or errors. Dma will be restarted on current frame transfer completion. Frame transfer completion is ensured even if overrun or error occurs by DCMI continuous capture mode which restarts data transfer at next frame sync. Do no warn on overrun while in irq thread,

[PATCH v2] media: stm32-dcmi: fix lock scheme

Fix lock scheme leading to spurious freeze. Signed-off-by: Hugues Fruchet --- version 2: - dcmi_buf_queue() refactor to avoid to have "else" after "return" (warning detected by checkpatch.pl --strict -f stm32-dcmi.c) drivers/media/platform/stm32/stm32-dcmi.c | 57

Re: [PATCH v2 3/3] mm/sparse: Optimize memmap allocation during sparse_init()

Hi Baoquan, > > In sparse_init(), two temporary pointer arrays, usemap_map and map_map > are allocated with the size of NR_MEM_SECTIONS. They are used to store > each memory section's usemap and mem map if marked as present. With > the help of these two arrays, continuous memory chunk is

Re: [PATCH RFC tools/lkmm 10/12] tools/memory-model: Add a S lock-based external-view litmus test

On Wed, Feb 21, 2018 at 09:42:08PM -0800, Daniel Lustig wrote: > And yes, if we go with a purely RCpc interpretation of acquire and > release, then I don't believe the writes in the previous critical > section would be ordered with the writes in the subsequent critical > section. Excuse my

Re: [PATCH RFC tools/lkmm 10/12] tools/memory-model: Add a S lock-based external-view litmus test

On Thu, Feb 22, 2018 at 02:58:47PM +0800, Boqun Feng wrote: > > And yes, if we go with a purely RCpc interpretation of acquire and > > release, then I don't believe the writes in the previous critical > > section would be ordered with the writes in the subsequent critical > > section. That's

Re: [PATCH v2] usb: host: ehci-platform: add support for optional external vbus supply

Hi, On 02/20/2018 07:10 PM, Alan Stern wrote: > On Tue, 20 Feb 2018, Roger Quadros wrote: > >> On 20/02/18 16:46, Amelie DELAUNAY wrote: >>> Hi, >>> >>> On 02/20/2018 03:00 PM, Roger Quadros wrote: Hi, On 20/02/18 14:58, Amelie Delaunay wrote: > On some boards, especially when

Re: [PATCH RFC tools/lkmm 10/12] tools/memory-model: Add a S lock-based external-view litmus test

On Thu, Feb 22, 2018 at 11:06:36AM +0100, Peter Zijlstra wrote: > On Wed, Feb 21, 2018 at 09:42:08PM -0800, Daniel Lustig wrote: > > And yes, if we go with a purely RCpc interpretation of acquire and > > release, then I don't believe the writes in the previous critical > > section would be ordered

  1   2   3   4   5   6   7   8   9   10   >