The RTL8153-AD supports a persistent system specific MAC address.
This means a device plugged into two different systems with host side
support will show different (but persistent) MAC addresses.
This information for the system's persistent MAC address is burned in when
the system HW is built and
asm-generic headers are generic implementations for architecture specific
code and should not be included by common code. Thus use the asm/ version
of sections.h to get at the linker sections.
Signed-off-by: Christoph Hellwig
---
kernel/kprobes.c | 2 +-
1 file changed, 1 insertion(+), 1 deleti
Hi,
> -Original Message-
> From: Pan, Jacob jun
> Sent: Tuesday, July 12, 2016 5:19 AM
> To: Ingo Molnar
> Cc: Chen, Yu C; 'Len Brown'; Jacob Pan; H. Peter Anvin; Peter Zijlstra;
> x...@kernel.org; linux-kernel@vger.kernel.org; Pan, Jacob jun
> Subject: Re: Hi, Ingo, would you please help
asm-generic headers are generic implementations for architecture specific
code and should not be included by common code. Thus use the asm/ version
of sections.h to get at the linker sections.
Signed-off-by: Christoph Hellwig
---
kernel/printk/printk.c | 2 +-
1 file changed, 1 insertion(+), 1
On Sun, Jul 10, 2016 at 08:28:37PM -0700, Tony Luck wrote:
>I'm very surprised that there was a BERT table on an Atom machine. More
>details about the machine please. Also BIOS version.
Hi, ying
Could you tell me what's BERT table? and how to check the BIOS version?
Thanks,
Xiaolong
>
>Sent fr
So don't mention it.
Signed-off-by: Christoph Hellwig
---
Documentation/DMA-API-HOWTO.txt | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/Documentation/DMA-API-HOWTO.txt b/Documentation/DMA-API-HOWTO.txt
index 781024e..494ffac 100644
--- a/Documentation/DMA-API-HOWTO.tx
On Mon, Jul 11, 2016 at 05:15:04PM -0700, Chunwei Chen wrote:
> We need to check i_count again with i_lock held, because iput might re-add
> i_count when lazytime is on. Without this check, we could end up with
> double-free or use-after-free.
Details, please. Ideally - with a reproducer. Who is
Hi,
On 07/11/2016 08:57 PM, Pengcheng Li wrote:
> A usb device in the connection state. Then host is suspend and resume.
> But the usb device could not be at the right speed. We should be reset
> the reset.
Have you tried applying XHCI_RESET_ON_RESUME quirk to your
host controller driver? Is your
On Mon, Jul 11, 2016 at 01:34:08PM +0200, Benjamin Tissoires wrote:
> On Fri, Jul 8, 2016 at 7:51 PM, Dmitry Torokhov
> wrote:
> > On Fri, Jul 08, 2016 at 11:17:39AM +0200, Benjamin Tissoires wrote:
> >> Hi,
> >>
> >> On Thu, Jul 7, 2016 at 9:11 AM, Lv Zheng wrote:
> >> > There are many AML table
On 07/11/2016 11:08 PM, Stephen Boyd wrote:
Add the call to of_clk_set_defaults() into the amba probe path so
that devices on the amba bus can use the assigned rates and
parents feature of the common clock framework.
Cc: Michael Turquette
Cc: Jorge Ramirez Ortiz
Signed-off-by: Stephen Boyd
During scsi command queueing or exception handling, if prepairing
fails, we need to reclaim the failed request. Otherwise, the garbage
request will be pushed into the ring for the backend to work.
Signed-off-by: Bin Wu
---
drivers/scsi/xen-scsifront.c | 4 ++--
1 file changed, 2 insertions(+), 2
On 2016/7/11 17:53, Juergen Gross wrote:
On 11/07/16 11:50, David Vrabel wrote:
On 11/07/16 10:33, Juergen Gross wrote:
On 11/07/16 04:51, Bin Wu wrote:
During scsi command queueing, if mapping data fails, we need to
reclaim the failed request. Otherwise, the garbage request will
be pushed int
This patch adds the APM X-Gene hwmon device tree node documentation.
Signed-off-by: Hoan Tran
---
.../devicetree/bindings/hwmon/apm-xgene-hwmon.txt | 14 ++
1 file changed, 14 insertions(+)
create mode 100644 Documentation/devicetree/bindings/hwmon/apm-xgene-hwmon.txt
diff
This patch adds hardware temperature and power reading support for
APM X-Gene SoC using the mailbox communication interface.
Signed-off-by: Hoan Tran
---
Documentation/hwmon/xgene-hwmon | 30 ++
drivers/hwmon/Kconfig | 7 +
drivers/hwmon/Makefile | 1 +
drivers/hwmon/xgen
This patch adds DT node to enable hwmon driver for APM X-Gene SoC.
Signed-off-by: Hoan Tran
---
arch/arm64/boot/dts/apm/apm-shadowcat.dtsi | 5 +
arch/arm64/boot/dts/apm/apm-storm.dtsi | 5 +
2 files changed, 10 insertions(+)
diff --git a/arch/arm64/boot/dts/apm/apm-shadowcat.dtsi
This patch set adds hardware temperature and power reading support for
APM X-Gene SoC using the mailbox communication interface.
For device tree, it is the standard DT mailbox.
For ACPI, it is the PCC mailbox.
For ACPI, tested with this patch[1] which supports PCC subspace 2
[1] http://www.spinic
Remove void function return statement
Signed-off-by: Shuah Khan
---
drivers/media/platform/s5p-mfc/s5p_mfc.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/media/platform/s5p-mfc/s5p_mfc.c
b/drivers/media/platform/s5p-mfc/s5p_mfc.c
index c96421f..b6fde20 100644
--- a/drivers/media/p
Fixes: 8112c4f140fa ("seccomp: remove 2-phase API")
Signed-off-by: Mickaël Salaün
Cc: Kees Cook
Cc: Andy Lutomirski
Cc: James Morris
---
arch/Kconfig | 11 ---
1 file changed, 11 deletions(-)
diff --git a/arch/Kconfig b/arch/Kconfig
index d794384a0404..96e434638767 100644
--- a/arch/
Colin King writes:
> From: Colin Ian King
>
> At the current point where ret is being checked for non-zero it has
> not changed since it was initialized to zero, hence the check and the
> label unref are redundant and can be removed.
Reviewed-by: Eric Anholt
I'll put this in my next pull requ
We need to check i_count again with i_lock held, because iput might re-add
i_count when lazytime is on. Without this check, we could end up with
double-free or use-after-free.
Cc: Alexander Viro
Cc: linux-fsde...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: sta...@vger.kernel.org
Signed-o
On 7/3/2016 8:20 PM, Paul Gortmaker wrote:
The Kconfig currently controlling compilation of this code is:
config PNPBIOS
bool "Plug and Play BIOS support"
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of modularity, so that when r
Hi Steve,
On Mon, Jul 11, 2016 at 12:55:22PM -0400, Steven Rostedt wrote:
> On Fri, 8 Jul 2016 14:56:12 +0900
> Namhyung Kim wrote:
>
> > When a task was migrated to other cpu in the middle of a function, the
> > fgraph_exit record will be in a different cpu than the enter record.
> > But curre
+Kishon,
On 05/27/2016 12:57 PM, Al Cooper wrote:
> Add a new USB Phy driver for Broadcom STB SoCs. This driver
> supports all Broadcom STB ARM SoCs. This driver in combination
> with the generic ohci, ehci and xhci platform drivers will enable
> USB1.1, USB2.0 and USB3.0 support. This Phy driver
Hi,
[auto build test WARNING on net-next/master]
[also build test WARNING on v4.7-rc7 next-20160711]
[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/Yeshaswi-M-R-Gowda/crypto-chcr-Add-Chelsio
On 05/27/2016 12:57 PM, Al Cooper wrote:
> Signed-off-by: Al Cooper
> ---
> drivers/soc/brcmstb/common.c| 12
> include/linux/soc/brcmstb/brcmstb.h | 10 ++
> 2 files changed, 22 insertions(+)
>
> diff --git a/drivers/soc/brcmstb/common.c b/drivers/soc/brcmstb/common
On Wed, Jul 06, 2016 at 10:57:19AM +0200, Linus Walleij wrote:
> > + gpiochip_irqchip_add(&wg->chip, &wcove_irqchip, 0,
> > +handle_simple_irq, IRQ_TYPE_NONE);
>
> Reexamine the use of handle_simple_irq() here. We have two kinds of
> irq hardware: those with one r
This patch introduces a separate GPIO driver for Intel WhiskeyCove PMIC.
This driver is based on gpio-crystalcove.c.
Signed-off-by: Ajay Thomas
Signed-off-by: Bin Gao
---
Changes in v5:
- Revisited the interrupt handler code to iterate until all pending
interrupts are handled. This change is
Hi Vivek,
On Mon, 11 Jul 2016 09:40:04 -0400 Vivek Goyal wrote:
>
> On Sat, Jul 09, 2016 at 01:41:38AM +0800, kbuild test robot wrote:
> > Hi,
> >
> > [auto build test ERROR on next-20160708]
> > [also build test ERROR on v4.7-rc6]
> > [cannot apply to pcmoore-selinux/next security/next v4.7-rc6
Hi all,
Today's linux-next merge of the tegra tree got a conflict in:
arch/arm64/configs/defconfig
between commit:
426f754be0bc ("arm64: defconfig: Enable more IP blocks for Exynos7 and
Exynos5433")
from the samsung-krzk tree and commit:
10a7b37b5b96 ("arm64: Update default configurati
The SUN_TOP_CTRL_FAMILY_ID register is at a fixed absolute address for
all of our supported chips, so utilize its value to determine what the
UARTA base address should be based on the value we read.
Since the code is called both during decompressor when the MMU is off,
and after the MMU has been
On 06/29/2016 12:49 PM, Markus Mayer wrote:
> From: Florian Fainelli
>
> Add an ARCH_BRCMSTB Kconfig symbol which allows us not to update the
> dependencies for all STB-related drivers. Select BRCMSTB_L2_IRQ and
> GENERIC_IRQ_CHIP which are required for proper functioning.
>
> Signed-off-by: Dou
Thank you very much, Mark!
In linux-nvdimm list, Dan Williams posted patch series which introduced
nvdimm_flush() and nvdimm_has_flush()
which assumes ARS(Asynchronous DRAM Refresh) feature or using Flush Hint in
NFIT to get persistency.
And.. arch_wmb_pmem() has been killed in the patch.
Wit
Hi Paulo,
On Mon, 11 Jul 2016 16:07:39 -0300 Paulo Flabiano Smorigo
wrote:
>
> diff --git a/drivers/crypto/vmx/aesp8-ppc.pl b/drivers/crypto/vmx/aesp8-ppc.pl
> index 2280539..813ffcc 100644
> --- a/drivers/crypto/vmx/aesp8-ppc.pl
> +++ b/drivers/crypto/vmx/aesp8-ppc.pl
> @@ -1,4 +1,11 @@
> -#!/u
Update the syscall number after earch PTRACE_SETREGS on ORIG_*AX.
This is needed to get the potentially altered syscall number in the
seccomp filters after RET_TRACE.
This fix four seccomp_bpf tests:
> [ RUN ] TRACE_syscall.skip_after_RET_TRACE
> seccomp_bpf.c:1560:TRACE_syscall.skip_after_R
On Thu, Jul 07, 2016 at 09:42:32AM +0200, Peter Zijlstra wrote:
> On Thu, Jul 07, 2016 at 11:20:36AM +1200, Campbell Steven wrote:
>
> > > commit 8974189222159154c55f24ddad33e3613960521a
> > > Author: Peter Zijlstra
> > > Date: Thu Jun 16 10:50:40 2016 +0200
>
> > Since these early reports fro
On Mon, Jul 11, 2016 at 10:07:31AM +, Nava kishore Manne wrote:
> Ping!!
>
> This email and any attachments are intended for the sole use of the named
> recipient(s) and contain(s) confidential information that may be proprietary,
> privileged or copyrighted under applicable law. If you a
On Sat, Jul 09, 2016 at 08:19:15PM +0200, Mickaël Salaün wrote:
> Fixes: a1db74209483 ("module: replace copy_module_from_fd with kernel
> version")
It's not a "fix", it's a "cleanup remaining bits"
On Mon, Jul 11, 2016 at 02:22:09PM +0200, Jean Delvare wrote:
> Hi Viresh,
>
> On Wed, 6 Jul 2016 13:55:40 -0700, Viresh Kumar wrote:
> > On 06-07-16, 19:12, Jean Delvare wrote:
> > > Well well... I don't like this patch at all to be honest.
> >
> > Sure, I didn't like it much as well. I just wan
The only place the values of free_node_ptr and max_size are read is in
befs_dump_index_entry(), which both times it is called, it is passed the on
disk superblock. Removing assignment of unused values.
Signed-off-by: Luis de Bethencourt
---
Hi,
Noticed this when reading befs' btree code.
Thanks
Fixing a grammatical error in the documentation.
Signed-off-by: Luis de Bethencourt
---
Hi,
Since befs_bt_read_node() calls befs_read_datastream(), and was touched
in the first commit of the series I decided to send a fix for the
grammatical error I had noticed there a while ago.
Thanks for all
befs_read_datastream() is used to read the inode from the disk, off is
meant to provide the offset of the data in the buffer head. But the only
function using this argument already knows the starting offset of the node,
so this argument isn't needed.
Signed-off-by: Luis de Bethencourt
---
Hi,
I
On Thu, 30 Jun 2016, Joonsoo Kim wrote:
> We need to find a root cause of this problem, first.
>
> I guess that this problem would happen when isolate_freepages_block()
> early stop due to watermark check (if your patch is applied to your
> kernel). If scanner meets, cached pfn will be reset and
On Jul 10, 2016, at 9:03 PM, Al Viro wrote:
> On Mon, Jul 11, 2016 at 02:01:13AM +0100, Al Viro wrote:
>> On Sun, Jul 10, 2016 at 07:14:18PM +0100, James Simmons wrote:
>>
>>> [ 111.210818] [] kiblnd_send+0x51d/0x9e0 [ko2iblnd]
>>
>> Mea culpa - in kiblnd_send() this
>>if (payload_kio
On Mon, Jul 11, 2016 at 02:50:07PM -0700, Stephen Boyd wrote:
> The voltage ranges listed here are wrong. The correct ranges can
> be seen in the "native" spmi regulator driver
> qcom_spmi-regulator.c at pldo_ranges[], ftsmps_ranges[] and
> boost_ranges[] for the pldo, ftsmps, and boost type regula
On 12-07-16, 00:44, Rafael J. Wysocki wrote:
> On Monday, July 11, 2016 03:35:01 PM Viresh Kumar wrote:
> > Hi Sergey and Jan,
> >
> > On 12-07-16, 00:44, Sergey Senozhatsky wrote:
> > > right. apart from cases when the existing console_unlock() behaviour can
> > > simply "block" a process to flus
On 9 July 2016 at 08:30, Markus Mayer wrote:
> On 9 July 2016 at 05:04, Luis de Bethencourt wrote:
>> On 08/07/16 23:43, Markus Mayer wrote:
>>> Add a collection of generic functions to convert strings to lowercase
>>> or uppercase.
>>>
>>> Changing the case of a string (with or without copying i
On Monday, July 11, 2016 03:35:01 PM Viresh Kumar wrote:
> Hi Sergey and Jan,
>
> On 12-07-16, 00:44, Sergey Senozhatsky wrote:
> > right. apart from cases when the existing console_unlock() behaviour can
> > simply "block" a process to flush the log_buf to slow serial consoles
> > (regardless the
On Mon, Jul 11, 2016 at 02:50:09PM -0700, Stephen Boyd wrote:
> The pm8x41_hfsmps ranges overlap. The first range is from 375000
> to 1562500:
>
> 375000 + (95 * 12500) == 1562500
>
> and the second range starts at 155. Interestingly, the second
> range ends at the correct value when it's se
Fix misspelled error message and existing checkpatch errors in the
error message conditional.
WARNING: suspect code indent for conditional statements (8, 24)
if (ctx->state != MFCINST_HEAD_PARSED &&
[...]
+ mfc_err("Can not get crop information\n");
Signed-off-by: Shuah Khan
On Mon, Jul 11, 2016 at 02:50:08PM -0700, Stephen Boyd wrote:
> The voltage ranges listed here are wrong. The pma8084 pldo
> supports three different overlapping voltage ranges with
> differing step sizes and the pma8084 ftsmps supports two. These
> ranges can be seen in the "native" spmi regulator
Hi Dmitry,
> T: Bus=01 Lev=01 Prnt=01 Port=07 Cnt=05 Dev#= 5 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=13d3 ProdID=3490 Rev=00.01
> C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
> I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> I: If#= 1 A
T: Bus=01 Lev=01 Prnt=01 Port=07 Cnt=05 Dev#= 5 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=13d3 ProdID=3490 Rev=00.01
C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlc
Hi Sergey and Jan,
On 12-07-16, 00:44, Sergey Senozhatsky wrote:
> right. apart from cases when the existing console_unlock() behaviour can
> simply "block" a process to flush the log_buf to slow serial consoles
> (regardless the process execution context) and make the system less
> responsive, I
Hi,
This series fix the recent seccomp update for the User-mode Linux architecture
(32-bit and 64-bit) since commit 26703c636c1f3272b39bd0f6d04d2e970984f1b6
(close the hole where ptrace can change a syscall out from under seccomp).
Regards,
Mickaël Salaün (3):
um/ptrace: Fix the syscall_trace_
Keep the same semantic as before the commit 26703c636c1f: deallocate
audit context and fake a proper syscall exit.
This fix a kernel panic triggered by the seccomp_bpf test:
> [ RUN ] global.ERRNO_valid
> BUG: failure at kernel/auditsc.c:1504/__audit_syscall_entry()!
> Kernel panic - not sync
On Wed, 29 Jun 2016 13:42:12 +0800 "Hillf Danton"
wrote:
> To avoid excessive reclaim, we give up rebalancing for high order
> allocations right after reclaiming enough pages.
hm. What are the observed runtime effects of this change? Any testing
results?
Quoting Franklin S Cooper Jr (2016-05-03 08:56:47)
> Add tblck to the pwm nodes. This insures that the ehrpwm driver has access
s/tblck/tbclk/
I see you have acks already. What tree should this patch go through?
Regards,
Mike
> to the time-based clk.
>
> Do not remove similar entries for ehrpw
The Kconfig for this file is:
drivers/acpi/Kconfig:config ACPI_PCI_SLOT
drivers/acpi/Kconfig: bool "PCI slot detection driver"
...and so it is not built as a module. Hence including module.h
and everything that comes with it just for the no-op MODULE_LICENSE
and friends is rather heavy handed.
PowerVM seems to only ever provide a single hotplug slot per PHB.
The under lying slot hotplug registration code assumed multiple slots,
but the actual implementation is broken for multiple slots. This went
unnoticed for years due to the nature of PowerVM as mentioned
previously. Under qemu/kvm the
Quoting Wan Zongshun (2016-07-10 00:27:24)
> diff --git a/drivers/clk/nuc900/clk-apll.c b/drivers/clk/nuc900/clk-apll.c
> new file mode 100644
> index 000..a05aec7
> --- /dev/null
> +++ b/drivers/clk/nuc900/clk-apll.c
> @@ -0,0 +1,168 @@
> +/*
> + * Copyright 2016 Wan Zongshun
> + *
> + * The
Topi Miettinen writes:
> There are many basic ways to control processes, including capabilities,
> cgroups and resource limits. However, there are far fewer ways to find
> out useful values for the limits, except blind trial and error.
>
> Currently, there is no way to know which capabilities are
On 10 July 2016 at 22:32, Peter Chen wrote:
> On Thu, Jul 07, 2016 at 03:21:09PM -0700, Stephen Boyd wrote:
>> @@ -40,11 +43,38 @@ struct ci_hdrc_msm {
>> struct clk *iface_clk;
>> struct clk *fs_clk;
>> struct ci_hdrc_platform_data pdata;
>> + struct reset_controller_dev rcd
The Kconfig currently controlling compilation of these files are:
drivers/acpi/Kconfig:menuconfig PMIC_OPREGION
drivers/acpi/Kconfig: bool "PMIC (Power Management Integrated Circuit)
operation region support"
drivers/acpi/Kconfig:config BXT_WC_PMIC_OPREGION
drivers/acpi/Kconfig: bool "ACPI o
From:
Date: Mon, 11 Jul 2016 21:54:07 +
> Please let me know what else can be done for this patch to make it
> acceptable so we can have parity for Linux.
Just resubmit it and I'll apply it, I'm so tired of hearing about this...
On 10 July 2016 at 21:43, Peter Chen wrote:
> On Thu, Jul 07, 2016 at 03:21:06PM -0700, Stephen Boyd wrote:
>> diff --git a/drivers/usb/chipidea/ci_hdrc_msm.c
>> b/drivers/usb/chipidea/ci_hdrc_msm.c
>> index 7e870a253f55..7708bee3ff3e 100644
>> --- a/drivers/usb/chipidea/ci_hdrc_msm.c
>> +++ b/dr
On 10 July 2016 at 20:10, Peter Chen wrote:
> On Thu, Jul 07, 2016 at 03:21:01PM -0700, Stephen Boyd wrote:
>> @@ -418,6 +427,17 @@ static inline bool ci_otg_is_fsm_mode(struct ci_hdrc
>> *ci)
>> #endif
>> }
>>
>> +#if IS_ENABLED(CONFIG_USB_CHIPIDEA_ULPI)
>> +int ci_ulpi_init(struct ci_hdrc *ci
Since the watermark calculations for Skylake are still broken, we're apt
to hitting underruns very easily under multi-monitor configurations.
While it would be lovely if this was fixed, it's not. Another problem
that's been coming from this however, is the mysterious issue of
underruns causing full
+++ Miroslav Benes [11/07/16 16:03 +0200]:
On Mon, 27 Jun 2016, Torsten Duwe wrote:
diff --git a/arch/arm64/include/asm/livepatch.h
b/arch/arm64/include/asm/livepatch.h
new file mode 100644
index 000..6b9a3d1
--- /dev/null
+++ b/arch/arm64/include/asm/livepatch.h
@@ -0,0 +1,37 @@
+/*
+ * l
On Fri, 2016-07-08 at 12:37 +0100, Suzuki K Poulose wrote:
> On systems with mismatched i/d cache min line sizes, we need to use
> the smallest size possible across all CPUs. This will be done by fetching
> the system wide safe value from CPU feature infrastructure.
> However the some special users
> David,
>
> Did you have any more thoughts about this? I'm happy to make some other
> adjustments to the patch, if you have some recommendations.
Hi,
I just wanted to share that the maintenance BIOSes released for the Dell
platforms with Type-C this past week enables the MAC address pass
thr
The voltage ranges listed here are wrong. The pma8084 pldo
supports three different overlapping voltage ranges with
differing step sizes and the pma8084 ftsmps supports two. These
ranges can be seen in the "native" spmi regulator driver
(qcom_spmi-regulator.c) at pldo_ranges[] and ftsmps_ranges[]
r
The pm8x41_hfsmps ranges overlap. The first range is from 375000
to 1562500:
375000 + (95 * 12500) == 1562500
and the second range starts at 155. Interestingly, the second
range ends at the correct value when it's set to be the
appropriate start value, 1575000:
1575000 + ((158 - 96) * 2500
The voltage ranges listed here are wrong. The correct ranges can
be seen in the "native" spmi regulator driver
qcom_spmi-regulator.c at pldo_ranges[], ftsmps_ranges[] and
boost_ranges[] for the pldo, ftsmps, and boost type regulators.
Port these ranges over to the RPM SMD regulator driver so that w
The voltage ranges listed in the RPM SMD regulator driver
aren't correct. This series makes the voltage range tables
match what the hardware supports. That fixes a problem
where pm8941 l24 fails to be set at 3.075V when the hardware
really supports it.
Stephen Boyd (3):
regulator: qcom_smd: Fix
When CONFIG_PM is not set, we get a warning about an unused function:
drivers/gpu/drm/exynos/exynos_drm_gsc.c:1219:12: error: 'gsc_clk_ctrl' defined
but not used [-Werror=unused-function]
static int gsc_clk_ctrl(struct gsc_context *ctx, bool enable)
^~~~
This removes the two
A recent commit added barry support to this driver, but that causes
a link failure when CONFIG_POWER_SUPPLY is not set:
drivers/hid/built-in.o: In function `hidpp_battery_get_property':
:(.text+0x1a834): undefined reference to `power_supply_get_drvdata'
drivers/hid/built-in.o: In function `hidpp_r
The newly added zynqmp_dma driver produces a warning on 32-bit architectures
when dma_addr_t is 64-bit wide:
drivers/dma/xilinx/zynqmp_dma.c: In function 'zynqmp_dma_config_sg_ll_desc':
drivers/dma/xilinx/zynqmp_dma.c:321:9: error: cast from pointer to integer of
different size [-Werror=pointer-t
A cleanup patch introduced a harmless warning about now unused local variables:
drivers/rtc/rtc-isl12057.c: In function 'isl12057_rtc_read_alarm':
drivers/rtc/rtc-isl12057.c:249:26: error: unused variable 'alarm_secs'
[-Werror=unused-variable]
unsigned long rtc_secs, alarm_secs;
On Mon, Jul 11, 2016 at 11:30:59PM +0200, Thierry Reding wrote:
> On Mon, Jul 11, 2016 at 09:47:34AM -0700, Doug Anderson wrote:
> > Hi,
> >
> > On Sun, Jul 10, 2016 at 11:56 PM, Stephen Rothwell
> > wrote:
> > > Hi Thierry,
> > >
> > > Today's linux-next merge of the pwm tree got a conflict in:
The newly added mtk-vcodec driver produces a number of warnings in an ARM
allmodconfig build, mainly since it assumes that dma_addr_t is 32-bit wide:
mtk-vcodec/venc/venc_vp8_if.c: In function 'vp8_enc_alloc_work_buf':
mtk-vcodec/venc/venc_vp8_if.c:212:191: error: cast to pointer from integer of
Quoting Maxime Ripard (2016-07-11 13:34:48)
> The Kconfig symbol for the sun8i SoC family was mistyped. Fix that.
>
> Signed-off-by: Maxime Ripard
Applied.
Regards,
Mike
> ---
> drivers/clk/sunxi-ng/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clk/
Quoting Maxime Ripard (2016-07-11 13:34:47)
> The code had a typo and got the wrong offset for the hardcoded divider, fix
> that.
>
> Signed-off-by: Maxime Ripard
> Reported-by: Jean-Francois Moine
> Reported-by: Chen-Yu Tsai
Applied.
Regards,
Mike
> ---
> drivers/clk/sunxi-ng/ccu-sun8i-h3.
On Mon, Jul 11, 2016 at 09:47:34AM -0700, Doug Anderson wrote:
> Hi,
>
> On Sun, Jul 10, 2016 at 11:56 PM, Stephen Rothwell
> wrote:
> > Hi Thierry,
> >
> > Today's linux-next merge of the pwm tree got a conflict in:
> >
> > drivers/regulator/pwm-regulator.c
> >
> > between commit:
> >
> > 8
VLAN and MQ control was doing DMA from the stack. Fix it.
Cc: Michael S. Tsirkin
Cc: "net...@vger.kernel.org"
Signed-off-by: Andy Lutomirski
---
I tested VLAN addition and removal with CONFIG_VMAP_STACK=y,
CONFIG_DEBUG_SG=y and it got rid of the warnings I saw. I haven't
tested the MQ part b
On 11/07/2016 at 10:23:51 +0200, Uwe Kleine-König wrote :
> Hello,
>
> On Mon, Jul 11, 2016 at 06:12:08PM +1000, Stephen Rothwell wrote:
> > After merging the rtc tree, today's linux-next build (x86 64_allmodconfig)
> > produced this warning:
> >
> > drivers/rtc/rtc-isl12057.c: In function 'isl12
The Makefile for building this is "acpi-y" and so it is not built
as a module. Hence including module.h and everything that comes
with it just for the no-op MODULE_LICENSE is rather heavy handed.
The license info is found at the top of the file, so we just remove
the MODULE_LICENSE and the includ
On Mon, 11 Jul 2016 21:31:04 +0200
Ingo Molnar wrote:
>
> * Jacob Pan wrote:
>
> > On Mon, 11 Jul 2016 07:59:19 -0700
> > "Chen, Yu C" wrote:
> >
> > > Currently it is in your x86/timer tree:
> > >
> > > commit fc273eeef314cdaf0ac992b400d126f8184a4d1c
> > > Author: Len Brown
> > > Date:
On Sun, 10 Jul 2016 01:17:05 +0800 cheng...@emindsoft.com.cn wrote:
> For a pure output parameter:
>
> - When callee fails, the caller should not assume the output parameter
>is still valid.
>
> - And callee should not assume the pure output parameter must be
>provided by caller -- cal
On Mon, Jul 11, 2016 at 02:29:39PM +0200, John Crispin wrote:
> +static const struct of_device_id mt6323_of_match[] = {
> + { .compatible = "mediatek,mt6323-regulator", },
> + { /* sentinel */ },
> +};
> +MODULE_DEVICE_TABLE(of, mt6323_of_match);
This may have been answered last time but
On Mon, Jul 11, 2016 at 06:06:48AM +0900, James Bottomley wrote:
> On Sun, 2016-07-10 at 15:29 -0500, Eric W. Biederman wrote:
> > Andrew Vagin writes:
> >
> > > On Fri, Jul 08, 2016 at 10:13:08PM -0500, Eric W. Biederman wrote:
> > > > "W. Trevor King" writes:
> > > >
> > > > > On Thu, Jul 07,
Add the call to of_clk_set_defaults() into the amba probe path so
that devices on the amba bus can use the assigned rates and
parents feature of the common clock framework.
Cc: Michael Turquette
Cc: Jorge Ramirez Ortiz
Signed-off-by: Stephen Boyd
---
drivers/amba/bus.c | 5 +
1 file change
On Mon, Jul 11, 2016 at 10:31:45PM +0200, John Crispin wrote:
> maybe i am missing something here, but i can see the dependencies inside
> the for-next branch of
> git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git. is
> this not the tree i should base patches on for v4.8 ?
Oh, s
On 07/01, Andy Gross wrote:
> The patch changes the initcall for SCM to use subsys_initcall
> instead of arch_initcall. This corrects the order so that we don't
> probe defer when trying to get clks which causes issues later when
> the spm driver makes calls to qcom_set_warm_boot_addr().
>
> The
This avoids pointless races in which another CPU or task might see a
partially populated global pgd entry. These races should normally
be harmless, but, if another CPU propagates the entry via
vmalloc_fault and then populate_pgd fails (due to memory allocation
failure, for example), this prevents
On 07/10, Jorge Ramirez Ortiz wrote:
> On 9 July 2016 at 08:42, Jorge Ramirez
> > um, I retested again this morning and it is all good - I was also a bit
> > surprised when things failed yesterday (it seems one of the wires on my
> > board was loose, sorry).
> >
> > So AFAIC your patch addresses
SMP does ECB crypto on stack buffers. This is complicated and
fragile, and it will not work if the stack is virtually allocated.
Switch to the crypto_cipher interface, which is simpler and safer.
Cc: Marcel Holtmann
Cc: Gustavo Padovan
Cc: Johan Hedberg
Cc: "David S. Miller"
Cc: linux-blueto
Currently, NR_KERNEL_STACK tracks the number of kernel stacks in a
zone. This only makes sense if each kernel stack exists entirely in
one zone, and allowing vmapped stacks could break this assumption.
Since frv has THREAD_SIZE < PAGE_SIZE, we need to track kernel stack
allocations in a unit that
On Sun, Jul 10, 2016 at 02:23:27PM +0100, Jonathan Cameron wrote:
> On 03/07/16 22:04, Alison Schofield wrote:
> > IIO driver, perhaps a reference driver, since this sensor is already
> > supported in hwmon/jc42 driver.
> >
> > Driver supports continuous conversion, resolution changes and
> > susp
kernel_unmap_pages_in_pgd() is dangerous: if a pgd entry in
init_mm.pgd were to be cleared, callers would need to ensure that
the pgd entry hadn't been propagated to any other pgd.
Its only caller was efi_cleanup_page_tables(), and that, in turn,
was unused, so just delete both functions. This le
We should account for stacks regardless of stack size, and we need
to account in sub-page units if THREAD_SIZE < PAGE_SIZE. Change the
units to kilobytes and Move it into account_kernel_stack().
Fixes: 12580e4b54ba8 ("mm: memcontrol: report kernel stack usage in cgroup2
memory.stat")
Cc: Vladimi
101 - 200 of 830 matches
Mail list logo
