On Mon 14-08-17 15:27:20, Ilia Mirkin wrote:
> On Mon, Aug 14, 2017 at 3:18 PM, Michal Hocko wrote:
[...]
> > nouveau :03:00.0: fifo: channel 6 [mpv/vo[3535]] kick timeout
> > nouveau: mpv/vo[3535]::906f: detach gr failed, -110
>
> Are you using mpv in conjunction with the GL vide
On Fri, 4 Aug 2017 15:35:06 -0400
Boris Ostrovsky wrote:
> On 08/04/2017 07:36 AM, Juergen Gross wrote:
> > There are some Xen specific trace functions defined in
> > include/trace/events/xen.h. Remove them.
> >
> > Signed-off-by: Juergen Gross
>
> (Again, adding Ingo and Steven)
Feel free t
On Fri, 4 Aug 2017 15:20:30 -0400
Boris Ostrovsky wrote:
> On 08/04/2017 07:36 AM, Juergen Gross wrote:
> > The function xen_set_domain_pte() is used nowhere in the kernel.
> > Remove it.
> >
> > Signed-off-by: Juergen Gross
>
> Reviewed-by: Boris Ostrovsky
>
> (+ Ingo and Steven who are ma
Em Mon, Aug 14, 2017 at 08:44:14PM +0200, Michael Petlan escreveu:
> Hi Arnaldo!
>
> Maybe this would be the right time to incorporate the shell-based
> perftool-testsuite [1] into perf-test, wouldn't it?
Perhaps its time, yes. Some questions:
Do these tests assume that perf was built in some pa
On Mon, Aug 14, 2017 at 11:42:45AM -0700, Laura Abbott wrote:
> On 08/14/2017 09:22 AM, Tycho Andersen wrote:
> > On Sat, Aug 12, 2017 at 12:17:34PM +0100, Mark Rutland wrote:
> >> Hi,
> >>
> >> On Fri, Aug 11, 2017 at 03:13:02PM -0600, Tycho Andersen wrote:
> >>> On Fri, Aug 11, 2017 at 10:25:14AM
Hi Mark,
First, thanks for taking a look!
On Sat, Aug 12, 2017 at 12:57:37PM +0100, Mark Rutland wrote:
> On Wed, Aug 09, 2017 at 02:07:52PM -0600, Tycho Andersen wrote:
> > From: Juerg Haefliger
> >
> > If the page is unmapped by XPFO, a data cache flush results in a fatal
> > page fault. So d
> -Original Message-
> From: linux-cifs-ow...@vger.kernel.org [mailto:linux-cifs-
> ow...@vger.kernel.org] On Behalf Of Long Li
> Sent: Wednesday, August 2, 2017 4:10 PM
> To: Steve French ; linux-c...@vger.kernel.org; samba-
> techni...@lists.samba.org; linux-kernel@vger.kernel.org
> Cc: L
Am Montag, 14. August 2017, 16:35:55 CEST schrieb Andy Yan:
> Add SPI device tree node for rv1108.
>
> Signed-off-by: Andy Yan
applied for 4.14
Thanks
Heiko
> -Original Message-
> From: linux-cifs-ow...@vger.kernel.org [mailto:linux-cifs-
> ow...@vger.kernel.org] On Behalf Of Long Li
> Sent: Wednesday, August 2, 2017 4:10 PM
> To: Steve French ; linux-c...@vger.kernel.org; samba-
> techni...@lists.samba.org; linux-kernel@vger.kernel.org
> Cc: L
Hi Pavel,
Thanks for the patch.
I understand Tony already applied this one. I'd have a few comments below,
could you address them in another patch, please?
On Thu, Aug 10, 2017 at 10:49:23PM +0200, Pavel Machek wrote:
>
> Add camera support to N900 dts. Also add a note about MMC & debugging.
>
On Mon, 2017-08-14 at 21:34 +0200, Borislav Petkov wrote:
> On Mon, Aug 14, 2017 at 07:02:15PM +, Kani, Toshimitsu wrote:
> > I do not know how likely we see such case, but the code should be
> > written according to the spec.
>
> Well, then you'll have to make ghes_edac_report_mem_error()
> r
On 08/14/2017 02:12 PM, John Stultz wrote:
> On Wed, Aug 9, 2017 at 3:05 PM, Shuah Khan wrote:
>> Fix compile error due to ksft_exit_skip() update to take var_args.
>>
>> freq-step.c: In function ‘init_test’:
>> freq-step.c:234:3: error: too few arguments to function ‘ksft_exit_skip’
>>ksft_ex
On Fri, Aug 11, 2017 at 04:26:16PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> Save the original array dimensions in xyarrays, so that users can retrieve
> them
> later. Add some inline functions to access these fields.
hi,
is there a branch with this?
also I recall sending feedback for so
On Mon, Aug 14, 2017 at 10:57:46AM -0700, Steve Longerbeam wrote:
> Hi Akturk, this has already been fixed, see
Sorry. Apparently, I missed to update my tree, somehow.
>
> 4560cb4a0c ("media: imx: add VIDEO_V4L2_SUBDEV_API dependency").
>
> Steve
>
> On 08/14/2017 04:00 AM, Cihangir Akturk wro
At least one BIOS enumerates the max17047 both through the INT33FE ACPI
device (it is right there in the resources table) as well as through a
separate MAX17047 device.
This commit checks for the max17047 already being enumerated through
a separate MAX17047 ACPI device and if so it uses the i2c-cl
This changes the earlier patch "nvmet: don't report 0-bytes
in serial number" to use the memcpy_and_pad() helper introduced
in a previous patch.
Signed-off-by: Martin Wilck
---
drivers/nvme/target/admin-cmd.c | 14 +++---
1 file changed, 3 insertions(+), 11 deletions(-)
diff --git a/dri
Hi Christoph,
I'm reposting the target-side of my patch rebased against 4.13-rc
as requested.
NOTE: an error has occurred while merging the previous version of my patch.
This is fixed by patch 1/3 in the series - that's an important fix for 4.13,
please push forward. 2/3 and 3/3 move the "copy_an
This helper function is useful for the nvme subsystem, and maybe
others.
Note: the warnings reported by the kbuild test robot for this patch
are actually generated by the use of CONFIG_PROFILE_ALL_BRANCHES
together with __FORTIFY_INLINE.
Signed-off-by: Martin Wilck
---
include/linux/string.h |
The merged version of my patch "nvmet: don't report 0-bytes in serial
number" fails to remove two lines which should have been replaced,
so that the space-padded strings are overwritten again with 0-bytes.
Fix it.
Fixes: 42de82a8b544 nvmet: don't report 0-bytes in serial number
Signed-off-by: Mart
On Wed, Aug 9, 2017 at 3:05 PM, Shuah Khan wrote:
> Fix compile error due to ksft_exit_skip() update to take var_args.
>
> freq-step.c: In function ‘init_test’:
> freq-step.c:234:3: error: too few arguments to function ‘ksft_exit_skip’
>ksft_exit_skip();
>^~
> In file included
From: Markus Elfring
Date: Mon, 14 Aug 2017 22:00:40 +0200
Add a jump target so that a bit of exception handling can be better reused
in these functions.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
sound/pci/rme9652/hdsp.c| 13 ++---
On Fri, Jul 28, 2017 at 01:45:58PM -0700, Brendan Higgins wrote:
> 24xx BMCs have larger clock divider granularity which can cause problems
> when trying to set them as 25xx clock dividers; this adds clock setting
> code specific to 24xx.
>
> This also fixes a potential issue where clock dividers
On Fri, Jul 28, 2017 at 06:00:12PM -0700, Brendan Higgins wrote:
> Before I skipped null checks when the master is in the STOP state; this
> fixes that.
>
> Signed-off-by: Brendan Higgins
Applied to for-current, thanks!
signature.asc
Description: PGP signature
> -Original Message-
> From: linux-cifs-ow...@vger.kernel.org [mailto:linux-cifs-
> ow...@vger.kernel.org] On Behalf Of Long Li
> Sent: Wednesday, August 2, 2017 4:10 PM
> To: Steve French ; linux-c...@vger.kernel.org; samba-
> techni...@lists.samba.org; linux-kernel@vger.kernel.org
> Cc: L
+linuxppc-dev
On Fri, Aug 11, 2017 at 11:29 AM, Robin Murphy wrote:
> Moving DMA configuration to happen later at driver probe time had the
> unnoticed side-effect that we now perform DMA configuration for *every*
> device represented in DT, rather than only those explicitly created by
> the of_p
On Mon, Aug 14, 2017 at 12:47:01PM -0700, Eric Anholt wrote:
> Cihangir Akturk writes:
>
> > Use drm_*_get() and drm_*_put() helpers instead of drm_*_reference()
> > and drm_*_unreference() helpers.
> >
> > drm_*_reference() and drm_*_unreference() functions are just
> > compatibility alias for d
Hi Daniel, Magnus,
On Thu, Aug 10, 2017 at 12:56 PM, Daniel Lezcano
wrote:
> On 10/08/2017 11:01, Geert Uytterhoeven wrote:
>> On Tue, Jul 11, 2017 at 1:56 PM, Simon Horman wrote:
>>> On Thu, Nov 24, 2016 at 11:58:43AM +0100, Simon Horman wrote:
On Mon, Mar 14, 2016 at 11:23:42PM +0900, Mag
All the locking related cmpxchg's in the following functions are
replaced with the _acquire variants:
- pv_queued_spin_steal_lock()
- trylock_clear_pending()
This change should help performance on architectures that use LL/SC.
The cmpxchg in pv_kick_node() is replaced with a relaxed version
wit
v4
- klp_shadow_attach(), klp_shadow_get_or_attach(), and
klp_shadow_update_or_attach()
- fix up return values depending on whether a new_shadow
variable was allocated, or an existing one was used
- kfree new_shadow, not shadow_data when shadow variable is found
under the lock (2nd s
Add exported API for livepatch modules:
klp_shadow_get()
klp_shadow_attach()
klp_shadow_get_or_attach()
klp_shadow_update_or_attach()
klp_shadow_detach()
klp_shadow_detach_all()
that implement "shadow" variables, which allow callers to associate new
shadow fields to existing data stru
Michael Ellerman [m...@ellerman.id.au] wrote:
> Sukadev Bhattiprolu writes:
>
> > We need the SPRN_TIDR to bet set for use with fast thread-wakeup
> > (core-to-core wakeup). Each thread in a process needs to have a
> > unique id within the process but as explained below, for now, we
> > assign g
The PMIC provides ACPI OpRegions which must be available for other
drivers' PS0 / PS3 methods early-on as such it must be builtin as the
Kconfig help text already states.
Somehow its Kconfig option ended up being a tristate though, this fixes
this.
Signed-off-by: Hans de Goede
---
Note, feel fre
Hi Lee,
This one seems to have fallen through the cracks, would be nice
to get this small fix into 4.14.
Thanks & Regards,
Hans
On Mon, Aug 14, 2017 at 05:38:39PM +0900, Minchan Kim wrote:
> memory-barrier.txt always scares me. I have read it for a while
> and IIUC, it seems semantic of spin_unlock(&same_pte) would be
> enough without some memory-barrier inside mm_tlb_flush_nested.
Indeed, see the email I just send. Its bo
> -Original Message-
> From: linux-cifs-ow...@vger.kernel.org [mailto:linux-cifs-
> ow...@vger.kernel.org] On Behalf Of Long Li
> Sent: Wednesday, August 2, 2017 4:10 PM
> To: Steve French ; linux-c...@vger.kernel.org; samba-
> techni...@lists.samba.org; linux-kernel@vger.kernel.org
> Cc: L
Cihangir Akturk writes:
> Use drm_*_get() and drm_*_put() helpers instead of drm_*_reference()
> and drm_*_unreference() helpers.
>
> drm_*_reference() and drm_*_unreference() functions are just
> compatibility alias for drm_*_get() and drm_*_put() and should not be
> used by new code. So convert
On Wed, Aug 09, 2017 at 12:12:56PM +0200, Javier Martinez Canillas wrote:
> The driver doesn't have a struct of_device_id table but supported devices
> are registered via Device Trees as shown in the following DT binding doc:
>
> Documentation/devicetree/bindings/i2c/i2c-designware.txt
Uhhh, that
On Mon, Aug 14, 2017 at 09:36:56AM +0800, Jun Gao wrote:
> On Sat, 2017-08-12 at 16:44 +0200, Wolfram Sang wrote:
> > > +static const struct i2c_adapter_quirks mt7622_i2c_quirks = {
> > > + .max_num_msgs = 255,
> > > + .max_write_len = 65535,
> > > + .max_read_len = 65535,
> > > + .max_comb_1st_msg
On 08/14/2017 02:21 AM, Thomas Gleixner wrote:
On Mon, 14 Aug 2017, Larry Finger wrote:
My Del Latitude D600 (single 32-bit CPU) shows the following locking message
when booted:
WARNING: possible recursive locking detected
4.12.0-rc2-00029-gfc8dffd
On Mon, Aug 14, 2017 at 05:07:19AM +, Nadav Amit wrote:
> >> So I'm not entirely clear about this yet.
> >>
> >> How about:
> >>
> >>
> >>CPU0CPU1
> >>
> >>tlb_gather_mmu()
> >>
> >>lock
On Thu, Aug 10, 2017 at 06:15:45PM +0300, Anton Vasilyev wrote:
> Use api pair of request_mem_region and release_mem_region
> instead of release_resource.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Anton Vasilyev
Applied to for-current, thanks!
sign
On Mon, Aug 14, 2017 at 07:02:15PM +, Kani, Toshimitsu wrote:
> I do not know how likely we see such case, but the code should be
> written according to the spec.
Well, then you'll have to make ghes_edac_report_mem_error() reentrant.
Which doesn't look that hard as the only thing it really nee
On Wed, Aug 09, 2017 at 11:21:28AM +0200, Javier Martinez Canillas wrote:
> I2C drivers were required to have an I2C device ID table even if were for
> devices that would only be registered using a specific firmware interface
> (e.g: OF or ACPI).
>
> But commit da10c06a044b ("i2c: Make I2C ID tabl
On Mon, Aug 07, 2017 at 05:10:58PM -0400, Stephen Douthit wrote:
> Hello all,
>
> We ran into an issue where the ipmi_ssif and i2c-ismt drivers don't
> agree on the format for data returned by i2c_smbus_read_block_data()
>
> Looking at the traffic on the wire with a beagle analyzer:
> -
> Pac
> -Original Message-
> From: linux-cifs-ow...@vger.kernel.org [mailto:linux-cifs-
> ow...@vger.kernel.org] On Behalf Of Christoph Hellwig
> Sent: Sunday, August 13, 2017 6:12 AM
> To: Long Li
> Cc: Steve French ; linux-c...@vger.kernel.org; samba-
> techni...@lists.samba.org; linux-kernel@
Benjamin Herrenschmidt [b...@au1.ibm.com] wrote:
> On Mon, 2017-08-14 at 17:02 +1000, Michael Neuling wrote:
> > > +/*
> > > + * We need to assign an unique thread id to each thread in a process.
> > > This
> > > + * thread id is intended to be used with the Fast Thread-wakeup (aka
> > > Core-
>
On Mon, Aug 14, 2017 at 3:18 PM, Michal Hocko wrote:
> Hi,
> I am having issues with nouveau driver in 4.11 Debian distribution
> kernel. I can start X session but the screen locks up e.g. when I try to
> exit mplayer fullscreen mode. The lock is swamped with tons of
> nouveau :03:00.0: fifo:
On 08/14/2017 01:53 PM, Guenter Roeck wrote:
On Mon, Aug 14, 2017 at 10:26:30AM -0500, Eddie James wrote:
From: "Edward A. James"
Signed-off-by: Edward A. James
---
Documentation/hwmon/ibm-cffps | 54 +++
1 file changed, 54 insertions(+)
create m
On Mon, Aug 14, 2017 at 01:55:41PM -0500, Eddie James wrote:
> From: "Edward A. James"
>
> Export all the available status registers through debugfs. This is
> useful for hardware diagnostics, especially on multi-page pmbus devices,
> as user-space access of the i2c space could corrupt the pmbus
On Tue, Aug 01, 2017 at 02:36:07PM +0100, Punit Agrawal wrote:
> During the driver init, the ghes driver initialises some data structures
Let's stick to "GHES" in capital letters everywhere.
> which are only used if a GHES platform device is probed. Similarly, the
> init function also checks for
On Sat, Aug 12, 2017 at 05:24:03PM +0530, Vikram N wrote:
> else
> - status = spi_sync(spi, message);
> + status = spidev->bus_locked ? spi_sync_locked(spi, message) :
> + spi_sync(spi, message);
Please don't abuse the ternery operator, pe
Hi,
I am having issues with nouveau driver in 4.11 Debian distribution
kernel. I can start X session but the screen locks up e.g. when I try to
exit mplayer fullscreen mode. The lock is swamped with tons of
nouveau :03:00.0: fifo: SCHED_ERROR 13 []
messages and I also can see some warnings
--
On Mon, Aug 14, 2017 at 05:08:42PM +0530, Bhumika Goyal wrote:
> Make these const as they are only passed as the 2nd argument to the function
> snd_soc_register_platform, which is of type const.
> Done using Coccinelle.
>
> Signed-off-by: Bhumika Goyal
Acked-by: Nicolin Chen
Thanks
> ---
> s
On Mon, 14 Aug 2017, Thomas Gleixner wrote:
On Wed, 9 Aug 2017, Vikas Shivappa wrote:
@@ -426,6 +426,9 @@ static int domain_setup_mon_state(struct rdt_resource *r,
struct rdt_domain *d)
GFP_KERNEL);
if (!d->rmid_busy_llc)
Nicholas Piggin [npig...@gmail.com] wrote:
> On Mon, 14 Aug 2017 15:21:48 +1000
> Michael Ellerman wrote:
>
> > Sukadev Bhattiprolu writes:
>
> > > arch/powerpc/include/asm/vas.h | 35
> > > arch/powerpc/include/uapi/asm/vas.h | 25 +++
> >
> > I thought we weren't exposing VAS
tsc_early_init():
Use verious methods to determine the availability of TSC feature and its
frequency early in boot, and if that is possible initialize TSC and also
call sched_clock_early_init() to be able to get timestamps early in boot.
tsc_early_fini()
Implement the finish part of early tsc feat
In Linux printk() can output timestamps next to every line. This is very
useful for tracking regressions, and finding places that can be optimized.
However, the timestamps are available only later in boot. On smaller
machines it is insignificant amount of time, but on larger it can be many
seconds
changelog
-
v3 - v4
- Fixed tsc_early_fini() call to be in the 2nd patch as reported
by Dou Liyang
- Improved comment before __use_sched_clock_early to explain why
we need both booleans.
- Simplified valid_clock logic in read_boot_clock64().
v2 -
On Mon, Aug 14, 2017 at 05:08:47PM +0530, Bhumika Goyal wrote:
> Make this const as it is only passed as the 2nd argument to the function
> devm_snd_soc_register_platform, which is of type const.
> Done using Coccinelle.
>
> Signed-off-by: Bhumika Goyal
> ---
> sound/soc/samsung/idma.c | 2 +-
>
On Wed, Aug 9, 2017 at 1:07 PM, Tycho Andersen wrote:
> From: Juerg Haefliger
>
> This test simply reads from userspace memory via the kernel's linear
> map.
>
> hugepages is only supported on x86 right now, hence the ifdef.
I'd prefer that the #ifdef is handled in the .c file. The result is
tha
> -Original Message-
> From: linux-cifs-ow...@vger.kernel.org [mailto:linux-cifs-
> ow...@vger.kernel.org] On Behalf Of Long Li
> Sent: Wednesday, August 2, 2017 4:10 PM
> To: Steve French ; linux-c...@vger.kernel.org; samba-
> techni...@lists.samba.org; linux-kernel@vger.kernel.org
> Cc: L
On Mon, 2017-08-14 at 20:35 +0200, Borislav Petkov wrote:
> On Mon, Aug 14, 2017 at 06:17:47PM +, Kani, Toshimitsu wrote:
> > Right, ghes_edac_report_mem_error() gets serialized per a GHES
> > entry, but not globally.
>
> Globally what?
GHES v2's ACK is not a global lock. So, it does not gua
> -Original Message-
> From: linux-cifs-ow...@vger.kernel.org [mailto:linux-cifs-
> ow...@vger.kernel.org] On Behalf Of Long Li
> Sent: Monday, August 14, 2017 2:20 PM
> To: Christoph Hellwig
> Cc: Steve French ; linux-c...@vger.kernel.org; samba-
> techni...@lists.samba.org; linux-kernel@
The pll post divider code was using DIV_ROUND_UP when determining the
divider value best suited to produce the target frequency.
Using DIV_ROUND_CLOSEST will give us better divider values when
the division results in a small remainder.
Also, change the post divider clock over to the determine_rate
From: Lori Hikichi
The iproc plls are capable of doing small rate changes without the
need for a full reset and re-lock procedure. This feature will
allow for small tweaks to the PLL rate to occur smoothly.
Signed-off-by: Lori Hikichi
---
drivers/clk/bcm/clk-iproc-pll.c | 47 +
On Mon, Aug 14, 2017 at 11:17:37AM -0700, Linus Torvalds wrote:
> Ok, guys, you ALL need to learn that blindly just trying to get rid of
> warnings IS A HORRIBLE IDEA.
Not blindly - I was actually suggesting/asking whether falling back to
the TSC that early during boot might make more sense than u
From: Lori Hikichi
There were a few fields in the iproc pll data structures that were
holding information that was not true state information.
Using stack variables is sufficient and simplifies the structure.
There are not any functional changes in this commit.
Signed-off-by: Lori Hikichi
---
Add the ability for the iproc pll to calculate the pll parameters at
runtime instead of only using predefined tables. This ability allows
the clock users to select from the full range of vco frequencies.
The old method of table based programming is retained so that existing
users will retain expect
This patchset enables the ability for the iproc plls to do small rate changes
without glitching the clock.
Lori Hikichi (4):
clk: iproc: Allow iproc pll to runtime calculate vco parameters
clk: iproc: Fix error in the pll post divider rate calculation
clk: iproc: Allow plls to do minor rate
Hi Heikki,
While testing with different type-c phones available in the market,
With some phones, I noticed that supports_usb_power_delivery
reports "no" eventhough an explicit pd contract has been
established. After spending sometime debugging, I noticed that
the root cause of this is that the par
From: "Edward A. James"
Export all the available status registers through debugfs. This is
useful for hardware diagnostics, especially on multi-page pmbus devices,
as user-space access of the i2c space could corrupt the pmbus page
accounting.
Signed-off-by: Edward A. James
Changes since v3:
*
On Mon, Aug 14, 2017 at 12:09:14PM +0900, Minchan Kim wrote:
> @@ -446,9 +450,7 @@ void tlb_finish_mmu(struct mmu_gather *tlb,
>*
>*/
> bool force = mm_tlb_flush_nested(tlb->mm);
> -
> arch_tlb_finish_mmu(tlb, start, end, force);
> - dec_tlb_flush_pending(tlb->mm);
>
On Mon, Aug 14, 2017 at 10:26:30AM -0500, Eddie James wrote:
> From: "Edward A. James"
>
> Signed-off-by: Edward A. James
> ---
> Documentation/hwmon/ibm-cffps | 54
> +++
> 1 file changed, 54 insertions(+)
> create mode 100644 Documentation/hwmon/ibm-c
On 08/09/2017 01:07 PM, Tycho Andersen wrote:
> diff --git a/mm/xpfo.c b/mm/xpfo.c
> new file mode 100644
> index ..3cd45f68b5ad
> --- /dev/null
> +++ b/mm/xpfo.c
> @@ -0,0 +1,208 @@
> +/*
> + * Copyright (C) 2017 Hewlett Packard Enterprise Development, L.P.
> + * Copyright (C) 2016 Bro
On Mon, Aug 14, 2017 at 01:01:22PM +0100, Will Deacon wrote:
> Yeah, that's right, you can't use the STXR status flag to create control
> dependencies.
Just for my elucidation; you can't use it to create a control dependency
on the store, but you can use it to create a control dependency on the
co
Hi Arnaldo!
Maybe this would be the right time to incorporate the shell-based
perftool-testsuite [1] into perf-test, wouldn't it?
It already contains bunch of shell-based perf tests that cover
25+ RH bugs...
A little problem might be different design, since the testsuite
has multiple levels of h
On Tue, Aug 8, 2017 at 8:47 PM, Marcelo Ricardo Leitner
wrote:
> On Tue, Jul 18, 2017 at 04:55:57PM +0200, Alexander Potapenko wrote:
>> KMSAN reported use of uninitialized sctp_addr->v4.sin_addr.s_addr and
>> sctp_addr->v6.sin6_scope_id in sctp_v6_cmp_addr() (see below).
>> Make sure all fields o
KMSAN reported use of uninitialized sctp_addr->v4.sin_addr.s_addr and
sctp_addr->v6.sin6_scope_id in sctp_v6_cmp_addr() (see below).
Make sure all fields of an IPv6 address are initialized, which
guarantees that the IPv4 fields are also initialized.
On 08/14/2017 09:22 AM, Tycho Andersen wrote:
> On Sat, Aug 12, 2017 at 12:17:34PM +0100, Mark Rutland wrote:
>> Hi,
>>
>> On Fri, Aug 11, 2017 at 03:13:02PM -0600, Tycho Andersen wrote:
>>> On Fri, Aug 11, 2017 at 10:25:14AM -0700, Laura Abbott wrote:
On 08/09/2017 01:07 PM, Tycho Andersen wr
On Thu, Aug 3, 2017 at 5:32 AM, Lorenzo Pieralisi
wrote:
> This patch series is v3 of a previous posting:
>
> v2->v3:
> - Fixed DMA masks computation
> - Fixed size computation overflow in acpi_dma_get_range()
>
> v1->v2:
> - Reworked acpi_dma_get_range() flow and logs
>
Currently the device is kept in D0, there is an opportunity
to save power by enabling runtime pm.
Device can be daisy chained from PMIC and we can't rely on I2C core
for auto resume/suspend. Driver will decide when to resume/suspend.
Signed-off-by: Divagar Mohandass
---
drivers/misc/eeprom/at24
This adds support to fetch device property "size" from _DSD.
There is a CAT24C16/GT24C16S NVMEM chip part of the OV13858
camera module and it is connected to i2c bus on Intel KBL board.
This device will use the existing ACPI ID INT3499 and platform
fw will expose "read-only", "pagesize" and "size"
This adds eeprom "size" as optional property for i2c eeproms.
"size" should be mentioned in byte and it should refer
to the eeprom size. This will be read by the driver and
used to calculating the number of bytes in read/write calls.
Signed-off-by: Divagar Mohandass
---
Documentation/devicetree
This series adds support for eeprom "size" property which will be read by the
driver for eeprom size. The existing ACPI has a different default size which
can be overridden with a DSD property value provided by the platform FW.
This series also adds support for runtime PM. The eeprom driver curren
Hi Eric,
> Stefan Wahren hat am 14. August 2017 um 19:11
> geschrieben:
>
>
> Hi Florian,
>
> > Florian Fainelli hat am 14. August 2017 um 18:25
> > geschrieben:
> >
> >
> >
> >
> > On 08/08/2017 04:04 AM, Phil Elwell wrote:
> > > Secondary cores should enter a low-power idle state when
Hello Uwe,
On Mon, Aug 14, 2017 at 08:51:49AM +0200, Uwe Kleine-König wrote:
> Hello Clemens,
>
> On Sun, Aug 13, 2017 at 12:07:56AM +0200, Clemens Gruber wrote:
> > On Sat, Aug 12, 2017 at 09:54:51PM +0200, Uwe Kleine-König wrote:
> > > On Sat, Aug 12, 2017 at 05:12:10PM +0200, Clemens Gruber wr
On Monday, August 14, 2017, Nicolas Pitre wrote:
> > However, now with your mkcramfs tool, I can no longer mount my cramfs
> > image as the rootfs on boot. I was able to do that before (ie, 30
> minutes
> > ago) when using the community mkcramfs (ie, 30 minutes ago).
> >
> > I get this:
> >
> > [
On Mon, Aug 14, 2017 at 06:17:47PM +, Kani, Toshimitsu wrote:
> Right, ghes_edac_report_mem_error() gets serialized per a GHES entry,
> but not globally.
Globally what?
What is the actual potential scenario for concurrency issues you see?
Example pls.
--
Regards/Gruss,
Boris.
Good mail
Introduce a per-memory-cgroup oom_priority setting: an integer number
within the [-1, 1] range, which defines the order in which
the OOM killer selects victim memory cgroups.
OOM killer prefers memory cgroups with larger priority if they are
populated with elegible tasks.
The oom_priority
Traditionally, the OOM killer is operating on a process level.
Under oom conditions, it finds a process with the highest oom score
and kills it.
This behavior doesn't suit well the system with many running
containers:
1) There is no fairness between containers. A small container with
few large pr
The oom_kill_process() function consists of two logical parts:
the first one is responsible for considering task's children as
a potential victim and printing the debug information.
The second half is responsible for sending SIGKILL to all
tasks sharing the mm struct with the given victim.
This co
Update cgroups v2 docs.
Signed-off-by: Roman Gushchin
Cc: Michal Hocko
Cc: Vladimir Davydov
Cc: Johannes Weiner
Cc: Tetsuo Handa
Cc: David Rientjes
Cc: Tejun Heo
Cc: kernel-t...@fb.com
Cc: cgro...@vger.kernel.org
Cc: linux-...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: linux...@kv
This patchset makes the OOM killer cgroup-aware.
v5:
- Rebased on top of Michal Hocko's patches, which have changed the
way how OOM victims becoming an access to the memory
reserves. Dropped corresponding part of this patchset
- Separated the oom_kill_process() splitting into a standal
On Mon, 2017-08-14 at 13:34 -0400, Luiz Capitulino wrote:
> On Mon, 14 Aug 2017 19:01:09 +0200
>
> > What is the source of the load balancing inducing such latency when a single
> > task is affine to a CPU? If this is idle load balancing, it is now affine to
> > housekeepers. If this is task wakeu
VOTARY GITHUB writes:
> From 3200cb6fd787390df1bccf1bb1f7a67ca04136fd Mon Sep 17 00:00:00 2001
> From: VT-Github-Raspberrypi
> Date: Tue, 8 Aug 2017 16:57:15 +0530
> Subject: [PATCH] arm64: bcm2837 dts: enable bcm2708 frambuffer driver for the
> raspberry pi-3
>
> This fb drivers to make render
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
rcu/next
head: 33103e7b1f89ef432dfe3337d2a6932cdf5c1312
commit: 33103e7b1f89ef432dfe3337d2a6932cdf5c1312 [14/14] EXP: Trace tick return
from tick_nohz_stop_sched_tick
config: arm-shmobile_defconfig (attached as .confi
Hi,
On 08/13/2017 01:41 PM, Pavel Machek wrote:
> Hi!
>
>>> You mentioned you was working on RGB support prototype. Could you post
>>> copy of the patches (even if unfinished)?
>>
>> Unfortunately it is at the stage of unfinished proof of concept and
>> I haven't managed yet to try how it fits to
An if statement test like
if ((foo == bar) && (baz != qux))
can arguably be better written without the parentheses as
if (foo == bar && baz != qux)
Add a test to find these cases.
Signed-off-by: Joe Perches
---
David Miller recently commented on the use of unnecessary parenthese
> -Original Message-
> From: Christoph Hellwig [mailto:h...@infradead.org]
> Sent: Sunday, August 13, 2017 3:24 AM
> To: Long Li
> Cc: Steve French ; linux-c...@vger.kernel.org; samba-
> techni...@lists.samba.org; linux-kernel@vger.kernel.org; Long Li
>
> Subject: Re: [[PATCH v1] 16/37]
On Mon, 2017-08-14 at 20:05 +0200, Borislav Petkov wrote:
> On Mon, Aug 14, 2017 at 05:52:25PM +, Kani, Toshimitsu wrote:
> > Yes, but this ACK is done per a GHES entry as well.
>
> So is the ghes_edac_report_mem_error() call.
Right, ghes_edac_report_mem_error() gets serialized per a GHES ent
501 - 600 of 1283 matches
Mail list logo
