On Mon, Jun 18, 2018 at 12:31 PM, Jason Gunthorpe wrote:
> On Mon, Jun 18, 2018 at 12:21:46PM -0700, Dan Williams wrote:
>> On Mon, Jun 18, 2018 at 11:14 AM, John Hubbard wrote:
>> > On 06/18/2018 10:56 AM, Dan Williams wrote:
>> >> On Mon, Jun 18, 2018 at 10:50 AM, John Hubbard
>> >> wrote:
On Sat, Jun 16, 2018 at 3:05 PM Ben Hutchings wrote:
>
> The help text for GOOGLE_FIRMWARE states that it should only be
> enabled when building a kernel for Google's own servers. However, it
> is now also a dependency for various Chromebook firmware drivers.
>
> Update the help text to reflect
On Mon, 18 Jun 2018 21:56:20 +0200
Robert Jarzmik wrote:
> Boris Brezillon writes:
>
> > Hi Robert,
> >
> > On Sun, 17 Jun 2018 19:02:03 +0200
> > Robert Jarzmik wrote:
> >
> >> As I gathered almost all the required acks, this is an information only
> >> post
> >> before queuing to the PXA
On Mon, Jun 18, 2018 at 08:48:32AM -0600, Rob Herring wrote:
> On Mon, Jun 18, 2018 at 6:39 AM, Niklas Cassel
> wrote:
> > On Mon, Jun 18, 2018 at 12:06:42PM +0100, Mark Brown wrote:
> >> On Thu, Jun 14, 2018 at 01:11:36PM +0200, Niklas Cassel wrote:
> >> > of_platform_device_destroy is only
On Mon, Jun 18 2018 at 13:54 -0600, Doug Anderson wrote:
Hi,
On Mon, Jun 18, 2018 at 12:06 PM, Lina Iyer wrote:
On Mon, Jun 18 2018 at 12:33 -0600, Doug Anderson wrote:
Lina,
On Mon, Jun 18, 2018 at 9:39 AM, Lina Iyer wrote:
+/**
* struct rsc_drv: the Direct Resource Voter (DRV) of the
Hi,
On Thu, Jun 14, 2018 at 12:47:02PM -0700, Matthias Kaehlcke wrote:
> Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding the
> devfreq device") initializes df->min/max_freq with the min/max OPP when
> the device is added. Later commit f1d981eaecf8 ("PM / devfreq: Use the
>
Hi George,
On 6/15/2018 4:03 AM, George Cherian wrote:
> Per Section 8.4.7.1.3 of ACPI 6.2, The platform provides performance
> feedback via set of performance counters. To determine the actual
> performance level delivered over time, OSPM may read a set of
> performance counters from the
Eric W. Biederman wrote:
> I have read through these patches and I noticed a significant issue.
>
> Today in mount_bdev we do something that looks like:
>
> mount_bdev(...)
> {
> s = sget(..., bdev);
> if (s->s_root) {
> /* Noop */
> } else {
>
Hi Boris,
Thus wrote Boris Brezillon (boris.brezil...@bootlin.com):
> > Signed-off-by: Martin Kaiser
> > Reviewed-by: Sascha Hauer
> > Cc: sta...@vger.kernel.org
> Hm, a Cc-stable tag without its associated Fixes tag, I don't like that.
> Can you find which commit introduced this bug?
the
There's no reason why we shouldn't pack/unpack bits into/from
u8 values/registers/etc., so add u8 helpers.
Use the MAKE_OP() macro directly to avoid having nonsense
le8_encode_bits() and similar functions.
Signed-off-by: Johannes Berg
---
include/linux/bitfield.h | 1 +
1 file changed, 1
The v21 version of the NAND flash controller contains a Spare Area Size
Register (SPAS) at offset 0x10. Its setting defaults to the maximum
spare area size of 218 bytes. The size that is set in this register is
used by the controller when it calculates the ECC bytes internally in
hardware.
Hey Steve,
On 06/18/2018 12:18 PM, Steve French wrote:
Gustavo,
Thx for pointing this out. Let me know if this patch addresses what
you found. Code is experimental mount option but extremely important
to get right due to move away from SMB1/CIFS which had posix
extensions.
Yep. It seems
Signed-off-by: Ryan Grachek
---
arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts | 1 -
arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 8
2 files changed, 9 deletions(-)
diff --git a/arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts
On Mon, Jun 18, 2018 at 11:14 AM, John Hubbard wrote:
> On 06/18/2018 10:56 AM, Dan Williams wrote:
>> On Mon, Jun 18, 2018 at 10:50 AM, John Hubbard wrote:
>>> On 06/18/2018 01:12 AM, Christoph Hellwig wrote:
On Sun, Jun 17, 2018 at 01:28:18PM -0700, John Hubbard wrote:
> Yes. However,
On Mon, Jun 18, 2018 at 05:38:06PM +0100, Will Deacon wrote:
> On Mon, Jun 18, 2018 at 11:19:01AM +0100, Mark Rutland wrote:
> > This series contains a few cleanups of the atomic API, fixing
> > inconsistencies between atomic_* and atomic64_*, and minimizing
> > repetition in arch code. This is
>
> On Fri, Jun 08, 2018 at 12:20:40AM +0300, Tomas Winkler wrote:
> > We cannot use go_idle cmd_ready commands via runtime_pm handles as
> > with the introduction of localities this is no longer an optional
> > feature, while runtime pm can be not enabled.
> > Though cmd_ready/go_idle provides a
Yogesh,
On Wed, 30 May 2018 15:14:32 +0200
Frieder Schrempf wrote:
> +static void fsl_qspi_select_mem(struct fsl_qspi *q, struct spi_device *spi)
> +{
> + unsigned long rate = spi->max_speed_hz;
> + int ret, i;
> + u32 map_addr;
> +
> + if (q->selected == spi->chip_select)
> +
On Mon, Jun 18, 2018 at 12:21:46PM -0700, Dan Williams wrote:
> On Mon, Jun 18, 2018 at 11:14 AM, John Hubbard wrote:
> > On 06/18/2018 10:56 AM, Dan Williams wrote:
> >> On Mon, Jun 18, 2018 at 10:50 AM, John Hubbard wrote:
> >>> On 06/18/2018 01:12 AM, Christoph Hellwig wrote:
> On Sun,
On Mon, Jun 18, 2018 at 09:07:12PM +0300, Jarkko Sakkinen wrote:
> On Fri, Jun 08, 2018 at 02:54:38PM +0800, Louis Collard wrote:
> > It is now possible for drivers to easily specify a hwrng quality, however
> > most do not currently do this, and in cases where they do, it may be
> > desirable to
When scaling max/min settings are changed, internally they are converted
to a ratio using the max turbo 1 core turbo frequency. This works fine
when 1 core max is same irrespective of the core. But under Turbo 3.0,
this will not be the case. For example:
Core 0: max turbo pstate: 43 (4.3GHz)
Core
Hi,
On Mon, Jun 18, 2018 at 12:06 PM, Lina Iyer wrote:
> On Mon, Jun 18 2018 at 12:33 -0600, Doug Anderson wrote:
>>
>> Lina,
>>
>> On Mon, Jun 18, 2018 at 9:39 AM, Lina Iyer wrote:
+/**
* struct rsc_drv: the Direct Resource Voter (DRV) of the
* Resource State Coordinator
On Mon, Jun 04, 2018 at 08:16:51AM +, Zhenzhong Duan wrote:
> Intel spec says: 'The processor flags in the 48-byte header and the
> processor flags field associated with the extended processor signature
> structures may have multiple bits set.'
>
> Make sure processor flags of the new
Boris Brezillon writes:
> Hi Robert,
>
> On Sun, 17 Jun 2018 19:02:03 +0200
> Robert Jarzmik wrote:
>
>> As I gathered almost all the required acks, this is an information only post
>> before queuing to the PXA tree.
>
> We'll need an immutable branch/tag containing those changes, just in
>
On Fri, Jun 08, 2018 at 02:54:38PM +0800, Louis Collard wrote:
> It is now possible for drivers to easily specify a hwrng quality, however
> most do not currently do this, and in cases where they do, it may be
> desirable to override the driver-specified value with a user-specified
> one. This
On 18.06.2018 18:44, Borislav Petkov wrote:
> On Tue, Jun 12, 2018 at 11:08:31PM +0200, Maciej S. Szmigiero wrote:
>> That was the solution before this patch series version (6) - there was
>> a variable holding the CPU equivalence table size for the late loader,
>> but you didn't like it:> Instead
Lina,
On Mon, Jun 18, 2018 at 9:39 AM, Lina Iyer wrote:
>> +/**
>> * struct rsc_drv: the Direct Resource Voter (DRV) of the
>> * Resource State Coordinator controller (RSC)
>> *
>> @@ -52,6 +78,7 @@ struct tcs_group {
>> * @tcs:TCS groups
>> * @tcs_in_use: s/w state of the TCS
>> *
On Fri, Jun 15, 2018 at 12:08 PM, Jason Gunthorpe wrote:
>
> The point is, I don't care about the imbalance report.
OK, we are not on the same page.
Sorry for wasting my time.
Xunlei Pang writes:
> The current condition to judge clock drift in expire_cfs_rq_runtime()
> is wrong, the two runtime_expires are actually the same when clock
> drift happens, so this condtion can never hit. The orginal design was
> correctly done by commit a9cf55b28610 ("sched: Expire invalid
Boris,
On 6/18/2018 1:23 PM, Borislav Petkov wrote:
On Mon, Jun 18, 2018 at 01:14:11PM -0500, Suthikulpanit, Suravee wrote:
This enumeration is only for the family17h model 00-1Fh of hardware
revision. The patch is intended for the future revision of hardware.
I realized that but the same
On Tue, 2018-06-05 at 19:01 +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Wolfram Sang
>
> commit 2c78cdc1c06308a59d6ed4145cdba73fdeff8c0d upstream.
>
> We don't need to init HW before every
On Mon, Jun 18 2018 at 12:33 -0600, Doug Anderson wrote:
Lina,
On Mon, Jun 18, 2018 at 9:39 AM, Lina Iyer wrote:
+/**
* struct rsc_drv: the Direct Resource Voter (DRV) of the
* Resource State Coordinator controller (RSC)
*
@@ -52,6 +78,7 @@ struct tcs_group {
* @tcs:TCS groups
*
On 06/12/2018 12:56 PM, Peter Zijlstra wrote:
>
>> Ultimately, my solution was to restore the previous behavior by reading and
>> storing the firmware setting of the bit rather than to always clear it.
>
> Ah, urgh.. what a mess. So the OS setting the bit to a known and
> consistent value is
> So we're talking about a workaround for broken software. The question
> is how wide spread is it?
For rr to work, it tries to replicate the process state *exactly*. That means:
1. The same instructions executed in the same order
2. The exact same register state at those instructions
3. The
On Fri, Jun 08, 2018 at 03:11:46PM +0800, Louis Collard wrote:
> Adds plumbing required for drivers based on tpm_tis to set hwrng quality.
>
> Signed-off-by: Louis Collard
NAK because this not connected to the current GIT tree (should probably
make a patch set?).
/Jarkko
Certain properties should be moved to the board file to reflect
the specific properties of the board, and not the SoC. Move these
properties to proper location and organize properties in both files.
Signed-off-by: Ryan Grachek
---
arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts | 27
On 06/18/2018 10:56 AM, Dan Williams wrote:
> On Mon, Jun 18, 2018 at 10:50 AM, John Hubbard wrote:
>> On 06/18/2018 01:12 AM, Christoph Hellwig wrote:
>>> On Sun, Jun 17, 2018 at 01:28:18PM -0700, John Hubbard wrote:
Yes. However, my thinking was: get_user_pages() can become a way to
Boris,
On 6/18/2018 12:20 PM, Borislav Petkov wrote:
On Wed, Jun 13, 2018 at 01:43:10PM -0500, Suravee Suthikulpanit wrote:
The current logic incorrectly calculates the LLC ID from the APIC ID.
Unless specified otherwise, the LLC ID should be calculated from
the count order of the number of
> So, to be useful, this interface needs to be called before an
> application can run XGETBV or XSAVE for the first time and caches a
> "bad" value. I think that means that it might not be feasible to use
> outside of cases where you ptrace() something and inject things before
> it has a chance
* H. Nikolaus Schaller [180618 16:46]:
>
> I can also demonstrate that the duplication has gone:
OK good to hear.
> And I was no longer able to reproduce the strcmp(NULL) issue. So it is either
> better hidden
> or gone.
It should not be possible with checks preventing registering
a group
On Mon, Jun 18, 2018 at 10:11:36AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.51 release.
> There are 189 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
On Mon, Jun 18, 2018 at 08:11:53PM +0200, Maciej S. Szmigiero wrote:
> The equivalence table size can be computed in the late loader - there is
> no problem there.
>
> However, this computed size needs to be passed somehow to functions
> scanning the equivalence table.
Ok, then let's make a
Fine by me.
On 6/18/18, 1:13 AM, "Greg Kroah-Hartman" wrote:
>4.14-stable review patch. If anyone has any objections, please let me know.
>
>--
>
>From: Jim Gill
>
>[ Upstream commit f4b024271ae3e9786e5d6f1c05b01b57a74e1d6d ]
>
>The vmw_pvscsi driver returns DID_ABORT for
Children of RPMh will need access to cmd_db. Rather than having each
child have code to check if cmd_db is ready let's add the check to
RPMh.
With this we'll be able to remove this boilerplate code from
clk-rpmh.c and qcom-rpmh-regulator.c. Neither of these files has
landed upstream yet but
mbers")
---
Problem located with an experimental coccinelle script
Patch was compile-tested with: x86_64_defconfig + STAGING=y, STAGING_BOARD=y
Patch is against 4.18-rc1 (localversion-next is next-20180618)
drivers/staging/board/board.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drive
On Mon, Jun 18, 2018 at 01:46:11PM -0500, Suthikulpanit, Suravee wrote:
> Your understanding is correct. I was not sure about what you were referring
> to earlier. Basically, the number of threads sharing cache is used to
> calculate the amount of right-shifting of APIC ID, which results in
Xunlei Pang writes:
> I noticed the group frequently got throttled even it consumed
> low cpu usage, this caused some jitters on the response time
> to some of our business containers enabling cpu quota.
>
> It's very easy to reproduce:
> mkdir /sys/fs/cgroup/cpu/test
> cd
On 18 June 2018 at 19:57, Joe Perches wrote:
> On Mon, 2018-06-18 at 19:42 +0200, Krzysztof Kozlowski wrote:
>> Remove leading 0x from recently introduced unit addresses to fix DTC
>> warnings:
>>
>> Warning (unit_address_format): /soc/sysmmu@0x1504: unit name should
>> not have leading
Hi Yogesh,
On Mon, 18 Jun 2018 13:32:27 +
Yogesh Narayan Gaur wrote:
> -Original Message-
> From: Boris Brezillon [mailto:boris.brezil...@bootlin.com]
> Sent: Friday, June 15, 2018 7:26 PM
> To: Yogesh Narayan Gaur ; Fabio Estevam
> ; David Wolfe ;
> dw...@infradead.org
> Cc:
On 06/18/2018 01:12 AM, Christoph Hellwig wrote:
> On Sun, Jun 17, 2018 at 01:28:18PM -0700, John Hubbard wrote:
>> Yes. However, my thinking was: get_user_pages() can become a way to indicate
>> that
>> these pages are going to be treated specially. In particular, the caller
>> does not really
On Mon, Jun 18, 2018 at 10:50 AM, John Hubbard wrote:
> On 06/18/2018 01:12 AM, Christoph Hellwig wrote:
>> On Sun, Jun 17, 2018 at 01:28:18PM -0700, John Hubbard wrote:
>>> Yes. However, my thinking was: get_user_pages() can become a way to
>>> indicate that
>>> these pages are going to be
On Mon, 2018-06-18 at 19:42 +0200, Krzysztof Kozlowski wrote:
> Remove leading 0x from recently introduced unit addresses to fix DTC
> warnings:
>
> Warning (unit_address_format): /soc/sysmmu@0x1504: unit name should
> not have leading "0x"
[]
> diff --git
On Fri, Jun 08, 2018 at 12:20:40AM +0300, Tomas Winkler wrote:
> We cannot use go_idle cmd_ready commands via runtime_pm handles
> as with the introduction of localities this is no longer an optional
> feature, while runtime pm can be not enabled.
> Though cmd_ready/go_idle provides a power
On Fri, Jun 08, 2018 at 06:26:33PM +0800, John Garry wrote:
> Currently smatch warns of possible Spectre-V1 issue in ahci_led_store():
> drivers/ata/libahci.c:1150 ahci_led_store() warn: potential spectre issue
> 'pp->em_priv' (local cap)
>
> Userspace controls @pmp from following callchain:
>
On Mon, Jun 18, 2018 at 01:14:11PM -0500, Suthikulpanit, Suravee wrote:
> This enumeration is only for the family17h model 00-1Fh of hardware
> revision. The patch is intended for the future revision of hardware.
I realized that but the same holds true for the future revision - there
you need to
Hi Tony,
> Am 18.06.2018 um 20:17 schrieb Tony Lindgren :
>
> * H. Nikolaus Schaller [180618 16:46]:
>
>>
>> I can also demonstrate that the duplication has gone:
>
> OK good to hear.
>
>> And I was no longer able to reproduce the strcmp(NULL) issue. So it is
>> either better hidden
>> or
On Mon, Jun 18, 2018 at 10:09:45AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.16.17 release.
> There are 279 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
On Mon, Jun 18, 2018 at 07:42:16PM +0200, Krzysztof Kozlowski wrote:
> The decon, decon_tv and dsi nodes have only one child port so
> address/size mappings are not necessary. This fixes DTC warnings like:
>
> Warning (graph_child_address): /soc/decon@1380/ports:
> graph node has
Hi Huacai,
On Fri, Jun 15, 2018 at 02:07:38PM +0800, Huacai Chen wrote:
> After commit 7f56b58a92aaf2c ("locking/mcs: Use smp_cond_load_acquire()
> in MCS spin loop") Loongson-3 fails to boot. This is because Loongson-3
> has SFB (Store Fill Buffer) and READ_ONCE() may get an old value in a
>
We rely on devices to use pinmuxing configurations in DT to select the
GPIO function (function 0) if they're going to use the gpio in GPIO
mode. Let's simplify things for driver authors by implementing
gpio_request_enable() for this pinctrl driver to mux out the GPIO
function when the gpio is use
On Mon, Jun 18, 2018 at 2:08 PM, Niklas Cassel wrote:
> On Mon, Jun 18, 2018 at 08:48:32AM -0600, Rob Herring wrote:
>> On Mon, Jun 18, 2018 at 6:39 AM, Niklas Cassel
>> wrote:
>> > On Mon, Jun 18, 2018 at 12:06:42PM +0100, Mark Brown wrote:
>> >> On Thu, Jun 14, 2018 at 01:11:36PM +0200,
When requesting a gpio as an interrupt, we should make sure to mux the
pin as the GPIO function and configure it to be an input so that various
functions or output signals don't affect the interrupt state of the pin.
So far, we've relied on pinmux configurations in DT to handle this, but
let's
Here's a collection of pinctrl fixes for the qcom driver that
make things a little smoother for DT writers while also fixing
a problem seen with level triggered interrupts.
The first patch fixes an issue where we always see one extra level
triggered interrupt when the interrupt triggers. The
The interrupt controller hardware in this pin controller has two status
enable bits. The first "normal" status enable bit enables or disables
the summary interrupt line being raised when a gpio interrupt triggers
and the "raw" status enable bit allows or prevents the hardware from
latching an
This adds the rpmh-clk node to sdm845 based on the examples in the
bindings.
Signed-off-by: Douglas Anderson
---
NOTE: to apply this patch cleanly, apply it atop:
arm64: dts: qcom: sdm845: Add I2C, SPI, and UART9 nodes
https://patchwork.kernel.org/patch/10462691/
This adds the rpmh-rsc node to sdm845 based on the examples in the
bindings.
Signed-off-by: Douglas Anderson
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 19 +++
1 file changed, 19 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
On Wed, Apr 11, 2018 at 6:48 AM, Faiz Abbas wrote:
> am335x-evm, am335x-evmsk and am335x-beaglebone are currently relying on
> pinmux set by the bootloader to set the correct value for mmc1. Fix
> this by adding pinmux data for the same in kernel.
>
> Signed-off-by: Faiz Abbas
> ---
>
From: Ilia Lin
Change to the @kernel.org address
Signed-off-by: Ilia Lin
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 035973b23b8b..15a836eebe9a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -11799,7 +11799,7 @@ F:
On Mon, Jun 18 2018 at 14:56 -0600, Douglas Anderson wrote:
This adds the rpmh-rsc node to sdm845 based on the examples in the
bindings.
Signed-off-by: Douglas Anderson
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 19 +++
1 file changed, 19 insertions(+)
diff --git
On Mon, Jun 18, 2018 at 8:11 AM Jethro Beekman wrote:
>
> On 2018-06-08 10:09, Jarkko Sakkinen wrote:
> > +/*
> > + * Writing the LE hash MSRs is extraordinarily expensive, e.g.
> > + * 3-4x slower than normal MSRs, so we use a per-cpu cache to
> > + * track the last known value of the MSRs to
On Mon, 18 Jun 2018 11:18:07 +0200 Vlastimil Babka wrote:
> The vmstat NR_KERNEL_MISC_RECLAIMABLE counter is for kernel non-slab
> allocations that can be reclaimed via shrinker. In /proc/meminfo, we can show
> the sum of all reclaimable kernel allocations (including slab) as
> "KReclaimable".
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Tobias Regnery
[ Upstream commit 2f860691c2d2e3af1404ffeb2d22dd5c3dbca811 ]
There is the following build error with CONFIG_TYPEC_UCSI=m, CONFIG_FTRACE=y
and CONFIG_TRACING=n:
ERROR:
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jiang Biao
[ Upstream commit 946b81da114b8ba5c74bb01e57c0c6eca2bdc801 ]
As described in the comment of blkcg_activate_policy(),
*Update of each blkg is protected by both queue and blkcg locks
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Tung Nguyen
[ Upstream commit 36a50a989ee8267588de520b8704b85f045a3220 ]
When configuring the number of used bearers to MAX_BEARER and issuing
command "tipc link monitor summary", the command
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Tyler Hicks
[ Upstream commit e86281e700cca8a773f9a572fa406adf2784ba5c ]
Both ecryptfs_filldir() and ecryptfs_readlink_lower() use
ecryptfs_decode_and_decrypt_filename() to translate lower
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Liam Girdwood
[ Upstream commit 05bdcf12905533b8628627b6634608cd3b57c607 ]
Validate the topology input before we dereference the pointer.
Signed-off-by: Liam Girdwood
Signed-off-by: Mark
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
[ Upstream commit 59275a0c037ed6fabd6354730f1e3104264ab719 ]
We transiently switch to KERNEL_DS in compat_ptrace_gethbpregs() and
compat_ptrace_sethbpregs(), but in either case
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
[ Upstream commit 2c2bf522ed8cbfaac666f7dc65cfd38de2b89f0f ]
dtc recently (v1.4.4-8-g756ffc4f52f6) added PCI bus checks. Fix the
warnings now emitted:
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jacopo Mondi
[ Upstream commit 7de5b7e5f6a67c285b86d1478e8e150929c93482 ]
Add documentation for r8a77965 compatible string to Renesas sci-serial
device tree bindings documentation.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: "oder_ch...@realtek.com"
[ Upstream commit 5ef5ac8de125fe6b4b23293bee026ca7ea1529b9 ]
The patch adds the missing register in the readable table.
Signed-off-by: Oder Chiou
Signed-off-by:
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Christophe JAILLET
[ Upstream commit 839c42273617787318da7baf6151d553108f5e17 ]
When extending the rmi_spi buffers, we must check that no out of memory
error occurs, otherwise we may access
* Andy Shevchenko [180618 08:25]:
> On Sat, Jun 16, 2018 at 2:08 PM H. Nikolaus Schaller
> wrote:
> > But it looks as if we still have duplicate assignments by deferred probing,
> > i.e. some cleanup is
> > missing (or is this intended behaviour?).
>
> > But I think the fundamental problem is
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Matheus Castello
[ Upstream commit b614e905a0bc8fc5d4fa72665ac26ae00c874a4e ]
Bindings describe hardware, not drivers.
Use reference to hardware Allwinner A1X Pin Controller instead driver.
* Pavel Machek [180618 07:43]:
>
> So... there are mA, mAh values. Those come from hardware, and I
> believe we should keep them.
>
> But there are also mW, mWh values, which are synthetic. Userland can
> compute them from mV, mA values... and it is confusing that kernel
> provides them. (My
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Jack Morgenstein
[ Upstream commit b03bcde962606d2ee59a4e9dd470db9ad53c5418 ]
When the kernel was compiled using the UBSAN option,
we saw the following stack trace:
[ 1184.827917] UBSAN:
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Sebastian Sanchez
[ Upstream commit e9777ad4399c26c70318c4945f94efac2ed95391 ]
When allocating device data, if there's an allocation failure, the
already allocated memory won't be freed such
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Sebastian Sanchez
[ Upstream commit 59482a14918b282ca2a98f38c69da5ebeb1107d2 ]
When IRQ affinity is set and the interrupt type is unknown, a cpu
mask allocated within the function is never
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Rob Herring
[ Upstream commit bc519d9574618e47a0c788000fb78da95e18d953 ]
The BCM2835 AUX SPI has a shared interrupt line (with AUX UART).
Downstream fixes this with an AUX irqchip to demux
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Keith Busch
[ Upstream commit a785dbccd95c37606c720580714f5a7a8b3255f1 ]
When CONFIG_NVME_MULTIPATH is set, but we're not using nvme to multipath,
namespaces with multiple paths were not
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Janusz Krzysztofik
[ Upstream commit baf64250b4a513bf4ac226fd938692dc1836f4f6 ]
The deferred_fiq handler used to limit hardware operations to IRQ
unmask only, relying on gpio-omap assigned
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: oulijun
[ Upstream commit 137ae3208416278aabef3b71e0ea1052940ca362 ]
When generated bad work reqeust, it needs to
report to user. This patch mainly fixes it.
Signed-off-by: Lijun Ou
On Mon 2018-06-18 15:37:38, Sergey Senozhatsky wrote:
> On (06/08/18 12:48), Petr Mladek wrote:
> [..]
> > diff --git a/include/linux/printk.h b/include/linux/printk.h
> > index 6d7e800affd8..872fbdf8df26 100644
> > --- a/include/linux/printk.h
> > +++ b/include/linux/printk.h
> > @@ -148,9
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Sekhar Nori
[ Upstream commit d45622c0eaa5992a1a2248cbe93e1ff7a2da7be4 ]
commit c4dc56be7e26 ("ARM: davinci: fix the GPIO lookup for omapl138-hawk")
fixed the GPIO chip name for look-up of
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Baolin Wang
[ Upstream commit f76cdd00ef0e39d880139b074e3b247594dff95a ]
The read_persistent_clock() uses a timespec, which is not year 2038 safe
on 32bit systems. On parisc architecture, we
Hello Sai,
On 16 June 2018 at 03:09, Sai Praneeth Prakhya
wrote:
> From: Sai Praneeth
>
> efi_memmap_alloc(), as the name suggests, allocates memory for a new efi
> memory map. It's referenced from couple of places, namely,
> efi_arch_mem_reserve() and efi_free_boot_services(). These callers,
>
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Ramon Fried
[ Upstream commit 93dd4e73c0d9cc32f835d76a54257020b0bfc75a ]
Added "rpmsg:rpmsg_chrdev" MODULE_ALIAS to autoload
rpmg_chrdev module automatically.
Signed-off-by: Ramon Fried
On Sun, 17 Jun 2018 22:45:59 +0200
Stefan Agner wrote:
> Changes definitly calm down, most noteably probably the changes
> around checking whether a page is empty if the stack reports ECC
> errors.. I verified the code using raw nandwrites with OOB to
> simulate an empty page which has some bits
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Taehee Yoo
[ Upstream commit d71efb599ad42ef1e564c652d8084252bdc85edf ]
When chain name is changed, nft_chain_commit_update is called.
In the nft_chain_commit_update, trans->ctx.chain->name
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
[ Upstream commit 19791a7ca674fb3009bb068260e852a2f05b605c ]
It's possible for userspace to control idx. Sanitize idx when using it
as an array index.
Found by smatch.
1 - 100 of 2166 matches
Mail list logo
