On 09.04.2018 8:23, Alexey Budankov wrote:
> On 07.04.2018 9:18, Alexey Budankov wrote:
>> On 06.04.2018 22:53, Andi Kleen wrote:
>>> 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/x
On Sun, Apr 8, 2018 at 4:03 PM, Tomer Maimon wrote:
> This patch Enable ARM L2 cache module in Nuvoton NPCM7xx BMC
> by adding L2 cache parameters into NPCM7xx DT machine start structure.
>
> At patch V7 arm: npcm: add basic support for Nuvoton BMCs we got comments
> regarding the flags use in L2
Tetsuo Handa writes:
> From 904d07a6eb014f3df0c5a1ebfcfd4323276a9a76 Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa
> Date: Tue, 10 Apr 2018 15:15:16 +0900
> Subject: [PATCH] commoncap: Handle memory allocation failure.
>
> syzbot is reporting NULL pointer dereference at xattr_getsecurity() [1],
On Tue, Apr 10, 2018 at 07:13:23PM +0900, Tetsuo Handa wrote:
> syzbot is reporting NULL pointer dereference at xattr_getsecurity() [1],
> for cap_inode_getsecurity() is returning sizeof(struct vfs_cap_data) when
> memory allocation failed. Return -ENOMEM if memory allocation failed.
>
> [1]
> ht
> As far as I understand, all this seems correct to me.
Good. Thank you, Joe!
> You want to maintain the core files in drivers/i2c/
> but not any files in any of algos/, busses/, or muxes/.
More specific: I don't want get_maintainer.pl to print me as a
maintainer for these drivers. This gives a
Hi Marek,
On Tue, Apr 10, 2018 at 4:37 PM, Marek Vasut wrote:
> On 04/10/2018 03:26 PM, Geert Uytterhoeven wrote:
>> On Mon, Apr 9, 2018 at 11:59 PM, Marek Vasut wrote:
>>> On 04/09/2018 02:25 PM, Geert Uytterhoeven wrote:
Currently add_mtd_device() failures are plainly ignored, which may l
On Tue, Apr 10, 2018 at 09:42:50AM -0500, Eric W. Biederman wrote:
> Tetsuo Handa writes:
>
> > From 904d07a6eb014f3df0c5a1ebfcfd4323276a9a76 Mon Sep 17 00:00:00 2001
> > From: Tetsuo Handa
> > Date: Tue, 10 Apr 2018 15:15:16 +0900
> > Subject: [PATCH] commoncap: Handle memory allocation failure
Author: Song Liu
Date: Wed Dec 6 14:45:15 2017 -0800
When running the perf_fuzzer on a current git checkout my logs are flooded
with messages such as this:
[71487.869077] trace_kprobe: Could not insert probe at unknown+0: -22
[71488.174479] trace_kprobe: Could not insert probe at unknown+0: -2
From: Chen Yu
There's a use case during test to only print specific round of loops
if --iterations is specified, for example, with this patch applied:
turbostat -i 5 -t 4
will capture 4 samples with 5 seconds interval.
Signed-off-by: Chen Yu
---
tools/power/x86/turbostat/turbostat.c | 26
Typo...
On 2018-04-10 10:08 PM, yuank...@codeaurora.org wrote:
On 2018-04-10 07:06 PM, Thomas Gleixner wrote:
On Tue, 10 Apr 2018, yuank...@codeaurora.org wrote:
On 2018-04-10 05:10 PM, Thomas Gleixner wrote:
> On Tue, 10 Apr 2018, yuank...@codeaurora.org wrote:
> > On 2018-04-10 04:00 PM, Raf
From: Jason Wang
Date: Tue, 10 Apr 2018 14:40:10 +0800
> On 2018年04月10日 13:26, Stefan Hajnoczi wrote:
>> v2:
>> * Rewrote the conditional to make the vq access check clearer [Linus]
>> * Added Patch 2 to make the return type consistent and harder to misuse
>> * [Linus]
>>
>> The first patch
Remove unnecessary braces {} around an 'if' statement block with a single
statement. Issue found by checkpatch.
Signed-off-by: Eyal Ilsar
---
This is part of my take on the Eudyptula challenge
drivers/staging/wilc1000/wilc_wfi_cfgoperations.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(
Commit-ID: a774635db5c430cbf21fa5d2f2df3d23aaa8e782
Gitweb: https://git.kernel.org/tip/a774635db5c430cbf21fa5d2f2df3d23aaa8e782
Author: Li RongQing
AuthorDate: Tue, 10 Apr 2018 09:16:06 +0800
Committer: Thomas Gleixner
CommitDate: Tue, 10 Apr 2018 16:46:39 +0200
x86/apic: Fix signednes
On Tue, 2018-04-10 at 15:06 +0200, Arnd Bergmann wrote:
> On Tue, Apr 10, 2018 at 2:57 PM, Benjamin Herrenschmidt
> wrote:
> > On Tue, 2018-04-10 at 13:29 +0200, Arnd Bergmann wrote:
> > > In the cases where an ad-hoc interface is needed, I can see
> > > two options: we can stick something in driv
From: Kunihiko Hayashi
Date: Mon, 9 Apr 2018 15:38:42 +0900
> This add the following stuffs to fix the activation issues and satisfy
> requirements for AVE ethernet driver implemented on some UniPhier SoCs.
>
> - Add support for additional necessary clocks and resets, because the kernel
> is
- Capitalize the first word of error messages,
- Unwrap statements that fit on a single line,
- Use "VFIO" instead of "vfio" as the error message prefix.
Signed-off-by: Geert Uytterhoeven
Reviewed-by: Eric Auger
---
v2:
- Add Reviewed-by.
---
drivers/vfio/platform/vfio_platform_common.c
On Tue, Apr 10, 2018 at 10:35:24PM +0800, Jia-Ju Bai wrote:
> hso_create_device() is never called in atomic context.
>
> The call chains ending up at hso_create_device() are:
> [1] hso_create_device() <- hso_create_bulk_serial_device() <- hso_probe()
> [2] hso_create_device() <- hso_create_mux_ser
On 04/10/2018 10:31 AM, Jia-Ju Bai wrote:
>
>
>
> On 2018/4/10 22:27, Boris Ostrovsky wrote:
>> On 04/09/2018 11:03 AM, Jia-Ju Bai wrote:
>>> pcistub_probe() is never called in atomic context.
>>> This function is only set as ".probe" in struct pci_driver.
>>>
>>> Despite never getting called from
Commit 45e01f401a2a16 ("ARM: dts: sunxi: Switch MMC nodes away from
cd-inverted property") changed most of the sunxi boards away from using
the cd-inverted property in MMC nodes. However, the
sun7i-a20-olimex-som204-evb board which got merged concurrently with
that commit is now using cd-inverted.
Hi Geert,
On 10 April 2018 15:29 Geert Uytterhoeven wrote:
> On Tue, Apr 10, 2018 at 4:23 PM, Phil Edworthy wrote:
> > On 10 April 2018 07:24 Phil Edworthy wrote:
> >> On 09 April 2018 20:20 Rob Herring wrote:
> >> > On Wed, Mar 28, 2018 at 03:22:30PM +0100, Phil Edworthy wrote:
> > [...]
> >> > >
Hello Marc, Hello Stephen,
On Tue, 21 Mar 2017 09:43:24 +, Marc Zyngier wrote:
> The whole idea behind this GICD_SETSPI_NSR is to offer a way to signal
> SPIs using memory transaction, even allowing level interrupts (in
> combinaison with the GICD_CLRSPI_NSR at offset 0x48). This is *not* a
>
From: Chen Yu
ThinkPad X1 Tablet(2016) is reported to have issues with
the Low Power S0 Idle _DSM interface and since this machine
model generally can do ACPI S3 just fine, and user would
like to use S3 as default sleep model, add a blacklist
entry to disable that interface for ThinkPad X1 Tablet
Hi,
On Mon, Apr 9, 2018 at 11:36 PM, Manu Gautam wrote:
> Hi,
>
>
> On 3/30/2018 2:24 AM, Doug Anderson wrote:
>> Hi,
>>
>> On Thu, Mar 29, 2018 at 11:44 AM, Doug Anderson
>> wrote:
>>> Hi,
>>>
>>> On Thu, Mar 29, 2018 at 4:04 AM, Manu Gautam wrote:
QMP PHY for USB/PCIE requires pipe_clk
Christian Brauner writes:
> On Mon, Apr 09, 2018 at 06:21:31PM -0500, Eric W. Biederman wrote:
>> Christian Brauner writes:
>>
>> > On Thu, Apr 05, 2018 at 10:59:49PM -0500, Eric W. Biederman wrote:
>> >> Christian Brauner writes:
>> >>
>> >> > On Thu, Apr 05, 2018 at 05:26:59PM +0300, Kirill
On 09/04/2018 22:08, David Rientjes wrote:
> On Mon, 9 Apr 2018, Christoph Hellwig wrote:
>
>>> -#ifdef __HAVE_ARCH_PTE_SPECIAL
>>> +#ifdef CONFIG_ARCH_HAS_PTE_SPECIAL
>>> # define HAVE_PTE_SPECIAL 1
>>> #else
>>> # define HAVE_PTE_SPECIAL 0
>>
>> I'd say kill this odd indirection and just use
On Tue, 2018-04-03 at 18:46 +0100, Ben Hutchings wrote:
> On Fri, 2018-03-23 at 10:54 +0100, Greg Kroah-Hartman wrote:
> > 4.4-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Gao Feng
> >
> >
> > [ Upstream commit 470acf55a021713
On Tue, 2018-04-10 at 16:46 +0200, Wolfram Sang wrote:
> > As far as I understand, all this seems correct to me.
>
> Good. Thank you, Joe!
> /
> > You want to maintain the core files in drivers/i2c/
> > but not any files in any of algos/, busses/, or muxes/.
>
> More specific: I don't want get_ma
On Tue, 2018-04-10 at 14:33 +0200, Peter Zijlstra wrote:
> On Tue, Apr 10, 2018 at 10:00:01AM +0200, Rafael J. Wysocki wrote:
> > On Tue, Apr 10, 2018 at 9:33 AM, wrote:
> > > +++ b/kernel/time/tick-sched.h
> > > @@ -48,8 +48,8 @@ struct tick_sched {
> > > unsigned long
Round two cleans up a few misc script and build items, adds a shadow
variable test, and reduces the total livepatch kselftest runtime to ~45
seconds.
The tests run on top of Petr's v11 atomic replace feature and v2 of the
shadow variable enhancement patchsets:
[PATCH 0/8] livepatch: Atomic repl
Add a few livepatch modules and simple target modules that the included
regression suite can run tests against.
Signed-off-by: Joe Lawrence
---
Documentation/livepatch/callbacks.txt | 487 -
lib/Kconfig.debug | 12 +
lib/Makefile
Hi Nicolin,
On Sun, Apr 8, 2018 at 8:57 PM, Nicolin Chen wrote:
> When the desired ratio is less than 256, the savesub (tolerance)
> in the calculation would become 0. This will then fail the loop-
> search immediately without reporting any errors.
>
> But if the ratio is smaller enough, there is
On 04/10, Matthew Wilcox wrote:
> On Tue, Apr 10, 2018 at 10:45:45PM +0900, Minchan Kim wrote:
> > On Tue, Apr 10, 2018 at 05:53:51AM -0700, Matthew Wilcox wrote:
> > > From: Matthew Wilcox
> > >
> > > The page cache has used the mapping's GFP flags for allocating
> > > radix tree nodes for a lon
On Tue, 10 Apr 2018 16:18:59 +0800
Yulei Zhang wrote:
> Corresponding to the V4 migration patch set for vfio pci device,
> this patch is to implement the new ioctl VFIO_IOMMU_GET_DIRTY_BITMAP
> to fulfill the requirement for vfio-mdev device live migration, which
> need copy the memory that has b
On 10/04/2018 14:38, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistakes in comment and message text
>
> Signed-off-by: Colin Ian King
> ---
> tools/testing/selftests/kvm/lib/kvm_util.c | 2 +-
> tools/testing/selftests/kvm/lib/sparsebit.c | 4 ++--
> 2 files changed
Hi Thomas,
On 10/04/18 16:01, Thomas Petazzoni wrote:
> Hello Marc, Hello Stephen,
>
> On Tue, 21 Mar 2017 09:43:24 +, Marc Zyngier wrote:
>
>> The whole idea behind this GICD_SETSPI_NSR is to offer a way to signal
>> SPIs using memory transaction, even allowing level interrupts (in
>> combi
However my fundamental concerns about the policy whether to disable the sched
tick remain:
Mixing the precise timer and vague heuristic for the decision is
dangerous. The timer should not be wrong, heuristic may be.
Well, I wouldn't say "dangerous". It may be suboptimal, but even that is not
a
On Mon, Apr 9, 2018 at 9:57 AM, Dmitry Vyukov wrote:
> On Mon, Apr 9, 2018 at 7:40 AM, Stephan Mueller wrote:
>> Am Montag, 9. April 2018, 00:46:03 CEST schrieb Theodore Y. Ts'o:
>>
>> Hi Theodore,
>>>
>>> So the syzbot will run while the patch goes through the normal e-mail
>>> review process, w
On Tue, Apr 10, 2018 at 3:57 PM, Jia-Ju Bai wrote:
> intel_scu_ipc_i2c_cntrl() calls mutex_lock(), which indicates
> this function is not called in atomic context.
>
> Despite never getting called from atomic context,
> intel_scu_ipc_i2c_cntrl() calls mdelay to busily wait.
> This is not necessary
> I believe get_maintainer.pl is still going to do that for
> awhile as you are a commit signer for several of these driver
> files.
Okay, I forgot that I use "--no-git" in the config file. Still, while
not perfect, it is one step better.
> btw: You signed-off using 2 different addresses on one
The per architecture __HAVE_ARCH_PTE_SPECIAL is defined statically in the
per architecture header files. This doesn't allow to make other
configuration dependent on it.
The first patch of this series is replacing __HAVE_ARCH_PTE_SPECIAL by
CONFIG_ARCH_HAS_PTE_SPECIAL defined into the Kconfig files
Currently the PTE special supports is turned on in per architecture header
files. Most of the time, it is defined in arch/*/include/asm/pgtable.h
depending or not on some other per architecture static definition.
This patch introduce a new configuration variable to manage this directly
in the Kcon
Remove the additional define HAVE_PTE_SPECIAL and rely directly on
CONFIG_ARCH_HAS_PTE_SPECIAL.
There is no functional change introduced by this patch
Signed-off-by: Laurent Dufour
---
mm/memory.c | 23 ++-
1 file changed, 10 insertions(+), 13 deletions(-)
diff --git a/mm/m
Hi!
This driver implements support for voltage dividers and current
sense shunts. It's pretty generic and should be easily adaptable
to other linear scaling purposes.
Cheers,
Peter
Changes since v2:https://lkml.org/lkml/2018/4/3/461
- Rename from current-sence-circuit to current-sense-shunt
An ADC is often used to measure other quantities indirectly. These
bindings describe two cases, a current through a shunt resistor, and
a "big" voltage measured with the help of a voltage divider.
Signed-off-by: Peter Rosin
---
.../bindings/iio/afe/current-sense-shunt.txt | 41
If an ADC channel measures the midpoint of a voltage divider, the
interesting voltage is often the voltage over the full resistance.
E.g. if the full voltage is too big for the ADC to handle.
Likewise, if an ADC channel measures the voltage across a shunt
resistor, the interesting value is often th
Hey Linus,
Here is the pull request for dmaengine updates for v4.17-rc1. Two new
drivers, updates to couple and off updates to many summarise this request.
Details below:
The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
ar
On Tue, 10 Apr 2018 09:19:26 -0600
Alex Williamson wrote:
> On Tue, 10 Apr 2018 16:18:59 +0800
> Yulei Zhang wrote:
>
> > Corresponding to the V4 migration patch set for vfio pci device,
> > this patch is to implement the new ioctl VFIO_IOMMU_GET_DIRTY_BITMAP
> > to fulfill the requirement for
On Mon, Apr 09, 2018 at 08:41:18PM -0400, Frank Mori Hess wrote:
> On Tue, Mar 13, 2018 at 2:34 PM, Frank Mori Hess wrote:
> > Do DMAFLUSHP _before_ the first DMAWFP to ensure controller
> > and peripheral are in agreement about dma request state before first
> > transfer. Add support for burst t
On Mon, Apr 09, 2018 at 04:14:20PM -0700, Laura Abbott wrote:
> On 04/09/2018 03:48 PM, Sinan Kaya wrote:
> >On 4/9/2018 5:06 PM, Laura Abbott wrote:
> >>+ /* dst_cnt can't be more than u8 */
> >>+ dma_addr_t dma_pq[255];
> >
> >This is 2k stack space on 64 bit a
On Mon, Apr 09, 2018 at 01:14:58PM +, David Laight wrote:
> From: kpark3...@gmail.com
> > Sent: 09 April 2018 12:59
> >
> > The old arch_within_stack_frames which used the frame pointer is
> > now reimplemented to use frame pointer unwinder apis. So the main
> > functionality is same as before.
On 10/04/18 15:22, Dan Carpenter wrote:
> On Tue, Apr 10, 2018 at 02:41:23PM +0100, Colin King wrote:
>> From: Colin Ian King
>>
>> Currently function __load_ucode_amd can assign an uninitialized cp to *ret
>> if get_builtin_microcode returns false.
>
> What are you looking at? Here is how it lo
Am Dienstag, 10. April 2018, 17:23:46 CEST schrieb Dmitry Vyukov:
Hi Dmitry,
> Stephan,
>
> Do you have any hypothesis as to why this is not detected by KASAN and
> causes silent corruptions?
> We generally try to understand such cases and improve KASAN so that it
> catches such cases more relia
Am Dienstag, 10. April 2018, 15:52:25 CEST schrieb Minas Harutyunyan:
> Hi Heiko,
>
> On 4/10/2018 4:28 PM, Heiko Stuebner wrote:
> > Am Montag, 26. März 2018, 11:00:01 CEST schrieb Tomeu Vizoso:
> >> devm_regulator_get_optional returns -ENODEV if the regulator isn't
> >> there, so if that's the c
Store user space frame-pointer value (BP register) into Perf trace
on a sample for a process so the value becomes available when
unwinding call stacks for functions gaining event samples.
Test executable for the example below was compiled with frame pointer
support enabled:
g++ -o futex-fp -f
On 2018-04-10 16:11, Wolfram Sang wrote:
> The number of I2C host controller drivers keeps increasing, and although
> I had some success acquiring specific driver maintainers, my bandwidth
> is by far not enough to act as a fallback for the rest of the drivers.
> To reflect this status-quo in MAINT
Using bool in a bitfield isn't a good idea as the
alignment behavior is arch implementation defined.
Suggest using unsigned int or u<8|16|32> instead.
Signed-off-by: Joe Perches
Suggested-by: Peter Zijlstra
---
scripts/checkpatch.pl | 6 ++
1 file changed, 6 insertions(+)
diff --git a/scr
Hello,
Thanks for your feedback!
On Tue, 10 Apr 2018 16:23:00 +0100, Marc Zyngier wrote:
> > In the current Marvell Armada 7K/8K, we have a unit called the ICU
> > that turns wired level interrupts on one side of the chip into MSIs,
> > signaled to the GIC through a special unit called GICP, whi
On Fri, Apr 06, 2018 at 11:30:14AM -0700, Ashok Raj wrote:
> Hi Greg
>
> Here is a series that addresses microcode loading stability issues post
> Spectre. All of them are simply cherry-picked and the patches themselves
> have the upstream commit ID's.
>
> I checked this for Intel platforms and
On Tue, 2018-04-10 at 09:06 -0500, Tom Lendacky wrote:
>
> Just out of curiosity, can you try the following patch and see if it
> fixes your reboot issue:
Yup, all better.
> diff --git a/arch/x86/boot/compressed/kaslr.c
> b/arch/x86/boot/compressed/kaslr.c
> index c5196d2..a0a50b9 100644
> --- a
Em Tue, Apr 10, 2018 at 11:55:15AM +0100, Mark Rutland escreveu:
> On Mon, Apr 09, 2018 at 04:40:32PM -0300, Arnaldo Carvalho de Melo wrote:
> > Now 'make LIBCLANGLLVM=1 -C tools/perf' works, but I'll look at the
> > patch below, probably it will save some time in the future if we get to
> > includ
Hi,
> Am 10.04.2018 um 16:41 schrieb Andy Shevchenko :
>
> On Wed, Apr 4, 2018 at 10:00 PM, H. Nikolaus Schaller
> wrote:
>> PCAL chips ("L" seems to stand for "latched") have additional
>> registers starting at address 0x40 to control the latches,
>> interrupt mask, pull-up and pull down etc.
Hi Peter,
> Hmm, I think you are ducking out from the i2c-mux-pinctrl driver as well.
> Was that the intent?
Oops, nope! Sorry, I just forgot about the demux (I think you mean that
one) driver and will create a seperate entry for it.
>
> > +I2C SUBSYSTEM DRIVERS
> > +L: linux-...@vger.kernel.or
Hi all,
This patch series improves reset support for vfio-platform:
- The first patch fixes a bug I ran into while working on this.
- The second patch implements generic DT reset controller support, for
devices that are connected to an SoC-internal reset controller and
can be r
Vfio-platform requires reset support, provided either by ACPI, or, on DT
platforms, by a device-specific reset driver matching against the
device's compatible value.
On many SoCs, devices are connected to an SoC-internal reset controller.
If the reset hierarchy is described in DT using "resets" pr
If the IOMMU group setup fails, the reset module is not released.
Fixes: b5add544d677d363 ("vfio, platform: make reset driver a requirement by
default")
Signed-off-by: Geert Uytterhoeven
Reviewed-by: Eric Auger
---
v2:
- Add Reviewed-by.
---
drivers/vfio/platform/vfio_platform_common.c | 15
On Tue, Apr 10, 2018 at 09:21:20AM -0500, Christopher Lameter wrote:
> On Tue, 10 Apr 2018, Matthew Wilcox wrote:
>
> > __GFP_ZERO requests that the object be initialised to all-zeroes,
> > while the purpose of a constructor is to initialise an object to a
> > particular pattern. We cannot do bot
This patch fixes some indentation issues and does not modify the
functionality of the driver.
Signed-off-by: Stefan Popa
---
drivers/iio/dac/ad5686.c | 25 ++---
1 file changed, 14 insertions(+), 11 deletions(-)
diff --git a/drivers/iio/dac/ad5686.c b/drivers/iio/dac/ad5686.
This patch adds a new num_channels attribute as part of the
ad5686_chip_info struct which replaces the AD5686_DAC_CHANNELS define. This
is a necessary step, since this driver should support similar devices which
differ only in the number of channels.
Signed-off-by: Stefan Popa
---
Changes in v2:
This driver acctually supports the AD5685R device and NOT the AD5685, which
does not exist.
More information can be found in the datasheet:
http://www.analog.com/media/en/technical-documentation/data-sheets/AD5686_5684.pdf
Signed-off-by: Stefan Popa
---
Changes in v2:
- Refactored the pa
The AD5684R/AD5686R are a family of 4 channel DACs with 12-bit, 14-bit and
16-bit precision respectively. The devices come either with a built-in
reference or no built-in reference.
The AD5672R/AD5676/AD5676R are similar, except that they have 8 channels
instead of 4.
Datasheets:
http://www.analo
In this patch restructures the existing ad5686 driver by adding a module
for SPI and a header file, while the baseline module deals with the
chip-logic.
This is a necessary step, as this driver should support in the future
similar devices which differ only in the type of interface used (I2C
instea
The AD5694/AD5694R/AD5695R/AD5696/AD5696R are a family of 4 channel DACs
with 12-bit, 14-bit and 16-bit precision respectively. The devices have
either no built-in reference, or built-in 2.5V reference.
The AD5671R/AD5675R are similar, except that they have 8 instead of 4
channels.
These devices
The iowait boosting code has been recently updated to add a progressive
boosting behavior which allows to be less aggressive in boosting tasks
doing only sporadic IO operations, thus being more energy efficient for
example on mobile platforms.
The current code is now however a bit convoluted. Some
On 10/04/18 16:25, Laurent Dufour wrote:
Remove the additional define HAVE_PTE_SPECIAL and rely directly on
CONFIG_ARCH_HAS_PTE_SPECIAL.
There is no functional change introduced by this patch
Signed-off-by: Laurent Dufour
---
mm/memory.c | 23 ++-
1 file changed, 10 inse
V3:
* add Reported-by: and Reviewed-by:
* fix working for bindings description and example
* convert all register offsets to hex
* omit the LEVEL-IRQ RFC/hack commit
2018-04-04 21:00:27: V2:
* added PCA_PCAL flags if matched through of-table
* fix address calculation for extended PCAL6524 register
The of_device_table is missing the PCA_PCAL flag so the
pcal6524 would be operated in tca6424 compatibility mode which
does not handle the new interrupt mask registers.
Suggested-by: Andy Shevchenko
Signed-off-by: H. Nikolaus Schaller
---
drivers/gpio/gpio-pca953x.c | 6 --
1 file changed,
Hardware can have a switchable Vcc supply, so let's add it to
the bindings (the current Linux driver code already supports it).
Signed-off-by: H. Nikolaus Schaller
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/gpio/gpio-pca953x.txt | 1 +
1 file changed, 1 insertion(+)
diff --
Hi Andy,
> Am 10.04.2018 um 16:38 schrieb Andy Shevchenko :
>
> On Wed, Apr 4, 2018 at 10:00 PM, H. Nikolaus Schaller
> wrote:
>
>> in driver code. Therefore, the pca953x driver rejects the
>> setup of the irq because it can only handle EDGE interrupts
>> so far.
>>
>> This hack translates le
It is not completely obvious that these are required and
how to use them. So we provide a tested example.
Signed-off-by: H. Nikolaus Schaller
---
.../devicetree/bindings/gpio/gpio-pca953x.txt | 33 ++
1 file changed, 33 insertions(+)
diff --git a/Documentation/devicetre
PCAL chips ("L" seems to stand for "latched") have additional
registers starting at address 0x40 to control the latches,
interrupt mask, pull-up and pull down etc.
The constants are so far defined in a way that they fit for
the pcal9555a when shifted by the number of banks, i.e. multiplied
by 2.
On Tue, Apr 10, 2018 at 05:25:50PM +0200, Laurent Dufour wrote:
> arch/powerpc/include/asm/pte-common.h | 3 ---
> arch/riscv/Kconfig | 1 +
> arch/s390/Kconfig | 1 +
You forgot to delete __HAVE_ARCH_PTE_SPE
On Sun, 08 Apr 2018, Eric Biggers wrote:
@@ -480,6 +487,7 @@ static int shm_release(struct inode *ino, struct file *file)
struct shm_file_data *sfd = shm_file_data(file);
put_ipc_ns(sfd->ns);
+ fput(sfd->file);
shm_file_data(file) = NULL;
kfree(sfd);
On 10/04/18 16:41, Thomas Petazzoni wrote:
> Hello,
>
> Thanks for your feedback!
>
> On Tue, 10 Apr 2018 16:23:00 +0100, Marc Zyngier wrote:
>
>>> In the current Marvell Armada 7K/8K, we have a unit called the ICU
>>> that turns wired level interrupts on one side of the chip into MSIs,
>>> sign
On 04/10/18 08:58, Stefan Popa wrote:
> The AD5694/AD5694R/AD5695R/AD5696/AD5696R are a family of 4 channel DACs
> with 12-bit, 14-bit and 16-bit precision respectively. The devices have
> either no built-in reference, or built-in 2.5V reference.
>
> The AD5671R/AD5675R are similar, except that th
On 03/04/2018 02:11, David Rientjes wrote:
> On Tue, 13 Mar 2018, Laurent Dufour wrote:
>
>> This change is inspired by the Peter's proposal patch [1] which was
>> protecting the VMA using SRCU. Unfortunately, SRCU is not scaling well in
>> that particular case, and it is introducing major perfo
On Tue, Apr 10, 2018 at 02:15:46PM +0200, KarimAllah Ahmed wrote:
> The VMX-preemption timer is used by KVM as a way to set deadlines for the
> guest (i.e. timer emulation). That was safe till very recently when
> capability KVM_X86_DISABLE_EXITS_MWAIT to disable intercepting MWAIT was
> introduced
On 4/10/18 5:28 AM, Cyrill Gorcunov wrote:
On Tue, Apr 10, 2018 at 01:10:01PM +0200, Michal Hocko wrote:
Because do_brk does vma manipulations, for this reason it's
running under down_write_killable(&mm->mmap_sem). Or you
mean something else?
Yes, all we need the new lock for is to get a cons
Hi,
we just started testing the v4.16 kernel and found the
device no longer bootable (works with v4.15). It turned
out that there was a harmful modification somewhere between
v4.15.0 and v4.16-rc1.
A git bisect points to this patch:
commit bdaca9345d41fd9420995469d27603ea62054691
Author: Ladislav
On 03/04/2018 01:57, David Rientjes wrote:
> On Tue, 13 Mar 2018, Laurent Dufour wrote:
>
>> When dealing with speculative page fault handler, we may race with VMA
>> being split or merged. In this case the vma->vm_start and vm->vm_end
>> fields may not match the address the page fault is occurrin
On Tue, Apr 10, 2018 at 08:14:54AM -0700, Joe Perches wrote:
> Whinging about bool : seems entirely sensible
> and straightforward to do.
>
> I'm not so sure about bool in structs as a patch context
> could be adding a bool to local stack definitions and
> there's no real ability to determine if
On Sun, Apr 08, 2018 at 08:41:21PM +0200, Wenhua Shi wrote:
> 2018-04-08 18:51 GMT+02:00 David Miller :
> >
> > From: Wenhua Shi
> > Date: Fri, 6 Apr 2018 03:43:39 +0200
> >
> > > Signed-off-by: Wenhua Shi
> >
> > This precondition should be made impossible instead of having to do
> > an extra c
On Tue, Apr 10, 2018 at 7:47 AM, Geert Uytterhoeven
wrote:
> Hi Marek,
>
> On Tue, Apr 10, 2018 at 4:37 PM, Marek Vasut wrote:
>> On 04/10/2018 03:26 PM, Geert Uytterhoeven wrote:
>>> On Mon, Apr 9, 2018 at 11:59 PM, Marek Vasut wrote:
On 04/09/2018 02:25 PM, Geert Uytterhoeven wrote:
>
Hi Linus,
The following changes since commit 0adb32858b0bddf4ada5f364a84ed60b196dbcda:
Linux 4.16 (2018-04-01 14:20:27 -0700)
are available in the git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-4.17-rc1
for you to fetch changes up to 9122eed5281e89bdb02162a8ecb3cc
By applying well known spin-on-lock-owner techniques, we can avoid the
blocking overhead during the process of when the task is trying to take
the rtmutex. The idea is that as long as the owner is running, there is a
fair chance it'll release the lock soon, and thus a task trying to acquire
the rtm
This field (debug) is unused. Furthermore it looks like a result
of rtmutex from -rt into upstream, where it serves to determine
if the wakeup is for a task blocked on a "sleeping spinlock",
iow if this is a regular rt_mutex_lock() or rt_spin_lock().
Of course, upstream we only have regular rt_mut
On 2018-04-10 17:52, Wolfram Sang wrote:
> Hi Peter,
>
>> Hmm, I think you are ducking out from the i2c-mux-pinctrl driver as well.
>> Was that the intent?
>
> Oops, nope! Sorry, I just forgot about the demux (I think you mean that
> one) driver and will create a seperate entry for it.
Right, I
On 10/04/2018 18:09, Matthew Wilcox wrote:
> On Tue, Apr 10, 2018 at 05:25:50PM +0200, Laurent Dufour wrote:
>> arch/powerpc/include/asm/pte-common.h | 3 ---
>> arch/riscv/Kconfig | 1 +
>> arch/s390/Kconfig
On 10/04/2018 17:58, Robin Murphy wrote:
> On 10/04/18 16:25, Laurent Dufour wrote:
>> Remove the additional define HAVE_PTE_SPECIAL and rely directly on
>> CONFIG_ARCH_HAS_PTE_SPECIAL.
>>
>> There is no functional change introduced by this patch
>>
>> Signed-off-by: Laurent Dufour
>> ---
>> m
Hi Steve,
On Tue, Apr 10, 2018 at 6:13 AM, Steven Rostedt wrote:
> On Tue, 10 Apr 2018 08:36:25 -0400
> Steven Rostedt wrote:
>
>> On Tue, 10 Apr 2018 14:27:06 +0200
>> Michal Hocko wrote:
>>
>> > I would rather that the code outside of MM not touch implementation
>> > details like OOM_SCORE_AD
On Tue, 2018-04-10 at 18:42 +0200, Peter Rosin wrote:
> On 2018-04-10 17:52, Wolfram Sang wrote:
> > Hi Peter,
> >
> > > Hmm, I think you are ducking out from the i2c-mux-pinctrl driver as well.
> > > Was that the intent?
> >
> > Oops, nope! Sorry, I just forgot about the demux (I think you mean
501 - 600 of 1296 matches
Mail list logo
