Hi all,
Changes since 20151217:
News: The arm defconfig build is fixed again.
The arm-soc tree lost its build failure.
The i2c tree still had its build failure for which I applied a patch.
The clockevents tree still had its build failure so I used the version
from next-20151216.
The pinctrl
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (powerpc
pseries_le_defconfig) failed like this:
mm/huge_memory.c: In function 'insert_pfn_pmd':
mm/huge_memory.c:970:21: error: implicit declaration of func
tion 'pfn_t_pmd' [-Werror=implicit-function-declaration]
entry
From: "Du, Changbin"
Queue a request to disabled ep doesn't make sense, and induce caller
make mistakes.
Here is a example for the android mtp gadget function driver. A mem
corruption can happen on below senario.
1) On disconnect, mtp driver disable its EPs,
2) During send_file_work and
On 12/17/2015 06:13 PM, Alexander Duyck wrote:
On Wed, Dec 16, 2015 at 11:59 PM, Hannes Reinecke wrote:
PCI-2.2 VPD entries have a maximum size of 32k, but might actually
be smaller than that. To figure out the actual size one has to read
the VPD area until the 'end marker' is reached.
Trying
Add driver for the TCON (timing controller) module. The TCON module
is a separate module attached after the DCU (display controller
unit). Each DCU instance has its own, directly connected TCON
instance. The DCU's RGB and timing signals are passing through
the TCON module. TCON can provide timing
Add the dcu and tcon nodes to enable the Display Controller Unit
and Timing Controller in Vybrid's SoC level device-tree file.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/vfxxx.dtsi | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/vfxxx.dtsi
Add the ipg (bus) clock for the TCON modules (Timing Controller). This
module is required by the new DCU DRM driver, since the display signals
pass through TCON.
Signed-off-by: Stefan Agner
---
drivers/clk/imx/clk-vf610.c | 3 +++
include/dt-bindings/clock/vf610-clock.h | 4 +++-
2
This patchset adds the missing pieces to make the Freescale
DCU DRM driver work on Freescale Vybrid.
Foremost, it adds support for the timing controller (TCON)
module. The module is between the Display Controller and the
actual output pins. It allows to alter the timings for RAW
TFT displays, but
Enable dcu node which is used by the DCU DRM driver. Assign the 5.7"
EDT panel with VGA resolution which Toradex sells often with the
evaluation board.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/vf-colibri-eval-v3.dtsi | 16 +++
arch/arm/boot/dts/vf-colibri.dtsi | 33
> >
> > diff --git a/include/linux/usb/gadget.h b/include/linux/usb/gadget.h
> > index 3d583a1..0c5d9ea 100644
> > --- a/include/linux/usb/gadget.h
> > +++ b/include/linux/usb/gadget.h
> > @@ -402,6 +402,9 @@ static inline void usb_ep_free_request(struct
> usb_ep *ep,
> > static inline int
Thanks to the patch.
On Fri, 2015-12-18 at 15:11 +0800, Daniel Kurtz wrote:
> This regulator is on a slow i2c bus. Register accesses are very simple,
> they all either enable/disable a regulator channel, or select a new
> voltage level. Thus, reading registers from the device will always
>
On Thu, 17 Dec 2015 19:26:10 +
Daniel Thompson wrote:
> On Wed, Dec 16, 2015 at 05:47:09PM +, Marc Zyngier wrote:
> > Hi Daniel,
>
> Hi Marc
>
> Thanks for the review.
>
>
> > On 16/12/15 17:08, Daniel Thompson wrote:
> > > It is possible for the secure world to reserve certain SGI
> On 18.12.2015, at 07:05, Vinod Koul wrote:
>
> On Thu, Dec 17, 2015 at 07:11:48PM +0100, Martin Sperl wrote:
>
>> +
>> +/* Setup addresses */
>> +if (d->dir == DMA_DEV_TO_MEM) {
>> +control_block->info = BCM2835_DMA_D_INC |
On 2015/12/18 15:04, Wangnan (F) wrote:
On 2015/12/18 14:19, Alexei Starovoitov wrote:
On Fri, Dec 18, 2015 at 09:47:11AM +0800, Wangnan (F) wrote:
This is a limitation in tools/lib/bpf/libbpf.h, which has a #include
in its header.
libbpf.h requires this include because its API uses
> From: Allen Hubbe [mailto:alle...@gmail.com]
> Sent: Friday, December 18, 2015 12:46 AM
> To: Yu, Xiangliang
> Cc: jdma...@kudzu.us; dave.ji...@intel.com; linux-...@googlegroups.com;
> linux-kernel@vger.kernel.org; SPG_Linux_Kernel
> Subject: Re: [PATCH 1/3] NTB: Add AMD PCI-Express NTB driver
>
On Thu, Dec 17, 2015 at 11:23:31AM -0800, Eduardo Valentin wrote:
> On Wed, Dec 16, 2015 at 07:23:22PM +0800, Daniel Kurtz wrote:
> > On Mon, Nov 30, 2015 at 7:42 PM, Sascha Hauer
> > wrote:
> > > This adds the device tree binding documentation for the mediatek thermal
> > > controller found on
This regulator is on a slow i2c bus. Register accesses are very simple,
they all either enable/disable a regulator channel, or select a new
voltage level. Thus, reading registers from the device will always
return what was last written.
Therefore we can save a lot of time when reading registers
On 2015/12/18 14:19, Alexei Starovoitov wrote:
On Fri, Dec 18, 2015 at 09:47:11AM +0800, Wangnan (F) wrote:
This is a limitation in tools/lib/bpf/libbpf.h, which has a #include
in its header.
libbpf.h requires this include because its API uses ERR_PTR() to encode
error code.
For example,
> -Original Message-
> From: Nicholas Krause [mailto:xerofo...@gmail.com]
> Sent: Monday, July 06, 2015 10:06 PM
> To: kashyap.de...@avagotech.com
> Cc: sumit.sax...@avagotech.com; uday.ling...@avagotech.com;
> jbottom...@odin.com; megaraidlinux@avagotech.com; linux-
>
>Hmm...like this ?
> sysctl.vm.fallback_mirror_memory = 0 // never fallback # default.
> sysctl.vm.fallback_mirror_memory = 1 // the user memory may be
> allocated from mirrored zone.
> sysctl.vm.fallback_mirror_memory = 2 // usually kernel allocates
> memory from mirrored
> -int
> +static int
> megasas_alloc_cmds_fusion(struct megasas_instance *instance) {
> int i, j, count;
Good catch. Let's not include patch to avoid further confusion on series
of acked patch which are not making significant functional difference.
NACK as not making any functional
On Fri, Dec 18, 2015 at 09:17:29AM +1100, Stephen Rothwell wrote:
> Hi Thierry,
>
> I noticed that you have rebased the drm-panel tree today. Unfortunately,
> Dave merged the previous version of your tree :-(
And I had hoped to have been fast enough. Sorry for the mess.
> So, now in linux-next
On December 17, 2015 9:29:21 PM PST, Andy Lutomirski
wrote:
>On Dec 17, 2015 6:53 PM, "Dave Hansen"
>wrote:
>>
>> On 12/17/2015 06:32 PM, Andy Lutomirski wrote:
>> > On Thu, Dec 17, 2015 at 6:13 PM, Dave Hansen
> wrote:
>> >> But what about the register state when delivering a signal? Don't
> The search, share, connect(?), and settings keys
I tested the patch again with xev and found that those "charm" keys
don't respond both on hid-microsoft and hid-multitouch, while other
keys respond. I'll have a further look.
Anyway, keys working with hid-microsoft also work with hid-multitouch,
On Fri, Dec 18, 2015 at 01:34:16PM +0800, Herbert Xu wrote:
> On Fri, Dec 18, 2015 at 09:39:22AM +0800, kernel test robot wrote:
> > FYI, we noticed the below changes on
> >
> > https://github.com/0day-ci/linux
> > Herbert-Xu/rhashtable-Fix-walker-list-corruption/20151216-164833
> > commit
On Wed, Dec 16, 2015 at 02:58:08PM +0800, Ming Lei wrote:
> On Wed, Dec 16, 2015 at 1:01 PM, Yang Shi wrote:
>
> >
> > I recalled Steven confirmed raw_spin_lock has the lockdep benefit too in the
> > patch review for changing to raw lock.
> >
> > Please check this thread out
> >
On Fri, Dec 18, 2015 at 09:47:11AM +0800, Wangnan (F) wrote:
>
> This is a limitation in tools/lib/bpf/libbpf.h, which has a #include
>
> in its header.
>
> libbpf.h requires this include because its API uses ERR_PTR() to encode
> error code.
> For example, when calling bpf_object__open(),
Hi Stephen,
The issue I pointed out is the relevant and is fully related to the statement-
" After merging the pinctrl tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:"
Even I tried the build for config "arm multi_v7_defconfig" it was compile
failed. After fixing this
On Fri, Dec 18, 2015 at 7:31 AM, Doug Anderson wrote:
> Hi,
>
> On Thu, Dec 17, 2015 at 12:30 PM, Douglas Anderson
> wrote:
>> The __iommu_alloc_buffer() is expected to be called to allocate pretty
>> sizeable buffers. Upon simple tests of video I saw it trying to
>> allocate 4,194,304 bytes.
Please let me gently ping in case the maintainers might be away from keyboard
during the Christmas days.
I want this trivial one for the next merge window.
Thanks!
2015-11-05 15:47 GMT+09:00 Masahiro Yamada :
> The UniPhier SoCs support pinctrl drivers.
>
> Signed-off-by: Masahiro Yamada
>
On Thu, Dec 17, 2015 at 07:11:48PM +0100, Martin Sperl wrote:
> +
> + /* Setup addresses */
> + if (d->dir == DMA_DEV_TO_MEM) {
> + control_block->info = BCM2835_DMA_D_INC |
> +
Hi Pramod,
On Fri, 18 Dec 2015 05:34:58 + Pramod Kumar wrote:
>
> Hi Stephen/Linus,
>
> Please suggest us how could we fix this issue.
I think you issue is different from what I reported, What I reported
was caused by the addition of the dependency on COMPILE_TEST which
allowed the driver
On 2015-12-15 22:02, Prarit Bhargava wrote:
> Some systems erroneously set the maximum time window field of
> MSR_PKG_POWER_INFO register to 0. This results in a user not being able
> to set the time windows for the package. In some cases, however, RAPL
> will still continue to work with a small
On 12/18/2015 12:15 AM, Tony Lindgren wrote:
> * Rob Herring [151211 07:10]:
>> On Fri, Dec 11, 2015 at 09:39:59AM +0530, Vignesh R wrote:
>>> Add qspi memory mapped region entries for DRA7xx based SoCs. Also,
>>> update the binding documents for the controller to document this change.
>>>
>>>
Existing test-all.c doesn't check BPF related features. For environment
with all other features enabled, BPF would be considered enabled
without doing real feature check.
This patch adds test-bpf.c into test-all.c.
Signed-off-by: Wang Nan
Cc: Arnaldo Carvalho de Melo
Cc: Namhyung Kim
Cc: Jiri
On Mon, Dec 14, 2015 at 10:47:37PM +0200, Peter Ujfalusi wrote:
> Hi,
>
> As it has been discussed in the following thread:
> http://www.gossamer-threads.com/lists/linux/kernel/2181487#2181487
>
> With this series I have taken a path which would result two new API, which can
> be used to convert
On Thu, Dec 10, 2015 at 03:07:23PM +, Damien Horsley wrote:
> From: "Damien.Horsley"
>
> Use of the CANCEL bit in mdc_terminate_all creates an
> additional 'command done' to appear in the registers (in
> addition to an interrupt).
>
> In addition, there is a potential race between
>
p)
> ^
>
> Caused by commit
>
> 616043d58a89 ("pinctrl: Rename gpio driver from cygnus to iproc")
>
> I have used the pinctrl tree from next-20151217 for today.
>
> --
> Cheers,
> Stephen Rothwells...@canb.auug.org.au
On Fri, Dec 18, 2015 at 09:39:22AM +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> https://github.com/0day-ci/linux
> Herbert-Xu/rhashtable-Fix-walker-list-corruption/20151216-164833
> commit f9f51b8070be3e829100614a7372b219723b864f ("rhashtable: Fix walker list
>
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/powerpc/include/asm/pgtable.h
between commit:
ee4889c7bc2a ("powerpc/mm: Don't have generic headers introduce functions
touching pte bits")
from the powerpc tree and commit:
e0e8474c0d55 ("mm, dax,
On Wed, Dec 16, 2015 at 03:19:05PM +0200, Peter Ujfalusi wrote:
> Due to changes in device and platform code drivers w/o probe will fail to
> load. This means that the devices for eDMA TPTCs are goign to be without
> driver and omap hwmod code will turn them off after the kernel finished
>
On Dec 17, 2015 6:53 PM, "Dave Hansen" wrote:
>
> On 12/17/2015 06:32 PM, Andy Lutomirski wrote:
> > On Thu, Dec 17, 2015 at 6:13 PM, Dave Hansen
> > wrote:
> >> But what about the register state when delivering a signal? Don't we
> >> set the registers to the init state? Do we need to
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/x86/kvm/mmu.c
between commits:
7ee0e5b29d27 ("KVM: x86: MMU: Remove unused parameter of __direct_map()")
029499b47738 ("KVM: x86: MMU: Make mmu_set_spte() return emulate value")
from the kvm tree and
On Thu, Dec 17, 2015 at 11:30:57PM +, Mans Rullgard wrote:
> If the "dma-channels" DT property is missing, the dw_dma_parse_dt()
> function return NULL, but not before allocating memory for a struct
> dw_dma_platform_data through devres. If the device supports parameter
> detection, the probe
On Thu, Dec 17, 2015 at 09:48:44AM -0800, Tony Lindgren wrote:
> * Peter Ujfalusi [151217 05:33]:
> > Hi,
> >
> > Changes since v1:
> > - Updated to use the non 16bit arrays [1]
> > - send the two patch as a series
> >
> > [1]
> > As it has been discussed earlier:
> >
Still something with af_unix and/or wake code on rc5 :
[34971.300210] Unable to handle kernel paging request at virtual address
56ac56ac
[34971.307455] pgd = a8c3
[34971.310164] [56ac56ac] *pgd=
[34971.313761] Internal error: Oops: 8005 [#1] PREEMPT SMP ARM
[34971.319683]
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/arm/mm/dma-mapping.c
drivers/iommu/intel-iommu.c
drivers/staging/android/ion/ion_chunk_heap.c
between commit:
3e6110fd5480 ("Revert "scatterlist: use sg_phys()"")
from Linus' tree and commit:
On 12/17/15 20:25, H. Peter Anvin wrote:
>
> /* DECLARE_LINKTABLE_RO */
> extern const struct foo tablename[], tablename__end[];
>
> /* DEFINE_LINKTABLE_RO */
> DECLARE_LINKTABLE_RO(struct foo, tablename);
>
> const struct
> foo__attribute__((used,section(".rodata.tbl.tablename.0")))
On 12/18/2015 01:38 PM, Alex Williamson wrote:
On Fri, 2015-12-18 at 13:05 +1100, Alexey Kardashevskiy wrote:
On 11/24/2015 07:43 AM, Alex Williamson wrote:
Please see the commit log and comments in patch 1 for a general
explanation of the problems that this series tries to address. The
On 18.12.2015 12:32, Pankaj Dubey wrote:
> In this series I am splitting up SoC specific PMU configuration data into
> mach-exynos folder itself, before moving all of them under
> drivers/soc/samsung/. Also instead of making all changes in single patch it
> has been broken into SoC specific
On 12/17/15 15:46, Luis R. Rodriguez wrote:
>
> I explain why I do that there but the gist of it is that on Linux we may also
> want stronger semantics for specific linker table solutions, and solutions
> such
> as those devised on the IOMMU init stuff do memmove() for sorting depending on
>
Move pinctrl initialization earlier in boot so that real devices can find
their pctldev without probe deferring.
Signed-off-by: Daniel Kurtz
---
drivers/pinctrl/mediatek/pinctrl-mt6397.c | 2 +-
drivers/pinctrl/mediatek/pinctrl-mt8127.c | 2 +-
drivers/pinctrl/mediatek/pinctrl-mt8135.c | 2 +-
On Fri, 18 Dec 2015 03:46:41 +0900,
Russell King - ARM Linux wrote:
>
> On Thu, Dec 17, 2015 at 07:51:14AM -0800, Dan Williams wrote:
> > The commit below causes the libnvdimm sub-system to stop loading.
> > This is due to the fact that nvdimm_bus_match() returns the result of
> > test_bit()
uct cygnus_gpio *chip)
^
Caused by commit
616043d58a89 ("pinctrl: Rename gpio driver from cygnus to iproc")
I have used the pinctrl tree from next-20151217 for today.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
--
To unsubscribe from this list:
Hi Krzysztof,
On Thursday 17 December 2015 11:01 AM, Krzysztof Kozlowski wrote:
> On 17.11.2015 15:05, Pankaj Dubey wrote:
>> In this series I am splitting up SoC specific PMU configuration data into
>> mach-exynos folder itself, before moving all of them under
>> drivers/soc/samsung/. Also
all,
I just started getting these "No irq handler for vector" messages
after upgrading to linux-next 20151217+.
(from the first boot)
...
[2.282652] [drm] Initialized drm 1.1.0 20060810
[2.318806] AVX version of gcm_enc/dec engaged.
[2.318810] AES CTR mode by8 optimizati
Hi Krzysztof,
On Thursday 17 December 2015 10:44 AM, Krzysztof Kozlowski wrote:
> On 12.12.2015 16:43, Pankaj Dubey wrote:
>> THIS IS A RESEND OF ONCE MERGED INTO kgene/for-next AND LOST PATCHES
>>
>> Series v5 got merged in kgene/for-next but due to last moment change before
>> pull
>> these
This patch splits up mach-exynos/pmu.c file, and moves exynos5250,
PMU configuration data and functions handing data into exynos5250
SoC specific PMU file mach-exynos/exynos5250-pmu.c.
Signed-off-by: Pankaj Dubey
Reviewed-by: Krzysztof Kozlowski
---
arch/arm/mach-exynos/Makefile | 4
This patch splits up mach-exynos/pmu.c file, and moves exynos3250 PMU
configuration data and functions handing those data into exynos3250
SoC specific PMU file mach-exynos/exynos3250-pmu.c.
Signed-off-by: Pankaj Dubey
Reviewed-by: Krzysztof Kozlowski
---
arch/arm/mach-exynos/Makefile |
This patch moves Exynos PMU driver implementation from "arm/mach-exynos"
to "drivers/soc/samsung". This driver is mainly used for setting misc
bits of register from PMU IP of Exynos SoC which will be required to
configure before Suspend/Resume. Currently all these settings are done
in
This patch splits up mach-exynos/pmu.c file, and moves exynos5420,
PMU configuration data and functions handing data into exynos5420
SoC specific PMU file mach-exynos/exynos5420-pmu.c.
Signed-off-by: Pankaj Dubey
Reviewed-by: Krzysztof Kozlowski
[for testing on Peach-Pi (Exynos5880)]
Tested-by:
This patch splits up mach-exynos/pmu.c file, and moves exynos4210,
exynos4412 and exynos4212 PMU configuration data and functions handing
data into a common exynos4 SoC specific PMU file mach-exynos/exynos4-pmu.c.
Signed-off-by: Pankaj Dubey
Reviewed-by: Krzysztof Kozlowski
[for testing on
In this series I am splitting up SoC specific PMU configuration data into
mach-exynos folder itself, before moving all of them under
drivers/soc/samsung/. Also instead of making all changes in single patch it
has been broken into SoC specific patches to avoid large size of patch.
With this
Moving Exynos PMU specific header file into "include/linux/soc/samsung"
thus updated affected files under "mach-exynos" to use new location of
these header files.
Signed-off-by: Amit Daniel Kachhap
Signed-off-by: Pankaj Dubey
Reviewed-by: Krzysztof Kozlowski
[for testing on Trats2 (Exynos4412)
On 2015/12/17 21:46, Daniel Wagner wrote:
On 12/17/2015 11:09 AM, Wangnan (F) wrote:
On 2015/12/17 16:29, Daniel Wagner wrote:
On 12/17/2015 08:03 AM, Daniel Wagner wrote:
Patch number 2 didn't apply cleanly.
Because I have another patch in my local tree which also modifis bpf
Makefile:
From: "james.chen"
Something wrong in suspend/resume of kernel v3.14 for the function of
wake-on-touch. The function of device_may_wakeup will return true if
the device supports wake-on-touch (for example, kitty and buddy).
So, modify the code from "if (device_may_wakeup(dev))" to
"if
On Thu, Dec 17, 2015 at 6:50 PM, Pandruvada, Srinivas
wrote:
> On Thu, 2015-12-17 at 18:33 -0800, Nish Aravamudan wrote:
>> On Thu, Dec 17, 2015 at 5:11 PM, Pandruvada, Srinivas
>> wrote:
>> > On Thu, 2015-12-17 at 17:08 -0800, Nish Aravamudan wrote:
>> > > On Thu, Dec 17, 2015 at 5:00 PM,
Move write data register before excute command to avoid
missing first byte write to nor flash
Signed-off-by: Bayi Cheng
---
the previous patch didn't drop the Change-Id
---
drivers/mtd/spi-nor/mtk-quadspi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 12/17/2015 06:32 PM, Andy Lutomirski wrote:
> On Thu, Dec 17, 2015 at 6:13 PM, Dave Hansen
> wrote:
>> But what about the register state when delivering a signal? Don't we
>> set the registers to the init state? Do we need to preserve PKRU state
>> instead of init'ing it? The init state
On 2015/12/17 21:30, Vladimir Davydov wrote:
> The rationale of separate swap counter is given by Johannes Weiner.
>
> Signed-off-by: Vladimir Davydov
> ---
> Changes in v2:
> - Add rationale of separate swap counter provided by Johannes.
>
> Documentation/cgroup.txt | 33
On Thu, 2015-12-17 at 18:33 -0800, Nish Aravamudan wrote:
> On Thu, Dec 17, 2015 at 5:11 PM, Pandruvada, Srinivas
> wrote:
> > On Thu, 2015-12-17 at 17:08 -0800, Nish Aravamudan wrote:
> > > On Thu, Dec 17, 2015 at 5:00 PM, Pandruvada, Srinivas
> > > wrote:
> > > > Hi Andy,
> > > >
> > > > As
On Thu, 2015-12-17 at 16:43 +0100, Jirka Hladky wrote:
> Hi Peter,
>
> I'm not sure how to do the bisecting and avoid landing at:
>
> [2a595721a1fa6b684c1c818f379bef834ac3d65e] sched/numa: Convert
> sched_numa_balancing to a static_branch
>
> I have redone the bisecting but I have landed again
On Thu, 17 Dec 2015, Paul Gortmaker wrote:
The Kconfig currently controlling compilation of this code is:
config HUGETLBFS
bool "HugeTLB file system support"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially
1ddaa021b000220b5f2ad023e4f15ed44990974b:
MAINTAINERS: brcmnand: Add co-maintainer for Broadcom SoCs (2015-11-18
13:16:58 -0800)
are available in the git repository at:
git://git.infradead.org/linux-mtd.git tags/for-linus-20151217
for you to fetch changes up to e488ca9f8d4f62c2dc36bfa5c32f68e7f05ab381:
doc: dt: mtd
On Fri, 2015-12-18 at 13:05 +1100, Alexey Kardashevskiy wrote:
> On 11/24/2015 07:43 AM, Alex Williamson wrote:
> > Please see the commit log and comments in patch 1 for a general
> > explanation of the problems that this series tries to address. The
> > general problem is that we have several
move write data register before excute command to avoid
missing first byte write to nor flash
Change-Id: Ie9d7ae30f9de1f3e976d2e1de5d8ee28837598c8
Signed-off-by: Bayi Cheng
---
drivers/mtd/spi-nor/mtk-quadspi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 2015/12/18 6:19, Johannes Weiner wrote:
To make it easier to quickly find what's needed list the basic
resource controllers of cgroup2 first - io, memory, cpu - while
pushing the more exotic and/or legacy controllers to the bottom.
Signed-off-by: Johannes Weiner
Acked-by: Zefan Li
---
Are you in need of private or business loans for various purposes? if yes,apply
now
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the
On Thu, Dec 17, 2015 at 5:11 PM, Pandruvada, Srinivas
wrote:
> On Thu, 2015-12-17 at 17:08 -0800, Nish Aravamudan wrote:
>> On Thu, Dec 17, 2015 at 5:00 PM, Pandruvada, Srinivas
>> wrote:
>> > Hi Andy,
>> >
>> > As per Nish these patches are impacting sensors on Yoga.
>> >
On Thu, Dec 17, 2015 at 6:13 PM, Dave Hansen
wrote:
> On 12/17/2015 05:48 PM, Andy Lutomirski wrote:
>> I think that, for PKRU in particular, we want the default signal
>> handling behavior to be a bit unusual.
>>
>> When a signal is delivered, I think we should save the entire xstate
>>
On Fri, Dec 18, 2015 at 12:07:08AM +0800, Xin Long wrote:
>
> I'm just wondering, why do not we handle the genuine double rehash
> issue inside rhashtable? i mean it's just a temporary error that a
> simple retry may fix it.
Because a double rehash means that someone has cracked your hash
On 2015/12/18 6:19, Johannes Weiner wrote:
The config options for the different cgroup controllers use various
terms: resource controller, cgroup subsystem, etc. Simplify this to
"controller", which is clear enough in the cgroup context.
Signed-off-by: Johannes Weiner
---
init/Kconfig | 65
On Mon, Dec 07, 2015 at 03:09:11PM +0100, Cyrille Pitchen wrote:
> This patch reworks the support of Quad and Dual SPI protocols for Micron,
> Spansion and Macronix Quad/Dual capable memories. Indeed, in the best
> case, only Spansion memories are correctly supported by the current
> spi-nor
On 12/17/2015 05:48 PM, Andy Lutomirski wrote:
> I think that, for PKRU in particular, we want the default signal
> handling behavior to be a bit unusual.
>
> When a signal is delivered, I think we should save the entire xstate
> including PKRU. I see no reason to do anything other than that.
On 2015/12/18 3:43, Luck, Tony wrote:
As Tony requested, we may need a knob to stop a fallback in "movable->normal",
later.
If the mirrored memory is small and the other is large,
I think we can both enable "non-mirrored -> normal" and "normal ->
non-mirrored".
Size of mirrored memory can
(Hit send too early; a few more comments)
On Mon, Dec 07, 2015 at 03:09:10PM +0100, Cyrille Pitchen wrote:
> drivers/mtd/spi-nor/spi-nor.c | 52
> +++
> include/linux/mtd/spi-nor.h | 23 +--
> 2 files changed, 69 insertions(+), 6
On 11/24/2015 07:43 AM, Alex Williamson wrote:
Please see the commit log and comments in patch 1 for a general
explanation of the problems that this series tries to address. The
general problem is that we have several cases where we want to expose
variable sized information to the user, whether
Hi Dave,
[auto build test ERROR on v4.4-rc5]
[also build test ERROR on next-20151217]
[cannot apply to tip/x86/core]
url:
https://github.com/0day-ci/linux/commits/Dave-Hansen/x86-pass-in-size-to-early-cmdline-parsing/20151218-060427
config: i386-allyesconfig (attached as .config)
reproduce
On Thu, Dec 17, 2015 at 5:16 PM, Srinivas Pandruvada
wrote:
> On Thu, 2015-12-17 at 17:07 -0800, Nish Aravamudan wrote:
>> On Thu, Dec 17, 2015 at 4:51 PM, Srinivas Pandruvada
>> wrote:
>> > On Thu, 2015-12-17 at 15:38 -0800, Nish Aravamudan wrote:
>> > > [Starting a new thread from
On 17-12-15, 23:30, Mans Rullgard wrote:
> If the "dma-channels" DT property is missing, the dw_dma_parse_dt()
> function return NULL, but not before allocating memory for a struct
> dw_dma_platform_data through devres. If the device supports parameter
> detection, the probe still succeeds and
Hi Mark:
在 2015/12/17 21:52, Mark Rutland 写道:
> On Thu, Dec 17, 2015 at 07:56:34PM +0800, MaJun wrote:
>> From: Ma Jun
[...]
>> +- compatible: Should be "hisilicon,mbigen-v2"
>> +
>> +- reg: Specifies the base physical address and size of the Mbigen
>> + registers.
>> +
>> +- interrupt
Thanks for testing.
On Thu, Dec 17, 2015 at 03:31:30PM -0800, Stephane Eranian wrote:
> I would not add a --topdown option but instead a --metric option with
> arguments
> such that other metrics could be added later:
>
>$ perf stat --metrics topdown -I 1000 -a sleep 100
>
> If you do
Hi Cyrille,
On Mon, Dec 07, 2015 at 03:09:10PM +0100, Cyrille Pitchen wrote:
> The quad (or dual) mode of a spi-nor memory may be enabled at boot time by
> non-volatile bits in some setting register. Also such a mode may have
> already been enabled at early stage by some boot loader.
>
> Hence,
On 17-12-15, 19:04, Bartlomiej Zolnierkiewicz wrote:
> Commit 01fb4d3c39d3 ("PM / OPP: Parse 'opp--'
> bindings") broke support for parsing standard opp-microvolt and
> opp-microamp properties. Fix it by setting 'name' string to
> proper value for !prop cases.
>
> Cc: Viresh Kumar
> Cc: Lee
Hi all-
I think that, for PKRU in particular, we want the default signal
handling behavior to be a bit unusual.
When a signal is delivered, I think we should save the entire xstate
including PKRU. I see no reason to do anything other than that.
When a signal returns (sigreturn is called),
On 2015/12/18 7:11, Alexei Starovoitov wrote:
On Thu, Dec 17, 2015 at 05:23:12AM +, Wang Nan wrote:
We are going to uses libbpf to replace old libbpf.[ch] and
bpf_load.[ch]. This is the first patch of this work. In this patch,
several macros and helpers in libbpf.[ch] and bpf_load.[ch]
On Thursday 12/17 at 17:08 -0800, Eric Dumazet wrote:
> On Thu, 2015-12-17 at 15:52 -0800, Calvin Owens wrote:
> > With built-in netconsole and IXGBE, configuring netconsole via the kernel
> > cmdline results in the following panic at boot:
> >
> > netpoll: netconsole: device eth0 not up yet,
On Thursday 12/17 at 17:10 -0800, Stephen Hemminger wrote:
> On Thu, 17 Dec 2015 15:52:39 -0800
> Calvin Owens wrote:
>
> > With built-in netconsole and IXGBE, configuring netconsole via the kernel
> > cmdline results in the following panic at boot:
> >
> > netpoll: netconsole: device eth0
FYI, we noticed the below changes on
https://github.com/0day-ci/linux
Herbert-Xu/rhashtable-Fix-walker-list-corruption/20151216-164833
commit f9f51b8070be3e829100614a7372b219723b864f ("rhashtable: Fix walker list
corruption")
[8.933376] ===
[8.933376]
Julian Margetson writes:
> On 12/17/2015 8:06 PM, Måns Rullgård wrote:
>> Julian Margetson writes:
>>
>>> On 12/17/2015 3:53 PM, Måns Rullgård wrote:
Julian Margetson writes:
> On 12/17/2015 2:51 PM, Måns Rullgård wrote:
>> Julian Margetson writes:
>>
>>> On
1 - 100 of 1668 matches
Mail list logo
