From: Alastair D'Silva
> Sent: 08 May 2019 08:02
> To: alast...@d-silva.org
...
> --- a/include/linux/printk.h
> +++ b/include/linux/printk.h
> @@ -480,13 +480,13 @@ enum {
> DUMP_PREFIX_OFFSET
> };
>
> -extern int hex_dump_to_buffer(const void *buf, size_t len, int rowsize,
> -
Support Fingerprint MCU as a special of CrOS EC devices. The current FP
MCU uses the same EC SPI protocol v3 as other CrOS EC devices on a SPI
bus.
When a MCU has fingerprint support (aka EC_FEATURE_FINGERPRINT), it is
instantiated as a special CrOS EC device with device name 'cros_fp'. So
regardl
Hi Lee,
Sorry for the delay, this is a new version rebased on top of
for-mfd-next tree solvind the conflicts with due the already applied
patches.
The first version depends on:
- mfd: cros: Update EC protocol to match current EC code
- https://lore.kernel.org/patchwork/patch/1046363
But there
Hi,
On 08-05-19 10:42, Andy Shevchenko wrote:
On Wed, May 8, 2019 at 10:48 AM Hans de Goede wrote:
On 07-05-19 22:17, Stephen Boyd wrote:
Quoting Hans de Goede (2019-05-06 08:05:42)
I guess this is urgent?
Somewhat, getting this into e.g. rc2 would be fine too, waiting till 5.3
would be
I'm announcing the release of the 4.9.174 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Documentation/usb/power-management.txt
b/Documentation/usb/power-management.txt
index 0a94ffe17ab6..b13e031beaa6 100644
--- a/Documentation/usb/power-management.txt
+++ b/Documentation/usb/power-management.txt
@@ -365,11 +365,15 @@ autosuspend the interface's device. When the usage
I'm announcing the release of the 4.14.117 kernel.
All users of the 4.14 kernel series must upgrade.
The updated 4.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.14.y
and can be browsed at the normal kernel.org git web browser
diff --git a/Documentation/driver-api/usb/power-management.rst
b/Documentation/driver-api/usb/power-management.rst
index 79beb807996b..4a74cf6f2797 100644
--- a/Documentation/driver-api/usb/power-management.rst
+++ b/Documentation/driver-api/usb/power-management.rst
@@ -370,11 +370,15 @@ autosuspe
On 08/05/19 10:14, luca abeni wrote:
> Hi Juri,
>
> On Wed, 8 May 2019 10:01:16 +0200
> Juri Lelli wrote:
>
> > Hi Luca,
> >
> > On 06/05/19 06:48, Luca Abeni wrote:
> > > From: luca abeni
> > >
> > > Currently, the scheduler tries to find a proper placement for
> > > SCHED_DEADLINE tasks whe
I'm announcing the release of the 5.0.14 kernel.
All users of the 5.0 kernel series must upgrade.
The updated 5.0.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-5.0.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Documentation/driver-api/usb/power-management.rst
b/Documentation/driver-api/usb/power-management.rst
index 79beb807996b..4a74cf6f2797 100644
--- a/Documentation/driver-api/usb/power-management.rst
+++ b/Documentation/driver-api/usb/power-management.rst
@@ -370,11 +370,15 @@ autosuspe
diff --git a/Documentation/driver-api/usb/power-management.rst
b/Documentation/driver-api/usb/power-management.rst
index 79beb807996b..4a74cf6f2797 100644
--- a/Documentation/driver-api/usb/power-management.rst
+++ b/Documentation/driver-api/usb/power-management.rst
@@ -370,11 +370,15 @@ autosuspe
I'm announcing the release of the 4.19.41 kernel.
All users of the 4.19 kernel series must upgrade.
The updated 4.19.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.19.y
and can be browsed at the normal kernel.org git web browser:
On 05/05/2019 19:12, Dmitry Osipenko wrote:
> The DMA_PREP_INTERRUPT flag means that descriptor's callback should be
> invoked upon transfer completion and that's it. For some reason driver
> completely disables the hardware interrupt handling, leaving channel in
> unusable state if transfer is i
On Wed, 8 May 2019 11:08:55 +0200
Juri Lelli wrote:
> On 06/05/19 06:48, Luca Abeni wrote:
> > From: luca abeni
> >
> > Instead of considering the "static CPU bandwidth" allocated to
> > a SCHED_DEADLINE task (ratio between its maximum runtime and
> > reservation period), try to use the remaini
Hi Krzysztof,
On 5/8/19 9:11 AM, Krzysztof Kozlowski wrote:
> ())On Mon, 6 May 2019 at 17:12, Lukasz Luba
> wrote:
>>
>> This patch adds driver for Exynos5422 Dynamic Memory Controller.
>> The driver provides support for dynamic frequency and voltage scaling for
>> DMC and DRAM. It supports chan
On Thu, May 02, 2019 at 01:50:22PM +0300, Alexander Shishkin wrote:
> The output setting is per-CPU, so all PEBS events must be either writing
> to PT or to the DS area, so in order to not mess up the event scheduling,
> we fall back to the latter in case both types of events are scheduled in.
>
On 05/08/19 at 11:04am, Borislav Petkov wrote:
> On Wed, May 08, 2019 at 04:24:18PM +0800, Baoquan He wrote:
> > I think this's worth noticing stable tree:
> >
> > Cc: sta...@vger.kernel.org
>
> Fixes: ?
Not sure which commit validated 5-level.
Hi Kirill,
Is this commit OK?
Fiexes: eedb92abb9
Steven Rostedt writes:
> [
> This is the non-RFC version.
>
> It went through and passed all my tests. If there's no objections
> I'm going to include this in my pull request. I still have patches
> in my INBOX that may still be included, so I need to run those through
> my tests as wel
Le 04/05/2019 à 18:48, Colin King a écrit :
From: Colin Ian King
Currently an int is being shifted and the result is being cast to a u64
which leads to undefined behaviour if the shift is more than 31 bits. Fix
this by casting the integer value 1 to u64 before the shift operation.
Addresses-Co
On 18/04/2019 14:57, Zhen Lei wrote:
First, add build option IOMMU_DEFAULT_{LAZY|STRICT}, so that we have the
opportunity to set {lazy|strict} mode as default at build time. Then put
the three config options in an choice, make people can only choose one of
the three at a time.
The default IOMMU
On 5/8/19 9:19 AM, Krzysztof Kozlowski wrote:
> On Tue, 7 May 2019 at 19:04, Rob Herring wrote:
>>> +- devfreq-events : phandles of the PPMU events used by the controller.
>>> +- samsung,syscon-chipid : phandle of the ChipID used by the controller.
>>> +- samsung,syscon-clk : phandle of the cloc
> On Wed, 8 May 2019 09:16:38 +, Rob Herring wrote:
> On Tue, 7 May 2019 09:16:38 +, Robin Gong wrote:
> > Add i.mx6ul and i.mx6sx compatible name.
> >
> > Signed-off-by: Robin Gong
> > ---
> > Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt | 2 ++
> > 1 file changed, 2 insertions
On Tue, Apr 23, 2019 at 04:26:36PM +0200, Sebastian Andrzej Siewior wrote:
> In commit 4b53a3412d66 ("sched/core: Remove the tsk_nr_cpus_allowed()
> wrapper") the tsk_nr_cpus_allowed() wrapper was removed. There was not
> much difference in !RT but in RT we used this to implement
> migrate_disable(
On Tue, May 07, 2019 at 01:33:06PM -0700, Linus Torvalds wrote:
> On Tue, May 7, 2019 at 10:59 AM Greg KH wrote:
> >
> > All of these have been in linux-next for a while with no reported
> > issues, other than an odd gcc warning for one of the new drivers that
> > should be fixed up soon.
>
> Ok,
On 5/8/19 9:22 AM, Krzysztof Kozlowski wrote:
> On Mon, 6 May 2019 at 17:12, Lukasz Luba wrote:
>>
>> In order get the clock by phandle and use it with regmap it needs to be
>> compatible with syscon. The DMC driver uses two registers from clock
>> register set and needs the regmap of them.
>>
>
On 5/8/19 9:25 AM, Krzysztof Kozlowski wrote:
> On Mon, 6 May 2019 at 17:12, Lukasz Luba wrote:
>>
>> Add description of Dynamic Memory Controller and PPMU counters.
>> They are used by exynos5422-dmc driver.
>> There is a definition of the memory chip, which is then used during
>> calculation
This patch changes the order of checks when initializing the device CPU.
We want first to check if we need to load the F/W, and only if we need to,
then we want to check the status of the CPU boot program.
Signed-off-by: Oded Gabbay
---
drivers/misc/habanalabs/goya/goya.c | 6 +++---
1 file chan
Hi,
On Wed, May 08, 2019 at 03:09:36PM +0900, Mark Brown wrote:
> On Tue, May 07, 2019 at 02:07:30PM +0200, Sebastian Reichel wrote:
> > FWIW, I send out kernel.org mails via mail.kernel.org. Konstantin
> > added that service in 2014. You can get a password with
>
> > ssh g...@gitolite.kernel.org
On Mon, May 06, 2019 at 08:50:45AM +0200, Johannes Thumshirn wrote:
> Acked-by: Johannes Thumshirn
Queued, thanks.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Hi
On 2019-05-07 15:24, Måns Rullgård wrote:
> Marek Szyprowski writes:
>> Commit 01fdf179f4b0 ("usb: core: skip interfaces disabled in devicetree")
>> add support for disabling given USB device interface by adding nodes to
>> the USB host controller device. The mentioned commit however identifie
Add a mailing list for patch reviews and discussions related to TEE
subsystem.
Signed-off-by: Sumit Garg
---
MAINTAINERS | 3 +++
1 file changed, 3 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 920a0a1..c05dff7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -11556,11 +11556,13 @@ F:
On Wed, 8 May 2019 at 11:50, Lukasz Luba wrote:
>
>
> On 5/8/19 9:22 AM, Krzysztof Kozlowski wrote:
> > On Mon, 6 May 2019 at 17:12, Lukasz Luba wrote:
> >>
> >> In order get the clock by phandle and use it with regmap it needs to be
> >> compatible with syscon. The DMC driver uses two registers
On Wed, 8 May 2019 at 11:45, Lukasz Luba wrote:
>
>
> On 5/8/19 9:19 AM, Krzysztof Kozlowski wrote:
> > On Tue, 7 May 2019 at 19:04, Rob Herring wrote:
> >>> +- devfreq-events : phandles of the PPMU events used by the controller.
> >>> +- samsung,syscon-chipid : phandle of the ChipID used by the
On Wed, May 08, 2019 at 03:09:36PM +0900, Mark Brown wrote:
> On Tue, May 07, 2019 at 02:07:30PM +0200, Sebastian Reichel wrote:
>
> > FWIW, I send out kernel.org mails via mail.kernel.org. Konstantin
> > added that service in 2014. You can get a password with
>
> > ssh g...@gitolite.kernel.org g
The subject line is not correct. This is an MFD driver.
When submitting you should follow the convention for the subsystem you
are patching against. The following command is helpful:
`git log --oneline -- `
I will fix it for you this time (and for the other patch I see).
On Mon, 22 Apr 2019
On Tue, 23 Apr 2019, Kefeng Wang wrote:
> Using dev_get_drvdata directly.
>
> Cc: Andy Gross
> Cc: David Brown
> Cc: Lee Jones
> Cc: linux-arm-...@vger.kernel.org
> Signed-off-by: Kefeng Wang
> ---
> drivers/mfd/ssbi.c | 2 +-
> drivers/mfd/t7l66xb.c | 12
> drivers/mfd/tc
On Thu, 18 Apr 2019, Jan Kiszka wrote:
> From: Su Bao Cheng
>
> Since there are more IOT2040 variants with identical hardware but
> different asset tags, the asset tag matching should be adjusted to
> support them.
>
> For the board name "SIMATIC IOT2000", currently there are 2 types of
> hardw
> -Original Message-
> From: Wen He
> Sent: 2019年5月8日 17:42
> To: dri-de...@lists.freedesktop.org; p.za...@pengutronix.de
> Cc: Leo Li ; Wen He
> Subject: [v1] gpu: ipu-v3: allow to build with ARCH_LAYERSCAPE
>
> The new LS1028A DP driver code causes a link failure when DRM_IMX built-in
The following changes since commit 085b7755808aa11f78ab9377257e1dad2e6fa4bb:
Linux 5.1-rc6 (2019-04-21 10:45:57 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tags/tty-5.2-rc1
for you to fetch changes up to 45c054d0815b1530d7c7ff8
On Fri, 26 Apr 2019, Steve Twiss wrote:
> Mismatch between what is found in the Datasheets for DA9063 and DA9063L
> provided by Dialog Semiconductor, and the register names provided in the
> MFD registers file. The changes are for the OTP (one-time-programming)
> control registers. The two naming
On Wed, May 08, 2019 at 12:13:01PM +0200, Sebastian Reichel wrote:
> On Wed, May 08, 2019 at 03:09:36PM +0900, Mark Brown wrote:
> > I'd have to send all mail out via kernel.org to do that, or persuade a
> > MTA to route mail differently based on contents which seems interesting
> > - I inject mos
On Fri, 19 Apr 2019, Chen-Yu Tsai wrote:
> From: Chen-Yu Tsai
>
> The AXP803 has a VBUS power input. Its functionality is the same as the
> one found in the AXP813. Now that the axp20x_usb_power driver supports
> this variant, we can add an mfd cell for it to use it.
>
> Signed-off-by: Chen-Yu
The following changes since commit 37624b58542fb9f2d9a70e6ea006ef8a5f66c30b:
Linux 5.1-rc7 (2019-04-28 17:04:13 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git tags/usb-5.2-rc1
for you to fetch changes up to 3515468a87a47781f6af818
Hello.
We are again getting corrupted reports where message from WARN() is missing.
For example, https://syzkaller.appspot.com/text?tag=CrashLog&x=1720cac8a0
was
titled as "WARNING in cgroup_exit" because the
"WARNING: CPU: 0 PID: 7870 at kernel/cgroup/cgroup.c:6008
cgroup_exit+0x51a/0x5d0"
The patch
spi: rockchip: turn down tx dma bursts
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus dur
On Thu, May 02, 2019 at 01:50:20PM +0300, Alexander Shishkin wrote:
> Hi Peter,
>
> New PEBS feature: output to Intel PT stream instead of the DS area. It's
> theoretically useful in virtualized environments, where DS area can't be
> used. It's also good for those who are interested in instruction
The LS1028A has a LCD controller and Displayport interface that
connects to eDP and Displayport connectors on the LS1028A board.
This patch enables the LCD controller driver on the LS1028A.
Signed-off-by: Alison Wang
Signed-off-by: Wen He
Reviewed-by: Liviu Dudau
Reviewed-by: Rob Herring
---
Commit 01fdf179f4b0 ("usb: core: skip interfaces disabled in devicetree")
add support for disabling given USB device interface by adding nodes to
the USB host controller device. The mentioned commit however identifies
the given USB interface node only by the 'reg' property in the host
controller ch
This patch enables the HDP controller driver on the LS1028A.
Signed-off-by: Alison Wang
Signed-off-by: Wen He
---
.../arm64/boot/dts/freescale/fsl-ls1028a.dtsi | 25 +++
1 file changed, 25 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
b/arch/arm64/b
This patch add HDP PHY Controller related nodes on the LS1028ARDB.
Now LS1028ARDB on DP has following features:
- Supports 4 dp lane channel and lane mapping is 1-0-3-2.
- By default, the pixel link rate value's 27Mhz.
- By default, support the resoluions are 4k@60,1080p@60,720p@60,
480p@60. also u
Add DT bindings documentmation for the HDP-TX PHY controller. The describes
which could be found on NXP Layerscape ls1028a platform.
Signed-off-by: Wen He
---
.../devicetree/bindings/display/fsl,hdp.txt | 56 +++
1 file changed, 56 insertions(+)
create mode 100644 Documentatio
This patch add HDP PHY Controller related nodes on the LS1028AQDS.
Now LS1028AQDS on DP has following features:
- Supports 4 dp lane channel and lane mapping is 1-0-3-2.
- By default, the pixel link rate value's 27Mhz.
- By default, support the resoluions are 4k@60,1080p@60,720p@60,
480p@60. also u
Hi Stephan,
We think the cast is fine, and it cannot guarantee the buf is
word-align.
I reference multiple rng driver's implementation and found it's common
usage for this. So it might be general usage for community. Is there any
suggestion that is more appropriate?
Thanks
A bug was introduced by commit b3b576461864 ("tty: serial_core: convert
uart_open to use tty_port_open"). It caused a constant warning printed
into the system log regarding the tty and port counter mismatch:
[ 21.644197] ttyS ttySx: tty_port_close_start: tty->count = 1 port count = 2
in case if
Hi Jose,
> -Original Message-
> From: Jose Abreu
> Sent: Wednesday, May 8, 2019 10:29 AM
> To: Eugeniy Paltsev ; jose.ab...@synopsys.com;
> linux-kernel@vger.kernel.org;
> Vineet Gupta ; devicet...@vger.kernel.org;
> linux-snps-...@lists.infradead.org
> Cc: joao.pi...@synopsys.com; vine
On Wed, 24 Apr 2019, Gwendal Grignou wrote:
> Add a IIO driver that reports the angle between the lid and the base for
> ChromeOS convertible device.
>
> Tested on eve with ToT EC firmware.
> Check driver is loaded and lid angle is correct.
>
> Signed-off-by: Gwendal Grignou
> ---
> Changes in
On Wed, May 08, 2019 at 07:58:26AM +0200, hotwater...@tutanota.com wrote:
> Hello guys, any updates on suspend issue?
Please, do not top-post.
The patch you mentioned is in a queue to be submitted after merge window closes.
Be patient.
--
With Best Regards,
Andy Shevchenko
On Wed, 08 May 2019, Mark Brown wrote:
> The patch
>
>dt-bindings: mfd: atmel-usart: add DMA bindings for USART in SPI mode
>
> has been applied to the spi tree at
>
>https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.3
>
> All being well this means that it will be i
From: Colin Ian King
The pointer l2_hdr is being assigned to itself, this is redundant
and can be removed.
Addresses-Coverity: ("Evaluation order violation")
Signed-off-by: Colin Ian King
---
drivers/net/ethernet/hisilicon/hns3/hns3_enet.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
* Yan Zhao (yan.y.z...@intel.com) wrote:
> This feature implements the version attribute for Intel's vGPU mdev
> devices.
>
> version attribute is rw.
> It's used to check device compatibility for two mdev devices.
> version string format and length are private for vendor driver. vendor
> driver i
On Sun, 28 Apr 2019, S.j. Wang wrote:
> Add macros to define masks and bits for imx6sx MQS registers
>
> Signed-off-by: Shengjiu Wang
> ---
> include/linux/mfd/syscon/imx6q-iomuxc-gpr.h | 9 +
> 1 file changed, 9 insertions(+)
Applied, thanks.
--
Lee Jones [李琼斯]
Linaro Services Techn
On Fri, 05 Apr 2019, Dan Murphy wrote:
> Fix the lm3632 dt binding examples as the LCM enable GPIOs
> are defined as enable GPIOs per the regulator/lm363x-regulator.txt
> bindings document.
>
> Signed-off-by: Dan Murphy
> ---
> Documentation/devicetree/bindings/mfd/ti-lmu.txt | 4 ++--
Applied,
Hi Prarit,
On Tue, May 07, 2019 at 10:54:13AM -0400, Prarit Bhargava wrote:
> Heiko, it would still be good to get a test of this patch from you. I
> tested this here at Red Hat on some System Z machines. Without the
> modification made here in v2, the systems failed to boot ~10% of the time.
>
On Sat, Apr 27, 2019 at 11:49:25PM +0200, Greg KH wrote:
> How about this patch, I think it fixes up everything you need to do
> here, right?
Almost, see the two patches as a reply to this message. I've taken
Pan's original patch because it is correct and I doubt you're dying for
attribution :-)
On Tue, 23 Apr 2019, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Add the core mfd driver for max77650 PMIC. We define five sub-devices
> for which the drivers will be added in subsequent patches.
>
> Signed-off-by: Bartosz Golaszewski
> ---
> drivers/mfd/Kconfig | 14
>From 28e7f23939208bea639d6cd3d492cde3f65a7e4f Mon Sep 17 00:00:00 2001
From: Pan Bian
Date: Thu, 18 Apr 2019 10:27:18 +0800
In edac_create_csrow_object(), the reference to the object is not
released when adding the device to the device hierarchy fails
(device_add()). This may result in a memory
On Tue, 7 May 2019 13:18:06 -0400
Sasha Levin wrote:
> On Tue, May 07, 2019 at 10:15:19AM -0700, Linus Torvalds wrote:
> >On Tue, May 7, 2019 at 10:02 AM Sasha Levin wrote:
> >>
> >> I got it wrong then. I'll fix it up and get efad4e475c31 in instead.
> >
> >Careful. That one had a bug too, and
--
From: Greg KH
Do put_device() if device_add() fails.
[ bp: do device_del() for the successfully created devices in
edac_create_csrow_objects(), on the unwind path. ]
Signed-off-by: Greg KH
Signed-off-by: Borislav Petkov
Link: https://lkml.kernel.org/r/20190427214925.ge16...@kroah.com
-
On Wed, 01 May 2019, Charles Keepax wrote:
> Lochnagar is an evaluation and development board for Cirrus
> Logic Smart CODEC and Amp devices. It allows the connection of
> most Cirrus Logic devices on mini-cards, as well as allowing
> connection of various application processor systems to provide
..
> > rdrand (calling every 8 syscalls): Simple syscall: 0.0795 microseconds
>
> You could try something like:
> u64 rand_val = cpu_var->syscall_rand
>
> while (unlikely(rand_val == 0))
> rand_val = rdrand64();
>
> stack_offset = rand_val & 0xff;
> rand_val
>
> On 4/25/19 10:00 PM, Pankaj Gupta wrote:
>
> > +void host_ack(struct virtqueue *vq)
> > +{
> > + unsigned int len;
> > + unsigned long flags;
> > + struct virtio_pmem_request *req, *req_buf;
> > + struct virtio_pmem *vpmem = vq->vdev->priv;
> > +
> > + spin_lock_irqsave(&vpmem->pm
On Tue, 30 Apr 2019, Jonathan Neuschäfer wrote:
> "debugfs" was misspelled.
>
> Signed-off-by: Jonathan Neuschäfer
> ---
> drivers/mfd/ab8500-debugfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open
Enjoy!
The following changes since commit e93c9c99a629c61837d5a7fc2120cd2b6c70dbdd:
Linux 5.1 (2019-05-05 17:42:58 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git
ib-mfd-gpio-input-leds-power-v5.2
for you to fetch changes up to 796f
Commit-ID: 0e72499c3cc0cead32f88b94a02204d2b80768bf
Gitweb: https://git.kernel.org/tip/0e72499c3cc0cead32f88b94a02204d2b80768bf
Author: Andi Kleen
AuthorDate: Fri, 29 Mar 2019 17:47:41 -0700
Committer: Ingo Molnar
CommitDate: Wed, 8 May 2019 13:13:58 +0200
x86/kprobes: Make trampoline_
The comment is no longer valid, since it supports arrays with gaps now.
Signed-off-by: Alexandru Ardelean
---
Changelog v2 -> v3:
* after fixing __sysfs_match_string() this comment is no longer valid
drivers/scsi/sd.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/scsi/sd.c b/dri
Hi Dan,
Thank you for the review. Please see my reply inline.
>
> Hi Pankaj,
>
> Some minor file placement comments below.
Sure.
>
> On Thu, Apr 25, 2019 at 10:02 PM Pankaj Gupta wrote:
> >
> > This patch adds virtio-pmem driver for KVM guest.
> >
> > Guest reads the persistent memory ran
Commit-ID: 81d30225bc0c246b53270eb90b23cfbb941a186d
Gitweb: https://git.kernel.org/tip/81d30225bc0c246b53270eb90b23cfbb941a186d
Author: Jia Zhang
AuthorDate: Mon, 1 Apr 2019 19:40:45 +0800
Committer: Ingo Molnar
CommitDate: Wed, 8 May 2019 13:13:57 +0200
x86/vdso: Remove hpet_page from
From: Eric Biggers
Date: Thu, May 2, 2019 at 4:34 AM
To: syzbot, Dmitry Vyukov,
Cc: , ,
, , ,
, ,
, , ,
, , ,
,
> On Wed, May 01, 2019 at 07:36:05AM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:baf76f0c slip: make slhc_free() silently acce
On Wed, Apr 17, 2019 at 11:52:00AM +0200, Hans de Goede wrote:
> Hi,
>
> On 12-04-19 15:41, Heikki Krogerus wrote:
> > In ACPI, and now also in DT, the USB connectors usually have
> > their own device nodes. In case of USB Type-C, those
> > connector (port) nodes are child nodes of the controller
On Wed, Apr 17, 2019 at 06:03:03PM +0200, Hans de Goede wrote:
> Hi,
>
> On 17-04-19 12:44, Heikki Krogerus wrote:
> > On Wed, Apr 17, 2019 at 12:15:18PM +0200, Hans de Goede wrote:
> > > Hi,
> > >
> > > On 17-04-19 11:32, Heikki Krogerus wrote:
> > > > On Wed, Apr 17, 2019 at 11:19:28AM +0200, H
The `rdmacg_resource_names` array is a static array of strings.
Using match_string() (which computes the array size via ARRAY_SIZE())
is possible.
The change is mostly cosmetic.
No functionality change.
Signed-off-by: Alexandru Ardelean
---
kernel/cgroup/rdma.c | 2 +-
1 file changed, 1 inserti
The intent of this patch series is to make a case for fixing the
match_string() string helper.
The doc-string of the `__sysfs_match_string()` helper mentions that `n`
(the size of the given array) should be:
* @n: number of strings in the array or -1 for NULL terminated arrays
However, this is n
On Thu, 02 May 2019, Matti Vaittinen wrote:
> ROHM BD70528MWV is an ultra-low quiescent current general
> purpose single-chip power management IC for battery-powered
> portable devices.
>
> Add MFD core which enables chip access for following subdevices:
> - regulators/LED drivers
> -
The change is purely cosmetic at this point in time, but it does highlight
the change done in lib/string.c for match_string().
Particularly for this change, a control mode can be removed/added at a
different index/enum-value, and the match_string() helper will continue
until the end of the array a
From: Steven Rostedt
Date: Thu, May 2, 2019 at 5:10 AM
To: Eric Biggers
Cc: syzbot, Dmitry Vyukov, ,
, ,
, , ,
, ,
, , ,
, ,
,
> On Wed, 1 May 2019 19:34:27 -0700
> Eric Biggers wrote:
>
> > > Call Trace:
> > > smp_call_function_many+0x750/0x8c0 kernel/smp.c:434
> > > smp_call_function+0x42/0
On Thu, 02 May 2019, Matti Vaittinen wrote:
> Document bindings for regulators (3 bucks, 3 LDOs and 2 LED
> drivers) and 4 GPIO pins which can be configured for I/O or
> as interrupt sources withe configurable trigger levels.
>
> Signed-off-by: Matti Vaittinen
> Reviewed-by: Rob Herring
> Acked
The change is also cosmetic, but it also does a tighter coupling between
the enums & the string values. This way, the ARRAY_SIZE(phy_types) that is
implicitly done in the match_string() macro is also a bit safer.
Signed-off-by: Alexandru Ardelean
---
drivers/mmc/host/sdhci-xenon-phy.c | 12 +
On Tue, 30 Apr 2019, Andy Shevchenko wrote:
> Intel Comet Lake has the same LPSS than Intel Cannon Lake.
> Add the new IDs to the list of supported devices.
>
> Signed-off-by: Andy Shevchenko
> ---
> - update i2c info
> drivers/mfd/intel-lpss-pci.c | 13 +
> 1 file changed, 13 inser
> On 5/6/19 7:06 AM, Zhiqiang Liu wrote:
>> From: Kai Shen
>>
>> spinlock recursion happened when do LTP test:
>> #!/bin/bash
>> ./runltp -p -f hugetlb &
>> ./runltp -p -f hugetlb &
>> ./runltp -p -f hugetlb &
>> ./runltp -p -f hugetlb &
>> ./runltp -p -f hugetlb &
>>
>> The dtor returned by get_c
The change is mostly cosmetic.
The `armada_37xx_pin_group` struct is defined as.
struct armada_37xx_pin_group {
const char *name;
unsigned intstart_pin;
unsigned intnpins;
u32 reg_mask;
u32 val[NB_FUNCS];
unsigned
The `lcd_types` array is a static array of strings.
Using match_string() (which computes the array size via ARRAY_SIZE())
is possible.
This reduces the array by 1 element, since the NULL (at the end of the
array) is no longer needed.
Signed-off-by: Alexandru Ardelean
---
drivers/video/fbdev/pxa
This change re-introduces `match_string()` as a macro that uses
ARRAY_SIZE() to compute the size of the array.
The macro is added in all the places that do
`match_string(_a, ARRAY_SIZE(_a), s)`, since the change is pretty
straightforward.
Signed-off-by: Alexandru Ardelean
---
drivers/clk/bcm/clk
This change is a bit more than cosmetic.
It replaces 2 values in mtrr_strings with NULL. Previously, they were
defined as "?", which is not great because you could technically pass "?",
and you would get value 2.
It's not sure whether that was intended (likely it wasn't), but this fixes
that.
Sig
* Reshetova, Elena wrote:
> CONFIG_PAGE_TABLE_ISOLATION=n:
>
> base: Simple syscall: 0.0510 microseconds
> get_random_bytes(4096 bytes buffer): Simple syscall: 0.0597 microseconds
>
> So, pure speed wise get_random_bytes() with 1 page per-cpu buffer wins.
On Mon, 2019-05-06 at 17:46 +0300, andriy.shevche...@linux.intel.com wrote:
> [External]
>
>
> On Mon, May 06, 2019 at 04:45:43PM +0300, Alexandru Ardelean wrote:
> > On Fri, Apr 26, 2019 at 5:27 PM andriy.shevche...@linux.intel.com
> > wrote:
> > >
> > > On Fri, Apr 26, 2019 at 12:29:11PM +030
> -Original Message-
> From: Sascha Hauer
> Sent: 2019年5月6日 15:38
> To: Chuanhua Han
> Cc: shawn...@kernel.org; Leo Li ; robh...@kernel.org;
> mark.rutl...@arm.com; linux-kernel@vger.kernel.org;
> linux-...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> devicet...@vger.kernel.
On Mon, 06 May 2019, Dan Murphy wrote:
> Fix the lm3632 dt binding examples as the LCM enable GPIOs
> are defined as enable GPIOs per the regulator/lm363x-regulator.txt
> bindings document.
>
> Reviewed-by: Rob Herring
> Signed-off-by: Dan Murphy
For my own reference:
Acked-for-MFD-by: Lee J
On Tue, May 07, 2019 at 04:09:15PM -0700, Florian Fainelli wrote:
> Hi Sudeep, Guenter,
>
> This patch series adds support for scaling SCMI sensor values read from
> firmware. Sudeep, let me know if you think we should be treating scale
> == 0 as a special value to preserve some firmware compatibi
On Mon, 06 May 2019, Dan Murphy wrote:
> Document the ramp-up and ramp-down property in the binding.
> Removing the "sec" from the property definition as seconds is
> implied.
>
> Reviewed-by: Rob Herring
> Signed-off-by: Dan Murphy
For my own reference:
Acked-for-MFD-by: Lee Jones
--
Lee
101 - 200 of 799 matches
Mail list logo
