On 6/7/16, 4:26 PM, "Mike Kravetz" wrote:
>The write at the end of the test to restore nr_hugepages to its previous
>value is failing. This is because it is trying to write the number of
>bytes in the char array as opposed to the number of bytes in the string.
>
>Signed-off-by: Mike Kravetz
>
alloc_workqueue replaces deprecated create_workqueue().
The workqueue device_reset_wq has workitem &reset_data->reset_work per
adf_reset_dev_data. The workqueue pf2vf_resp_wq is a workqueue for
PF2VF responses has workitem &pf2vf_resp->pf2vf_resp_work per pf2vf_resp.
The workqueue adf_vf_stop_wq
On Mon, Jun 06, 2016 at 02:55:29PM -0400, Jarod Wilson wrote:
> On Mon, Jun 06, 2016 at 05:29:30PM +0100, Bert Kenward wrote:
> > 7000-series SFC NICs connected with an SFP+ module currently fail to
> > report any supported link speeds.
> >
> > Reported-by: Jarod Wilson
> > Signed-off-by: Bert Ke
On Tuesday, June 7, 2016 1:47:25 PM CEST Dave Hansen wrote:
> From: Dave Hansen
>
> These new syscalls are implemented as generic code, so enable
> them for architectures like arm64 which use the generic syscall
> table.
>
> According to Arnd:
>
> Even if the support is x86 specific for
Python doesn't do automatic expansion of paths. In case one passes
path of the from ~/foo/bar the gdb scripts won't automatically expand
that and as a result the symbols files won't be loaded. Fix this
by explicitly expanding all paths which begin with "~"
Signed-off-by: Nikolay Borisov
---
scri
On 06/07/16 13:12, Andrew Morton wrote:
> On Mon, 6 Jun 2016 22:11:37 -0700 Randy Dunlap wrote:
>
>> On 06/05/16 21:20, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20160603:
>>>
>>
>> on i386:
>>
>> mm/built-in.o: In function `init_cache_random_seq':
>> slub.c:(.text+0x76921): undef
On 6 June 2016 at 03:51, Shawn Lin wrote:
> Hi Stephen,
>
> On 2016/6/6 9:38, Stephen Rothwell wrote:
>>
>> Hi Ulf,
>>
>> After merging the mmc-uh tree, today's linux-next build (x86_64
>> allmodconfig) produced this warning:
>>
>> In file included from include/linux/err.h:4:0,
>>
On Tue, Jun 07, 2016 at 05:10:51PM -0400, Lyude Paul wrote:
> Managed to find someone in the office with one of these laptops and it looks
> like the adaptive keyboard works perfectly with this patch, so I can give my
> t-
> b:
>
> Tested-by: Lyude Paul
>
> Cheers,
> Lyude
>
> On T
On Tue, Jun 07, 2016 at 08:38:45PM +0300, Vladimir Zapolskiy wrote:
> The change adds a simple watchdog pretimeout framework infrastructure,
> its purpose is to allow users to select a desired handling of watchdog
> pretimeout events, which may be generated by some watchdog devices.
>
> A user sel
From: Jason Wang
Date: Wed, 1 Jun 2016 01:56:33 -0400
> We don't stop rx polling socket during rx processing, this will lead
> unnecessary wakeups from under layer net devices (E.g
> sock_def_readable() form tun). Rx will be slowed down in this
> way. This patch avoids this by stop polling socke
etr_ptff definitions are moved and renamed but we missed updating them
here and as a result s390 defconfig and allmodconfig was failing with
the error:
arch/s390/kvm/kvm-s390.c:230:45: error: 'ETR_PTFF_QAF' undeclared
Fixes: cc8f94656487 ("s390/time: move PTFF definitions")
Signed-off-by: Sudip Mu
Michal Hocko wrote:
> OK, so you are arming the timer for each mark_oom_victim regardless
> of the oom context. This means that you have replaced one potential
> lockup by other potential livelocks. Tasks from different oom domains
> might interfere here...
>
> Also this code doesn't even seem eas
Mateusz Guzik writes:
> On Tue, Jun 07, 2016 at 07:29:37PM +0800, Zhao Lei wrote:
>> In current system, when we set core_pattern to a pipe, both pipe program
>> and program's output are in host's filesystem.
>> But when we set core_pattern to a file, the container will write dump
>> into containe
> On Mon, Jun 06, 2016 at 05:40:19PM -0400, Jerome Glisse wrote:
> > Brokens how ? Symptoms ?
>
> Whoops, sorry, I meant to elaborate...
>
> After doing:
>
> echo "shutdown" > /sys/power/disk
> echo "disk" > /sys/power/state
>
> screen goes blank but machine remains powered on a
On Tue, Jun 07, 2016 at 02:10:28PM +, Zanoni, Paulo R wrote:
> I tested both patches you provided:
> - kbuild: do not append NOSTDINC_FLAGS to avoid rebuild in package
> targets
> - kbuild: Initialize NOSTDINC_CFLAGS
>
> Both seem to improve the situation to a point where, at least for a
> t
On Tue, 7 Jun 2016 13:59:53 -0700
Kees Cook wrote:
> >
> > I applied the series to kbuild.git#kbuild now, sorry for the delay.
>
> Awesome! Thank you very much. I'll prepare the latent entropy plugin
> for -next now too.
I'll send a new patch series this week because I'm developing a small feat
I've decided to start using the maint-scripts to make generating
>> a single for-next branch trivial.
>
> Thanks for that.
>
>> So, could you replace all of my -next branches you're pulling with:
>>
>> git://github.com/anholt/linux.git#for-next
>
> Don
On Tue, Jun 07, 2016 at 12:48:17PM +0800, Ye Xiaolong wrote:
> FYI, below is the comparison info between 3ed3a4f, 795ae7ay, v4.7-rc2 and the
> revert commit (eaa7f0d).
Thanks for running this.
Alas, I still can not make heads or tails of this, or reproduce it
locally for that matter.
With this t
This cleans up comments a bit to improve readability, adjusts the
name of the module after the source file renaming, and corrects the
MAINTAINERS for the upcoming lkdtm files.
Signed-off-by: Kees Cook
---
MAINTAINERS | 2 +-
drivers/misc/lkdtm_core.c | 12 ++--
2 files cha
Kbuild lacks a way to do in-place objcopy or other modifications of
built targets, so in order to move functions into non-text sections
without renaming the kernel module, the build of lkdtm must be split
into separate source files. This renames lkdtm.c to lkdtm_core.c in
preparation for adding the
This adds a function that lives in the .rodata section. The section
flags are corrected using objcopy since there is no way with gcc to
declare section flags in an architecture-agnostic way.
Signed-off-by: Kees Cook
---
drivers/misc/Makefile | 7 +++
drivers/misc/lkdtm.h| 6 +
Each direction of the atomic wrapping should be individually testable.
Signed-off-by: Kees Cook
---
drivers/misc/lkdtm_core.c | 26 --
1 file changed, 20 insertions(+), 6 deletions(-)
diff --git a/drivers/misc/lkdtm_core.c b/drivers/misc/lkdtm_core.c
index f212f865f9c6..
On 7 June 2016 at 15:57, Peter Griffin wrote:
> Hi Lee,
>
> On Tue, 07 Jun 2016, Lee Jones wrote:
>
>> On Tue, 07 Jun 2016, Peter Griffin wrote:
>>
>> > mmc_select_bus_width() returns bus width (4 or 8) on success or
>> > zero if unsupported. If bus width is set successfully we then wish
>> > to s
This adds test to detect copy_to_user/copy_from_user problems that are
protected by PAX_USERCOPY (and will be protected by HARDENED_USERCOPY).
Explicitly tests both "to" and "from" directions of heap object size
problems, heap object markings and, stack frame misalignment.
Signed-off-by: Kees Cook
On Tue, Jun 7, 2016 at 2:59 PM, Emese Revfy wrote:
> On Tue, 7 Jun 2016 13:59:53 -0700
> Kees Cook wrote:
>
>> >
>> > I applied the series to kbuild.git#kbuild now, sorry for the delay.
>>
>> Awesome! Thank you very much. I'll prepare the latent entropy plugin
>> for -next now too.
>
> I'll send
On Monday, May 16, 2016 05:11:11 PM Lv Zheng wrote:
> There is a facility in Linux, developers can manage GPE enabling/disabling
> through /sys/firmware/acpi/interrupts/gpexx. This is mainly for debugging
> purposes. Many users expect to use this facility to implement quirks to
> disable specific G
A dedicated workqueue has been used since the workqueue hws_wq with
workitem &cb->worker, is involved in hardware based sampling
on System z processors.
Since, these are long-running work items and aren't involved in memory
reclaim in any way, system_long_wq has been used.
Signed-off-by: Bhaktipr
From: Roman Volkov
Hi Arnd, Stephen,
This patch finally removes the warnings from GCC about possibly uninitialized
variables 'best_div2', 'best_div1', and 'best_mul'. Also one of the functions
is reworked, so that the algorithm is much easier. This is to continue the
work started in [1].
This c
This adds several new tests to lkdtm.
To test non-executability of .rodata, lkdtm's build method shifted
around a bit requiring a source file rename. But after some objcopy
magic, there is now an architecture-agnostic way to write functions
into .rodata.
The atomic under/overflow test was split s
From: Roman Volkov
PLL clock on WM8650 is calculated in the following way:
M * parent [O1] => / P [O2] => / D [O3]
Where O2 is 600MHz >= (M * parent) / P >= 300MHz.
Current algorithm does not met this requirement, so that the
function may return rates which are not supported by the hardware.
From: Arnd Bergmann
This fixes some false positive warnings we get with older compiler
versions:
clk-vt8500.c: In function ‘wm8650_find_pll_bits’:
clk-vt8500.c:430:12: ‘best_div2’ may be used uninitialized in this function
clk-vt8500.c:429:12: ‘best_div1’ may be used uninitialized in this functi
On Thursday 02 June 2016 12:41:42 Michał Kępień wrote:
> > Signed-off-by: Pali Rohár
>
> My guess is that Darren won't let you off without at least a short
> commit message.
I have no idea what else to write. I think that description is enough.
> > ---
> > drivers/platform/x86/dell-wmi.c | 3
On Thursday 02 June 2016 12:41:53 Michał Kępień wrote:
> I have one more entry to add here:
>
> { KE_IGNORE, 0xe06e, { KEY_RESERVED } },
>
> WMI event 0xe06e is emitted on a Vostro V131 when the Dell Support
> Center hotkey is pressed, along with an i8042 interrupt.
Ok, I will add it to this
2016-06-07 17:10 GMT-04:00 Lyude Paul :
> Managed to find someone in the office with one of these laptops and it looks
> like the adaptive keyboard works perfectly with this patch, so I can give my
> t-
> b:
>
> Tested-by: Lyude Paul
>
I can confirm it works too.
Tested-by: Marco Trevis
This patch adds a firmware check for the uPD720201K8-711-BAC-A
and uPD720202K8-711-BAA-A variant. Both of these chips are listed
in Renesas' R19UH0078EJ0500 Rev.5.00 "User's Manual: Hardware" as
devices which need a firmware in order to work as they do not have
support to load the firmware from an
On Tue, 7 Jun 2016, Oleg Nesterov wrote:
> On 06/06, David Rientjes wrote:
> >
> > > There is a potential race where we kill the oom disabled task which is
> > > highly unlikely but possible. It would happen if __set_oom_adj raced
> > > with select_bad_process and then it is OK to consider the old
Arnd Bergmann writes:
> On Friday, June 3, 2016 8:18:24 AM CEST Gerd Hoffmann wrote:
>> From: Eric Anholt
>>
>> Made with make defconfig; make menuconfig (only saying Y to new
>> entries); make savedefconfig.
>
> Please try not to mix 'make savedefconfig' changes with your
> own changes, it mak
On Tue, Jun 07, 2016 at 05:08:32PM -0400, Jon Mason wrote:
> Many users (and some applications) are expecting the CPU clock speed to
> be output in /proc/cpuinfo (as is done in x86, avr32, c6x, tile, parisc,
> ia64, and xtensa).
Such as what applications? This is just another meaningless number,
On 06/07/2016 11:30, Alexandre Belloni wrote:
> Hi,
>
> On 07/06/2016 at 16:18:31 +0100, David Binderman wrote :
>> Hello there,
>>
[snip]
>> Duplicate. Also in the same file:
>>
>> [drivers/rtc/rtc-ds1685.c:265]: (style) Variable 'ctrlb' is assigned a
>> value that is never used.
This looks li
On 06/07/2016 11:22 PM, Mauro Carvalho Chehab wrote:
Em Mon, 30 May 2016 20:29:14 +0800
Tiffany Lin escreveu:
==
Introduction
==
The purpose of this series is to add the driver for video codec hw embedded in
the Mediatek's MT8173 SoCs.
Mediatek Video Codec is able
On 06/07/2016 11:54 AM, Geert Uytterhoeven wrote:
Hi Daniel,
Hi Geert,
[ ... ]
Using "earlycon keep_bootcon" on koelsch (this doesn't help on arm64)
reveals it's stuck at:
clocksource_probe: no matching clocksources found
sched_clock: 32 bits at 100 Hz, resolution 1000ns, wrap
Add support for the PL330 DMA engine and the XMC form factor for
Broadcom Northstar Plus SoCs
Jon Mason (2):
ARM: dts: NSP: Add XMC board support
ARM: dts: NSP: Add PL330 support
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/bcm-nsp.dtsi | 17 ++
arch/arm/boot/dts/b
From: Jon Mason
Add PL330 support to the the Broadcom Northstar Plus device tree.
Signed-off-by: Jon Mason
---
arch/arm/boot/dts/bcm-nsp.dtsi | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm/boot/dts/bcm-nsp.dtsi b/arch/arm/boot/dts/bcm-nsp.dtsi
index 1759e65..8d
From: Jon Mason
The BCM958525XMC board is a smaller form factor typically used as
controller boards for switches. This smaller board has less devices
pinned out, so only a few need be populated in the device tree.
Signed-off-by: Jon Mason
---
arch/arm/boot/dts/Makefile | 1 +
arch/a
On Thursday 02 June 2016 12:42:11 Michał Kępień wrote:
> > -static void dell_wmi_process_key(int reported_key)
> > +static void dell_wmi_process_key(int type, int code)
> > {
> > const struct key_entry *key;
> >
> > key = sparse_keymap_entry_from_scancode(dell_wmi_input_dev,
> > -
From: kbuild test robot
Date: Sun, 5 Jun 2016 07:17:19 +0800
> net/rxrpc/rxkad.c:1165:1-3: WARNING: PTR_ERR_OR_ZERO can be used
>
>
> Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
>
> Generated by: scripts/coccinelle/api/ptr_ret.cocci
>
> CC: David Howells
> Signed-off-by: Fengg
On Fri, Jun 03, 2016 at 10:17:55AM -0500, Andrew F. Davis wrote:
> On 06/03/2016 09:14 AM, Laxman Dewangan wrote:
> >
> > On Friday 03 June 2016 06:59 PM, Guenter Roeck wrote:
> >> On 06/03/2016 03:06 AM, Jonathan Cameron wrote:
> >>> On 01/06/16 13:34, Laxman Dewangan wrote:
> The INA3221 is
+++ Petr Mladek [07/06/16 11:36 +0200]:
On Wed 2016-06-01 10:31:59, Miroslav Benes wrote:
Currently we do not allow patch module to unload since there is no
method to determine if a task is still running in the patched code.
The consistency model gives us the way because when the unpatching
fin
The theme of this series of patches is to try to allow running the eMMC
at 150 MHz on the rk3399 SoC, though the changes should still be correct
and have merit on their own. The motivation for running at 150 MHz is
that doing so improves signal integrity and (with some eMMC devices)
doesn't affect
In the the earlier change in this series ("Documentation: mmc:
sdhci-of-arasan: Add soc-ctl-syscon for corecfg regs") we can see the
mechansim for specifying a syscon to properly set corecfg registers in
sdhci-of-arasan. Now let's use this mechanism to properly set
corecfg_baseclkfreq on rk3399.
On rk3399 we'd like to be able to properly set corecfg registers in the
Arasan SDHCI component. Specify the syscon to enable that.
Signed-off-by: Douglas Anderson
---
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399
Hi,
[auto build test ERROR on spi/for-next]
[also build test ERROR on v4.7-rc2 next-20160607]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Vignesh-R/spi-Add-DMA-support-for-ti-qspi/20160607
As of an earlier change in this series ("Documentation: mmc:
sdhci-of-arasan: Add ability to export card clock") the SDHCI driver
used on Rockchip SoCs can now expose its clock. Let's now specify that
the PHY can use it.
Letting the PHY get access to this clock means it can adjust
phyctrl_frqsel
Previous changes in this series allowed exposing the card clock from the
rk3399 SDHCI device and allowed consuming the card clock in the rk3399
eMMC PHY. Hook things up in the main rk3399 dtsi file.
Signed-off-by: Douglas Anderson
---
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 4
1 file ch
Some SD/eMMC PHYs (like the PHY from Arasan that is designed to work
with arasan,sdhci-5.1) need to know the card clock in order to function
properly. Let's expose this clock using a standard device tree
mechanism so that the PHY can get access to and query the card clock.
Signed-off-by: Douglas
There's no reason to store the return value of rockchip_emmc_phy_power()
in a variable nor to check it. Just return it.
Signed-off-by: Douglas Anderson
---
drivers/phy/phy-rockchip-emmc.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/drivers/phy/phy-rockchip-emmc.c
On Tue, Jun 07, 2016 at 10:07:40AM +, Po Liu wrote:
> Hi Bjorn,
>
> > -Original Message-
> >
> > On Mon, Jun 06, 2016 at 10:01:44AM -0400, Murali Karicheri wrote:
> > > On 06/06/2016 03:32 AM, Po Liu wrote:
> > > > Hi Bjorn,
> > > > I confirm we met same problem with KeyStone ba
The "phyctrl_frqsel" is described in the Arasan datasheet [1] as "the
frequency range of DLL operation". Although the Rockchip variant of
this PHY has different ranges than the reference Arasan PHY it appears
as if the functionality is similar. We should set this phyctrl field
properly.
Note: as
Some SD/eMMC PHYs (like the PHY from Arasan that is designed to work
with arasan,sdhci-5.1) need to know the card clock in order to function
properly. Let's add the ability to expose this clock. Any PHY that
needs to know the clock rate can add a reference and query the clock
rate.
At the moment
In commit 802ac39a5566 ("mmc: sdhci-of-arasan: fix set_clock when a phy
is supported") we added code to power the PHY off and on whenever the
clock was changed but we avoided doing the power cycle code when the
clock was low speed. Let's now do it always.
Although there may be other reasons for p
Previous PHY code waited a fixed amount of time for the DLL to lock at
power on time. Unfortunately, the time for the DLL to lock is actually
a bit more dynamic and can be longer if the card clock is slower.
Instead of waiting a fixed 30 us, let's now dynamically wait until the
lock bit gets set.
As can be seen in Arasan's datasheet [1] there are several "corecfg"
settings in their SDHCI IP Block that are supposed to be controlled by
software. Although the datasheet referenced is a bit vague about how to
access corecfg, in Figure 5 you can see that for Arasan's PHY (a
separate component th
On Tue, Jun 07, 2016 at 07:02:23PM +0530, Naveen N. Rao wrote:
> PPC64 eBPF JIT compiler.
>
> Enable with:
> echo 1 > /proc/sys/net/core/bpf_jit_enable
> or
> echo 2 > /proc/sys/net/core/bpf_jit_enable
>
> ... to see the generated JIT code. This can further be processed with
> tools/net/bpf_jit_d
From: Zhao Qiang
Date: Mon, 6 Jun 2016 14:30:00 +0800
> Signed-off-by: Zhao Qiang
Applied.
From: Zhao Qiang
Date: Mon, 6 Jun 2016 14:30:01 +0800
> QE has module to support TDM, some other protocols
> supported by QE are based on TDM.
> add a qe-tdm lib, this lib provides functions to the protocols
> using TDM to configurate QE-TDM.
>
> Signed-off-by: Zhao Qiang
Applied.
From: Zhao Qiang
Date: Mon, 6 Jun 2016 14:29:59 +0800
> Add tdm clock configuration in both qe clock system and ucc
> fast controller.
>
> Signed-off-by: Zhao Qiang
Applied.
From: Zhao Qiang
Date: Mon, 6 Jun 2016 14:30:02 +0800
> The driver add hdlc support for Freescale QUICC Engine.
> It support NMSI and TSA mode.
>
> Signed-off-by: Zhao Qiang
Applied.
From: Zhao Qiang
Date: Mon, 6 Jun 2016 14:29:58 +0800
> Rx_sync and tx_sync are used by QE-TDM mode,
> add them to struct ucc_fast_info.
>
> Signed-off-by: Zhao Qiang
Applied.
On Tue, Jun 07, 2016 at 11:18:10PM +0100, Russell King - ARM Linux wrote:
> On Tue, Jun 07, 2016 at 05:08:32PM -0400, Jon Mason wrote:
> > Many users (and some applications) are expecting the CPU clock speed to
> > be output in /proc/cpuinfo (as is done in x86, avr32, c6x, tile, parisc,
> > ia64, a
On Tue, Jun 07, 2016 at 09:39:55AM -0500, Dan Williams wrote:
> On Tue, 2016-06-07 at 13:30 +0400, Pavel Andrianov wrote:
> > Hi!
> >
> > There is a potential race condition in
> > drivers/net/wireless/libertas/libertas.ko.
> > In the function lbs_hard_start_xmit(..), line 159, a socket buffer
>
On Friday 27 May 2016 00:04:23 Gabriele Mazzotta wrote:
> On 22/05/2016 13:36, Pali Rohár wrote:
> > ACPI DSDT tables have defined other WMI codes, but does not contain any
> > description when those codes are emitted. Some other codes can be found in
> > logs on internet. In this patch are all whi
From: John Crispin
Date: Mon, 6 Jun 2016 08:43:13 +0200
> i think one solution would be to add some code to have 2 devices share
> the same dql instance. would that be an acceptable solution ?
You still need to address the issue of synchronization.
dql purposefully doesn't use locking, always b
The req_canceled() callback is used by tpm_transmit() periodically to
check whether the request has been canceled while it is receiving a
response from the TPM.
The TPM_CRB_CTRL_CANCEL register was cleared already in the crb_cancel
callback, which has two consequences:
* Cancel might not happen.
wmb()'s are not needed as iowrite32() is used.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm_crb.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/char/tpm/tpm_crb.c b/drivers/char/tpm/tpm_crb.c
index b4d46ae..ca2cad9 100644
--- a/drivers/char/tpm/tpm_crb.c
+++ b/drivers/
The register TPM_CRB_CTRL_REQ_0 contains bits goIdle and cmdReady for
invoking the chip to suspend and resume. This commit implements runtime
PM for tpm_crb by using these bits.
The legacy ACPI start (SMI + DMA) based devices do not support these
bits. Thus this functionality only is enabled only
Support for runtime PM with TPM2 CRB chips such as PTT in Skylake.
Jarkko Sakkinen (3):
tpm_crb: fix crb_req_canceled behavior
tpm, tpm_crb: remove wmb()'s
tpm, tpm_crb: runtime power management
drivers/char/tpm/tpm-interface.c | 3 ++
drivers/char/tpm/tpm_crb.c | 72 +++
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
tags/clk-fixes-for-linus
for you to fetch changes up to 72ad679aa7182d2
On 06/07, Charanya Venkatraman wrote:
> Avoid data corruption issues that result in CRC errors during file
> transfers over serial ports at higher baud rates.
>
> The current msm_serial driver masks the FIFO Rx interrupts in
> msm_start_rx_dma() since Rx FIFO interrupts are not required in DMA
> m
Hi Eric,
On Tue, 07 Jun 2016 14:56:10 -0700 Eric Anholt wrote:
>
> In next-20160607 I see drm-vc4-next merged separately, which I also
> included in for-next. I think it would be best to drop that one, too.
OK, I was assuming that it was being merged via the drm tree. I will
drop
* branchperf/core -> FETCH_HEAD
Already up-to-date.
And then nothing changed, I didn't also find new commits
and new tag 'perf-core-for-mingo-20160607'.
However, if using tag perf-core-for-mingo-20160607,
I can get new commits from your repository as below.
# git fetch
Hi Tomasz,
On Mon, May 30, 2016 at 05:14:13PM +0200, Tomasz Nowicki wrote:
> From the functionality point of view this series may be split into the
> following logic parts:
> 1. Export ECAM API and add parent device to pci_config_window
> 2. Add IO resources handling to PCI core code
> 3. Support
From: Colin King
Date: Mon, 6 Jun 2016 09:21:44 +0100
> From: Colin Ian King
>
> trivial fix to spelling mistakes and add missing newline in pr_err
> messages
>
> Signed-off-by: Colin Ian King
Applied.
At 2016-06-08 03:12:08, "James Bottomley"
wrote:
>On Wed, 2016-06-08 at 02:00 +0800, Tiezhu Yang wrote:
>> There exists potential memory leak in ufshcd_parse_clock_info(),
>> this patch fixes it.
>
>What makes you think there's a leak here? These are all devm_
>allocations, so they're all freed
On Tue, Jun 7, 2016 at 4:01 PM, David Miller wrote:
> From: John Crispin
> Date: Mon, 6 Jun 2016 08:43:13 +0200
>
>> i think one solution would be to add some code to have 2 devices share
>> the same dql instance. would that be an acceptable solution ?
>
> You still need to address the issue of s
On Tue, Jun 7, 2016 at 8:27 AM, Ming Lin wrote:
> On Tue, Jun 7, 2016 at 7:57 AM, Keith Busch wrote:
>> On Mon, Jun 06, 2016 at 11:21:52PM +0200, Christoph Hellwig wrote:
>>> +struct request *blk_mq_alloc_request_hctx(struct request_queue *q, int rw,
>>> + unsigned int flags, unsigned
If the function ufshcd_parse_clock_info returns an error, the memory clkfreq
allocated by devm_kzalloc will be freed at that time. But when the function
ufshcd_parse_clock_info returns 0 on success, there exists potential memory
leak, this patch fixes it.
Signed-off-by: Tiezhu Yang
---
drivers/s
Hi,
[auto build test ERROR on s390/features]
[also build test ERROR on v4.7-rc2 next-20160607]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Bhaktipriya-Shridhar/s390-oprofile-Remove
Remove open-coded uses of set instructions to use CC_SET()/CC_OUT() in
arch/x86/boot/boot.h.
Signed-off-by: H. Peter Anvin
---
arch/x86/boot/boot.h | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/arch/x86/boot/boot.h b/arch/x86/boot/boot.h
index 2edb2d5..7c1495f 1006
From: "H. Peter Anvin"
Remove open-coded uses of set instructions to use CC_SET()/CC_OUT() in
.
Signed-off-by: H. Peter Anvin
---
arch/x86/include/asm/bitops.h | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/arch/x86/include/asm/bitops.h b/arch/x86/include/
The Denx MA5D4 dts doesn't properly define the slow_xtal and main_xtal
frequencies, the PMC then has to fallback to using the RC oscillators whose
precision is not really good.
As both crystals are populated, define their frequencies, see p17 of
http://www.denx-cs.de/sites/all/files/MA5D4.HWM_.002
From: "H. Peter Anvin"
Use SETC instead of SBB to return the value of CF from assembly. Using
SETcc enables uniformity with other flags-returning pieces of assembly
code.
Signed-off-by: H. Peter Anvin
---
arch/x86/include/asm/bitops.h | 24
arch/x86/include/asm/pe
From: "H. Peter Anvin"
Remove open-coded uses of set instructions to use CC_SET()/CC_OUT() in
.
Signed-off-by: H. Peter Anvin
---
arch/x86/include/asm/percpu.h | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/arch/x86/include/asm/percpu.h b/arch/x86/include/asm/perc
Hi Andrew,
On Tue, 7 Jun 2016 13:12:42 -0700 Andrew Morton
wrote:
>
> On Mon, 6 Jun 2016 22:11:37 -0700 Randy Dunlap wrote:
>
> > On 06/05/16 21:20, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Changes since 20160603:
> > >
> >
> > on i386:
> >
> > mm/built-in.o: In function `init
From: "H. Peter Anvin"
Change the lexical defintion of the GEN_*_RMWcc() macros to not take
the condition code as a quoted string. This will help support
changing them to use the new __GCC_ASM_FLAG_OUTPUTS__ feature in a
subsequent patch.
Signed-off-by: H. Peter Anvin
---
arch/x86/include/asm
From: "H. Peter Anvin"
Remove open-coded uses of set instructions to use CC_SET()/CC_OUT() in
.
Signed-off-by: H. Peter Anvin
---
arch/x86/include/asm/rwsem.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/include/asm/rwsem.h b/arch/x86/include/asm/rwsem.h
ind
Signed-off-by: Pali Rohár
Tested-by: Michał Kępień
---
drivers/platform/x86/dell-wmi.c | 29 -
1 file changed, 16 insertions(+), 13 deletions(-)
diff --git a/drivers/platform/x86/dell-wmi.c b/drivers/platform/x86/dell-wmi.c
index 4d23c91..6750604 100644
--- a/drive
Hi,
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on v4.7-rc2 next-20160607]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Kees-Cook/lkdtm-add-usercopy-and
>From Dell we know that WMI event code 0xe045 is for Num Lock key, but it is
unclear due to message in commit 0b3f6109f0c9 ("dell-wmi: new driver for
hotkey control").
Signed-off-by: Pali Rohár
Tested-by: Michał Kępień
Cc: Matthew Garrett
Cc: Mario Limonciello
Link: https://lkml.org/lkml/2015/
First patch describe problem about 0xe045 code. Second and third are just
cosmetic and last rework code which processing WMI events. It should be
properly tested on more Dell machines, to check that everything is still
working correctly.
Changes since v1:
* Fixed comments
* Fixed memory leak
* Add
This patch unify procedure for generating sparse keymap and unify also big
switch code for processing WMI events of different types. After this patch
dell-wmi driver does not differ between "old" and "new" hotkey type.
It construct sparse keymap table with all WMI codes. It is because on some
lapt
901 - 1000 of 1210 matches
Mail list logo
