On 25/07/2017 at 09:37:10 +0200, Quentin Schulz wrote:
> From: Cyrille Pitchen
>
> This patch adds the pin muxing for classd and enables it.
>
> Signed-off-by: Cyrille Pitchen
> Signed-off-by: Nicolas Ferre
> Signed-off-by: Quentin Schulz
> ---
> arch/arm/boot/dts/at91-sama5d2_xplained.dts |
On Wed, Jul 26, 2017 at 2:13 AM, Rafael J. Wysocki wrote:
> On Tuesday, July 25, 2017 05:32:31 PM Arnd Bergmann wrote:
>> The newly added irqchip_fwnode_ops structure is not exported, which can
>> lead to link errors:
>>
>> ERROR: "irqchip_fwnode_ops" [drivers/gpio/gpio-xgene-sb.ko] undefined!
>>
On Tue, Jul 25, 2017 at 11:39 PM, Kamal Dasu wrote:
> Arnd, Cyrille,
>
> I am working on fixing spi-bcm-qspi.c as per Cyrill's suggestion as
> mentioned here : https://patchwork.kernel.org/patch/9624585/.
> And remove the use of SPINOR_OP_READ* and there by remove need to
> include spi-nor.h.
Ok
On Sun, Jul 23, 2017 at 6:27 PM, Icenowy Zheng wrote:
> From: Ondrej Jirman
>
> Add SY8106A regulator to r_i2c bus and enable the r_i2c bus on
> Orange Pi PC, then set the power supply of the ARM cores to this
> regulator, in order to enable DVFS.
>
> Signed-off-by: Ondrej Jirman
> [Icenowy: Ena
Hi Alexandre,
On 26/07/2017 08:57, Alexandre Belloni wrote:
> On 25/07/2017 at 17:44:19 +0200, Nicolas Ferre wrote:
>> On 25/07/2017 at 09:37, Quentin Schulz wrote:
>>> This patch series adds support for the audio PLLs and enables ClassD that
>>> can be found in ATMEL Sama5d2 SoC.
>>>
>>> There ar
Oops, that shouldn't have happened. Actually, our maintainer tooling
ensures this doesn't happen, by auto-adding the committer sob line.
But these patches (and a bunch of others pushed by Benjamin) haven't
been pushed by our tooling it seems (the Link: tag is missing at
least).
Benjamin, what happ
On Sun, Jul 23, 2017 at 6:27 PM, Icenowy Zheng wrote:
> From: Chen-Yu Tsai
>
> This patch utilizes the new PLL clk notifier to gate then ungate the
> PLL CPU clock after rate changes. This should prevent any system hangs
> resulting from cpufreq changes to the clk.
>
> Reported-by: Ondrej Jirman
于 2017年7月26日 GMT+08:00 下午3:08:06, Chen-Yu Tsai 写到:
>On Sun, Jul 23, 2017 at 6:27 PM, Icenowy Zheng wrote:
>> From: Ondrej Jirman
>>
>> Add SY8106A regulator to r_i2c bus and enable the r_i2c bus on
>> Orange Pi PC, then set the power supply of the ARM cores to this
>> regulator, in order to en
On Tue, Jul 25, 2017 at 05:41:36PM +0200, Peter Zijlstra wrote:
> On Wed, May 24, 2017 at 05:59:41PM +0900, Byungchul Park wrote:
> > We can skip adding a dependency 'AX -> B', in case that we ensure 'AX ->
> > the previous of B in hlocks' to be created, where AX is a crosslock and
> > B is a typic
On Tue, Jul 25, 2017 at 03:09:00PM -0400, Douglas Gilbert wrote:
> _TO_ is toward the device (i.e. WRITE) and what T10 call "data-out".
> _FROM_ is from the device (e.g. INQUIRY) and what T10 call "data-in".
>
> _TO_FROM_ is basically _FROM_ (and has nothing to do with bidi).
> _TO_FROM_ is very o
On Tue, Jul 25, 2017 at 05:15:10PM -0700, Dan Williams wrote:
> We're in the process of walking back and potentially deprecating the
> use of the dax mount option for xfs and ext4 since dax can have
> negative performance implications if page cache memory happens to be
> faster than pmem. It should
> > > Hmm, I though that NIAI is a NOP on older machines. A runtime check for
> > > the facility bit is out of the question as the NIAI-7 gets inlined in
> > > the spin_unlock code. So yes, the only available fix is to make the
> > > NIAI hinting conditional on zEC12. Which is quite ugly as we woul
On 25/07/17 11:05, Kirill A. Shutemov wrote:
> On Tue, Jul 18, 2017 at 04:24:06PM +0200, Juergen Gross wrote:
>> Xen PV guests will never run with 5-level-paging enabled. So I guess you
>> can drop the complete if (IS_ENABLED(CONFIG_X86_5LEVEL)) {} block.
>
> There is more code to drop from mmu_pv
Reviewed-by: Marcus Wolf
This is similar to patch "[PATCH -next] staging: pi433: depends on SPI" of
Randy Dunlap
> Arnd Bergmann hat am 25. Juli 2017 um 17:38 geschrieben:
>
>
> I ran into a build error with the new pi433 driver and
> CONFIG_SPI disabled:
>
> drivers/staging/pi433/pi433_if.o:
On Wed, Jul 26, 2017 at 3:16 PM, Icenowy Zheng wrote:
>
>
> 于 2017年7月26日 GMT+08:00 下午3:08:06, Chen-Yu Tsai 写到:
>>On Sun, Jul 23, 2017 at 6:27 PM, Icenowy Zheng wrote:
>>> From: Ondrej Jirman
>>>
>>> Add SY8106A regulator to r_i2c bus and enable the r_i2c bus on
>>> Orange Pi PC, then set the po
On Tue, Jul 25, 2017 at 10:41:48PM -0300, Arnaldo Carvalho de Melo wrote:
SNIP
> > diff --git a/tools/perf/util/stat.c b/tools/perf/util/stat.c
> > index 53b9a994a3dc..2c258554f94d 100644
> > --- a/tools/perf/util/stat.c
> > +++ b/tools/perf/util/stat.c
> > @@ -128,6 +128,9 @@ static int perf_evs
在 2017-07-26 15:30，Chen-Yu Tsai 写道：
On Wed, Jul 26, 2017 at 3:16 PM, Icenowy Zheng wrote:
于 2017年7月26日 GMT+08:00 下午3:08:06, Chen-Yu Tsai 写到:
On Sun, Jul 23, 2017 at 6:27 PM, Icenowy Zheng
wrote:
From: Ondrej Jirman
Add SY8106A regulator to r_i2c bus and enable the r_i2c bus on
Orange Pi
Enabling and preparing clocks can be written quite naturally with
recursion. We start at some point in the tree and recurse up the
tree to find the oldest parent clk that needs to be enabled or
prepared. Then we enable/prepare and return to the caller, going
back to the clk we started at and enabli
On 07/26/2017 07:29 AM, Vinod Koul wrote:
> On Mon, Jul 24, 2017 at 01:55:10PM +, Pierre Yves MORDRET wrote:
>
+
+ res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
+ if (!res)
+ return -ENODEV;
+
+ iomem = devm_ioremap_resource(&pdev->dev, res);
On Tue, Jul 25, 2017 at 01:25:07PM -0500, Jason L Tibbitts III wrote:
> > "JT" == Johannes Thumshirn writes:
> ioctl(3, SG_IO, {interface_id='S', dxfer_direction=SG_DXFER_TO_DEV,
> cmd_len=12, cmdp="\xa5\x00\x00\x00\x00\x01\x03\xe9\x00\x00\x00\x00",
> mx_sb_len=20, iovec_count=0, dxfer_len=0
Commit 1c3c5eab1715 ("sched/core: Enable might_sleep() and
smp_processor_id() checks early") enables checks for might_sleep() and
smp_processor_id() being used in preemptible code earlier in the boot
than before. This results in a new BUG from
pcibios_set_cache_line_size().
BUG: using smp_processo
There exist macros to return the cache line size of the L1 dcache and L2
scache but there is currently no macro for the L3 tcache. Add this macro
which will be used by the following patch "MIPS: PCI: Fix
smp_processor_id() in preemptible"
Signed-off-by: Matt Redfearn
---
Changes in v3:
Split in
From: Yuantian Tang
ls2088a supports another cpu idle state which is pw20 which saves
more power when cpu is idle.
It was implemented through psci firmware.
Signed-off-by: Tang Yuantian
---
arch/arm64/boot/dts/freescale/fsl-ls2088a.dtsi | 17 +
arch/arm64/boot/dts/freescale/fsl
From: Yuantian Tang
ls1088a supports another cpu idle state which is ph20 which saves
more power when cpu is idle.
It was implemented through psci firmware.
Signed-off-by: Tang Yuantian
---
arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi | 22 ++
1 file changed, 22 insertion
On Tue, Jul 25, 2017 at 04:59:36PM -0700, Paul E. McKenney wrote:
> On Tue, Jul 25, 2017 at 11:55:10PM +0200, Peter Zijlstra wrote:
> > People always do crazy stuff, but what surprised me is that such s patch
> > got merged in urcu even though its known broken for a number of
> > architectures.
>
On 25/07/17 16:09, Boris Ostrovsky wrote:
> On 07/25/2017 05:50 AM, Juergen Gross wrote:
>> Provide a hook in hypervisor_x86 called after setting up initial
>> memory mapping.
>>
>> This is needed e.g. by Xen HVM guests to map the hypervisor shared
>> info page.
>
> This is not necessarily a probl
On Tue, Jul 25, 2017 at 10:50:13PM +, Mathieu Desnoyers wrote:
> This would implement a MEMBARRIER_CMD_PRIVATE_EXPEDITED (or such) flag
> for expedited process-local effect. This differs from the "SHARED" flag,
> since the SHARED flag affects threads accessing memory mappings shared
> across pr
On Wed, Jul 26, 2017 at 11:12:03AM +0530, Pratyush Anand wrote:
> I too had thought to put it under include/linux/perf_event.h : struct
> perf_event. But, see hw_break_module_init() which does not have knowledge of
> this structure, and we need to have some way so that none-perf kernel module
> imp
On Tue, Jul 25, 2017 at 12:48:40PM -0500, Grygorii Strashko wrote:
> Hi Johan,
>
> On 07/25/2017 03:24 AM, Johan Hovold wrote:
> > On Mon, Jul 24, 2017 at 05:16:02PM -0500, Grygorii Strashko wrote:
> >> On 07/24/2017 04:52 AM, Johan Hovold wrote:
> >>> Since commit a8636c89648a ("PM / Runtime: Don
On Tue, Jul 25, 2017 at 01:40:06PM +0300, Andy Shevchenko wrote:
> Christoph, can we apply this one at least to move things forward?
Id be happy to pick this up for 4.14. Does everyone involved agree
that the uuid tree is the right one?
On 2017/7/25 18:30, Marc Zyngier wrote:
On 22/07/17 04:54, Hanjun Guo wrote:
From: Hanjun Guo
When running 4.13-rc1 on top of D05, I got the boot log:
[0.00] SRAT: PXM 0 -> ITS 0 -> Node 0
[0.00] SRAT: PXM 0 -> ITS 1 -> Node 0
[0.00] SRAT: PXM 0 -> ITS 2 -> Node 0
[
The recent reshuffling of header files left one type definition
missing in some configurations:
In file included from drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.h:39:0,
from drivers/staging/fsl-dpaa2/ethernet/dpaa2-ethtool.c:34:
drivers/staging/fsl-dpaa2/ethernet/../../fsl-mc/in
On Tue, Jul 25, 2017 at 12:47:42AM -0400, Prakash Sangappa wrote:
> Signed-off-by: Prakash Sangappa
> ---
> tools/testing/selftests/vm/userfaultfd.c | 121
> +-
> 1 files changed, 118 insertions(+), 3 deletions(-)
Please describe the new test in the commit log
> d
On Tue, Jul 25, 2017 at 12:47:41AM -0400, Prakash Sangappa wrote:
> In some cases, userfaultfd mechanism should just deliver a SIGBUS signal
> to the faulting process, instead of the page-fault event. Dealing with
> page-fault event using a monitor thread can be an overhead in these
> cases. For ex
gcc warns that the device name might overflow:
drivers/net/hamradio/dmascc.c: In function 'dmascc_init':
drivers/net/hamradio/dmascc.c:584:22: error: 'sprintf' may write a terminating
nul past the end of the destination [-Werror=format-overflow=]
sprintf(dev->name, "dmascc%i", 2 * n + i);
driv
On 26/07/17 08:52, Hanjun Guo wrote:
> On 2017/7/25 18:30, Marc Zyngier wrote:
>> On 22/07/17 04:54, Hanjun Guo wrote:
>>> From: Hanjun Guo
>>>
>>> When running 4.13-rc1 on top of D05, I got the boot log:
>>>
>>> [0.00] SRAT: PXM 0 -> ITS 0 -> Node 0
>>> [0.00] SRAT: PXM 0 -> ITS 1
This reverts commit 809ecb9bca6a9424ccd392d67e368160f8b76c92. Since it
was reported to break vhost_net. We want to cache used event and use
it to check for notification. We try to valid cached used event by
checking whether or not it was ahead of new, but this is not correct
all the time, it could
On 26/07/17 05:03, Masahiro Yamada wrote:
> Some irqchip drivers have a Kconfig prompt. When we run menuconfig
> or friends, those drivers are directly listed in the "Device Drivers"
> menu level. This does not look nice. Create a sub-system level menu.
>
> Signed-off-by: Masahiro Yamada
> ---
On 2017/7/25 18:47, Lorenzo Pieralisi wrote:
On Sat, Jul 22, 2017 at 11:54:12AM +0800, Hanjun Guo wrote:
From: Hanjun Guo
When running 4.13-rc1 on top of D05, I got the boot log:
Nit: You should stick to what the problem is and why you need to solve
it, "Fixes:" tag gives the commit history
On Wed, Jul 26, 2017 at 11:59:12AM +0530, Viresh Kumar wrote:
> On 24-07-17, 15:47, Peter Zijlstra wrote:
> > I said nothing about the shared locking. That is indeed required. All I
> > said is that those two tests you add could be left out.
>
> I was right, I didn't understood your comment at all
* Johan Hovold [170726 00:51]:
> On Tue, Jul 25, 2017 at 12:48:40PM -0500, Grygorii Strashko wrote:
> > So, thank you for your patches and sorry for the noise.
> >
> > Tested-by: Grygorii Strashko
>
> Thanks for testing.
So does the patch description need updating? And this is needed
as a fix
On Tue, 25 Jul 2017, Mani, Rajmohan wrote:
> Hi Lee,
>
> > Subject: Re: [PATCH v4 1/3] mfd: Add new mfd device TPS68470
> >
> > On Fri, 21 Jul 2017, Mani, Rajmohan wrote:
> > > > On Wed, 19 Jul 2017, Rajmohan Mani wrote:
> > > >
> > > > > The TPS68470 device is an advanced power management unit
On Tue, 25 Jul 2017, Andy Shevchenko wrote:
> On Tue, Jul 25, 2017 at 12:10 PM, Lee Jones wrote:
> > On Fri, 21 Jul 2017, Mani, Rajmohan wrote:
> >> > On Wed, 19 Jul 2017, Rajmohan Mani wrote:
>
> >> > > + /* Force software reset */
> >> > > + ret = regmap_write(regmap, TPS68470_REG_RESET,
> >>
On Tue, 25 Jul 2017, Alexander Dahl wrote:
> The converter function for translating ns timings in register values was
> initialized with a wrong function pointer. This resulted in wrong
> register values also for the setup and pulse registers when configuring
> the EBI interface trough dts.
>
> I
On Tue, Jul 25, 2017 at 05:32:08PM -0700, Stephen Boyd wrote:
> On 07/25, Peter De Schrijver wrote:
> > From: Alex Frid
> >
> > Add a check for error returned by divider value calculation to avoid
> > writing error code into hw register.
> >
> > Signed-off-by: Alex Frid
> > Reviewed-by: Peter D
On Tue, Jul 25, 2017 at 03:43:54PM -0400, Leeder, Neil wrote:
> On 7/25/2017 1:01 PM, Mark Rutland wrote:
> > On Mon, Jul 24, 2017 at 05:17:02PM -0400, Neil Leeder wrote:
> >> The check for column exclusion did not verify that the event being
> >> checked was an L2 event, and not a software event.
On Tue, Jul 25, 2017 at 06:37:46PM -0700, Stephen Boyd wrote:
> On 07/25, Peter De Schrijver wrote:
> > A number of smaller fixes and simplifications for the Tegra clock
> > implementation.
>
> Any of these need fixes tags so they can be backported to stable
> trees? Also, everyone is on To: line,
The binding already lists compatibles and regulators for the AXP806,
but it is missing from the list of supported chips at the beginning.
Add it.
Fixes: 204ae2963e10 ("mfd: axp20x: Add bindings for AXP806 PMIC")
Signed-off-by: Chen-Yu Tsai
Acked-by: Rob Herring
Acked-for-MFD-by: Lee Jones
---
The AXP813/AXP818 PMICs used with the A83T/H8 SoCs are actually 2 dies
in one package sharing the serial bus (I2C/RSB) pins. One die is the
actual PMIC. The other is an AC100 codec / RTC combo chip.
This patch enables the RSB controller and adds a device node for the
PMIC die to the h8homlet-v2 de
The X-Powers AXP813 is a PMIC designed to be paired with Allwinner's
A83T SoC. There is also an AXP818, which is paired with the H8 SoC.
The two models seem to be identical, apart from the external markings.
This patch introduces the basic mfd and regulator bindings for the
AXP813.
Signed-off-by
The A83T has an RSB controller for talking to the PMIC and audio codec.
Add a device node for it. Since there is only one usable pinmux setting,
for it, add that as well.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-a83t.dtsi | 23 +++
1 file changed, 23 insertions
The AXP813/AXP818 PMICs used with the A83T/H8 SoCs are actually 2 dies
in one package sharing the serial bus (I2C/RSB) pins. One die is the
actual PMIC. The other is an AC100 codec / RTC combo chip.
This patch adds the device nodes for the AC100 chip to the Cubietruck
Plus device tree.
Signed-off
The AXP813/AXP818 PMICs used with the A83T/H8 SoCs are actually 2 dies
in one package sharing the serial bus (I2C/RSB) pins. One die is the
actual PMIC. The other is an AC100 codec / RTC combo chip.
This patch enables the RSB controller and adds a device node for the
PMIC die to the Cubietruck Plu
From: Quentin Schulz
According to their datasheets, the AXP221, AXP223, AXP288, AXP803,
AXP809 and AXP813 PEK have different values for startup time bits from
the AXP20X, let's use the platform device id with the correct values.
Signed-off-by: Quentin Schulz
Acked-for-MFD-by: Lee Jones
Signed-
The AXP813/AXP818 PMICs used with the A83T/H8 SoCs are actually 2 dies
in one package sharing the serial bus (I2C/RSB) pins. One die is the
actual PMIC. The other is an AC100 codec / RTC combo chip.
This patch adds the device nodes for the AC100 chip to the h8homlet-v2
device tree.
Signed-off-by:
On Tue, Jul 25, 2017 at 01:31:13PM +0100, Roman Gushchin wrote:
> On Tue, Jul 25, 2017 at 03:05:37PM +0300, Vladimir Davydov wrote:
> > On Tue, Jul 25, 2017 at 12:40:47PM +0100, Roman Gushchin wrote:
> > > A removed memory cgroup with a defined low limit and some belonging
> > > pagecache has very
The X-Powers AXP813 PMIC is normally used with Allwinner's A83T SoC.
It has the same range of functions as other X-Powers PMICs, such as
DC-DC buck converter and linear regulator outputs, AC-IN and VBUS
power supplies, power button trigger, GPIOs, ADCs, and a battery
charger.
Note that the IRQ tab
Hi everyone,
This is v2 of my AXP813 support series. The device tree patches are
based on my A83T MMC support series. These will go through the sunxi
tree. The dt-binding and mfd patches are based on v4.13-rc1. These
will go through Lee's mfd tree.
Changes since v1:
- Provided relative path fo
On Wed, Jul 26, 2017 at 04:28:23PM +0800, Chen-Yu Tsai wrote:
> Hi everyone,
>
> This is v2 of my AXP813 support series. The device tree patches are
> based on my A83T MMC support series. These will go through the sunxi
> tree. The dt-binding and mfd patches are based on v4.13-rc1. These
> will go
From: Michal Hocko
vmem_altmap allows vmemmap_populate to allocate memmap (struct page
array) from an alternative allocator rather than bootmem resp.
kmalloc. Only x86 currently supports altmap handling, most likely
because only nvdim code uses this mechanism currently and the code
depends on ZON
From: Michal Hocko
Both functions will use altmap rather than kmalloc for sparsemem-vmemmap
so rename them to alloc_section_memmap/free_section_memmap which better
reflect the functionality.
Signed-off-by: Michal Hocko
---
mm/sparse.c | 16
1 file changed, 8 insertions(+), 8 d
From: Michal Hocko
Physical memory hotadd has to allocate a memmap (struct page array) for
the newly added memory section. kmalloc is currantly used for those
allocations.
This has some disadvantages a) an existing memory is consumed for
that purpose (~2MB per 128MB memory section) and b) if the
From: Michal Hocko
check_pages_isolated_cb currently accounts the whole pfn range as being
offlined if test_pages_isolated suceeds on the range. This is based on
the assumption that all pages in the range are freed which is currently
the case in most cases but it won't be with later changes. I ha
From: Michal Hocko
All current users of the altmap are in the memory hotplug code and
they use __vmemmap_populate explicitly (via __sparse_mem_map_populate).
Complain if somebody uses vmemmap_populate with altmap registered
because that could be an unexpected usage. Also call __vmemmap_populate
w
Hi,
this is another step to make the memory hotplug more usable. The primary
goal of this patchset is to reduce memory overhead of the hot added
memory (at least for SPARSE_VMEMMAP memory model). Currently we use
kmalloc to poppulate memmap (struct page array) which has two main
drawbacks a) it con
On Wed, Jul 26, 2017 at 01:17:17AM -0700, Tony Lindgren wrote: > * Johan Hovold
[170726 00:51]:
> > On Tue, Jul 25, 2017 at 12:48:40PM -0500, Grygorii Strashko wrote:
> > > So, thank you for your patches and sorry for the noise.
> > >
> > > Tested-by: Grygorii Strashko
> >
> > Thanks for testi
On 26 July 2017 at 08:52, Christoph Hellwig wrote:
> On Tue, Jul 25, 2017 at 01:40:06PM +0300, Andy Shevchenko wrote:
>> Christoph, can we apply this one at least to move things forward?
>
> Id be happy to pick this up for 4.14. Does everyone involved agree
> that the uuid tree is the right one?
On Tue, Jul 25, 2017 at 06:10:57PM +0200, Rafael J. Wysocki wrote:
> On Tuesday, July 25, 2017 01:00:12 PM Mika Westerberg wrote:
> > On Tue, Jul 25, 2017 at 01:31:00AM +0200, Rafael J. Wysocki wrote:
> > > From: Rafael J. Wysocki
> > >
> > > On one of my test machines nhi_mailbox_cmd() called fr
On Tue, Jul 25, 2017 at 04:41:14PM +0100, Punit Agrawal wrote:
> When walking the page tables to resolve an address that points to
> !p*d_present() entry, huge_pte_offset() returns inconsistent values
> depending on the level of page table (PUD or PMD).
>
> It returns NULL in the case of a PUD ent
On Wed 2017-07-26 01:33:25, Sergey Senozhatsky wrote:
> Hello,
>
> On (07/25/17 06:57), Greg KH wrote:
> > On Tue, Jul 25, 2017 at 10:28:16AM +0200, Michael Wang wrote:
> > > Hi, greg k-h
> > >
> > > During our testing with 4.4.73 we got soft lockup like:
> > >
> > > NMI watchdog: BUG: soft loc
From: Borislav Petkov
... so that GHES can dump memory errors into it and consumers like
ghes_edac can register.
Signed-off-by: Borislav Petkov
---
drivers/acpi/apei/ghes.c | 14 ++
include/acpi/ghes.h | 2 ++
2 files changed, 16 insertions(+)
diff --git a/drivers/acpi/apei/
From: Borislav Petkov
Hi,
here's the conversion of ghes_edac to a proper module using a notifier.
This is only the bare minimum stuff and we should do all outstanding
work ontop. Which right now is:
* platform whitelist
* Tony: "Additional cleanup: edac_ghes.c should really call
cper_mem_err_l
From: Borislav Petkov
Analogue to the generic pr_* variants but issuing the EDAC prefix.
No functionality change.
Signed-off-by: Borislav Petkov
---
drivers/edac/edac_mc.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/edac/edac_mc.h b/drivers/edac/edac_mc.h
index 5357800e418d
From: Borislav Petkov
Register with the GHES notifier chain so that there's no need to call
into the module with ghes_edac_report_mem_error().
Signed-off-by: Borislav Petkov
---
drivers/acpi/apei/ghes.c | 18 +++
drivers/edac/Kconfig | 4 +-
drivers/edac/ghes_edac.c | 129 ++
On Tue 25-07-17 16:41:14, Punit Agrawal wrote:
> When walking the page tables to resolve an address that points to
> !p*d_present() entry, huge_pte_offset() returns inconsistent values
> depending on the level of page table (PUD or PMD).
>
> It returns NULL in the case of a PUD entry while in the
On Wed 26-07-17 10:50:38, Michal Hocko wrote:
> On Tue 25-07-17 16:41:14, Punit Agrawal wrote:
> > When walking the page tables to resolve an address that points to
> > !p*d_present() entry, huge_pte_offset() returns inconsistent values
> > depending on the level of page table (PUD or PMD).
> >
>
On 18/07/17 05:52, Oleksij Rempel wrote:
Hallo all,
Here Gentle Ping to the Old King ;)
DT is already ACKed.
Thanks for patience, As this is a new driver it will be queued for 4.14
just before 4.13-rc5 is released.
thanks,
srini
On 20.06.2017 09:09, Oleksij Rempel wrote:
changes v7:
On Wed, Jul 05, 2017 at 07:57:57AM +, Tian, Kevin wrote:
> > > struct tlb_invalidate_info
> > > {
> > > __u32 model; /* Vendor number */
I don't like to have a model-specifier here, as I don't think its
needed.
> > > __u8 granularity
> > > #define DEVICE_SELECTVIE_INV(1
On Tue, Jul 25, 2017 at 6:36 PM, Michael Chan wrote:
> On Tue, Jul 25, 2017 at 8:29 AM, Arnd Bergmann wrote:
>> The sriov_lock is used to serialize the sriov code with the vfr code.
>> However, when SRIOV is disabled, the lock is not there at all, leading
>> to a build error:
>>
>> drivers/net/et
On Fri, Jul 21, 2017 at 10:53:46PM +0200, Arnd Bergmann wrote:
> I originally sent the patch in March 2013, the day after the broken
^ 2017?
> + depends on NVME_TARGET_FC || NVME_TARGET_FC=n
> + depends on NVME_FC || NVME_FC=n
OK Kconfig is black mag
On Wed, May 31, 2017 at 06:52:29PM +0100, Robin Murphy wrote:
> When a PCI device has DMA quirks, we need to ensure that an upstream
> IOMMU knows about all possible aliases, since the presence of a DMA
> quirk does not preclude the device still also emitting transactions
> (e.g. MSIs) on its 'real
On Wed, Jun 28, 2017 at 07:42:23PM -0700, David Dillow wrote:
> When adding a large scatterlist entry that covers more than the L3
> superpage size (1GB) but has an alignment such that we must use L2
> superpages (2MB) , we give dma_pte_free_level() a range that causes it
> to free the L3 pagetable
On Tue, Jul 04, 2017 at 10:55:55PM +0900, Tomasz Figa wrote:
> Current implementation of __iommu_dma_alloc_pages() keeps adding
> __GFP_HIGHMEM to GFP flags regardless of whether other zone flags are
> already included in the incoming flags. If __GFP_DMA or __GFP_DMA32 is
> set at the same time as
On Wed, Jul 26, 2017 at 11:08 AM, Johannes Thumshirn wrote:
> On Fri, Jul 21, 2017 at 10:53:46PM +0200, Arnd Bergmann wrote:
>> I originally sent the patch in March 2013, the day after the broken
>^ 2017?
Oops. Let me resend that.
>> + depends on NVME_
On Wed, Jul 26, 2017 at 11:16 AM, Arnd Bergmann wrote:
> On Wed, Jul 26, 2017 at 11:08 AM, Johannes Thumshirn
> wrote:
>> On Fri, Jul 21, 2017 at 10:53:46PM +0200, Arnd Bergmann wrote:
>>> I originally sent the patch in March 2013, the day after the broken
>>
On Wed, Jul 26, 2017 at 11:16:10AM +0200, Arnd Bergmann wrote:
> We use this construct in many places these days. A few years ago I added
> a comment whenever I added an instance, but most others don't so I treat
> it as an idiom now.
>
> "depends on X" means that if X=m, the current symbol can on
On Wed, Jul 26, 2017 at 11:17:09AM +0200, Arnd Bergmann wrote:
> Ah, it was only below the "---" line, so I'll skip the resending
> unless you want me
> to add a comment in the Kconfig file.
Nah no need, really.
Reviewed-by: Johannes Thumshirn
--
Johannes Thumshirn
Hi,
I had some IRC discussions with Peter and V4 is based on his feedback.
Here is the diff between V3 and V4:
diff --git a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c
index d64754fb912e..df9aa1ee53ff 100644
--- a/kernel/sched/cpufreq_schedutil.c
+++ b/kernel/sched/cpufreq
This patch updates the schedutil governor to process cpufreq utilization
update hooks called for remote CPUs where the remote CPU is managed by
the cpufreq policy of the local CPU.
Based on initial work from Steve Muckle.
Signed-off-by: Viresh Kumar
---
kernel/sched/cpufreq_schedutil.c | 21 +++
On Tue, Jul 04, 2017 at 10:55:56PM +0900, Tomasz Figa wrote:
> diff --git a/drivers/iommu/dma-iommu.c b/drivers/iommu/dma-iommu.c
> index bf23989b5158..6ed8c8f941d8 100644
> --- a/drivers/iommu/dma-iommu.c
> +++ b/drivers/iommu/dma-iommu.c
> @@ -433,6 +433,7 @@ static struct page **__iommu_dma_allo
We do not call cpufreq callbacks from scheduler core for remote
(non-local) CPUs currently. But there are cases where such remote
callbacks are useful, specially in the case of shared cpufreq policies.
This patch updates the scheduler core to call the cpufreq callbacks for
remote CPUs as well.
Fo
This patch updates the legacy governors (ondemand/conservative) to
process cpufreq utilization update hooks to be called for remote CPUs.
Proper locking is already in place for shared policies and nothing extra
is required to be done.
Based on initial work from Steve Muckle.
Signed-off-by: Vires
Hi Joerg,
On Wed, Jul 26, 2017 at 6:15 PM, Joerg Roedel wrote:
> On Tue, Jul 04, 2017 at 10:55:55PM +0900, Tomasz Figa wrote:
>> Current implementation of __iommu_dma_alloc_pages() keeps adding
>> __GFP_HIGHMEM to GFP flags regardless of whether other zone flags are
>> already included in the inc
On Wed, Jul 05, 2017 at 08:27:53PM +0300, Dmitry Osipenko wrote:
> Commit 7d3002cc8c16 ("iommu/core: split mapping to page sizes as supported
> by the hardware") replaced 'int gfp_order' with a 'size_t size' of
> iommu_map / iommu_unmap function arguments, but missed the function
> prototypes for t
Hi Joerg,
On Wed, Jul 26, 2017 at 6:24 PM, Joerg Roedel wrote:
> On Tue, Jul 04, 2017 at 10:55:56PM +0900, Tomasz Figa wrote:
>> diff --git a/drivers/iommu/dma-iommu.c b/drivers/iommu/dma-iommu.c
>> index bf23989b5158..6ed8c8f941d8 100644
>> --- a/drivers/iommu/dma-iommu.c
>> +++ b/drivers/iommu/
From: Srinivas Kandagatla
missing err.h header file can cause simillar errors like below
in some configurations.
"error: implicit declaration of function 'ERR_PTR'
[-Werror=implicit-function-declaration]"
This adds the missing include to ensure we can always include
the header.
Signed-off-by: S
From: Frank Wang
As the comments from Heiko Stuebner that compatible
should not contain any placeholders, this patch fix it for rk3228 SoC.
Note that this is a fix for v4.13, due to fixing the current non-standard
binding name that should not become part of an official kernel release.
Signed-o
From: Dan Carpenter
"p" is the list iterator so it can't be NULL. Static checkers complain
about this unnecessary check because we dereference the list iterator to
get the next item in the list so we'd be in trouble if it really was
NULL. I have removed the check.
Signed-off-by: Dan Carpenter
From: Philipp Zabel
Commit a53e35db70d1 ("reset: Ensure drivers are explicit when requesting
reset lines") started to transition the reset control request API calls
to explicitly state whether the driver needs exclusive or shared reset
control behavior. Convert all drivers requesting exclusive re
From: Leonard Crestez
This function does a quick and easy read of an u32 value without any
kind of resource management code on the consumer side.
Signed-off-by: Leonard Crestez
Reviewed-by: Shawn Guo
Signed-off-by: Srinivas Kandagatla
---
drivers/nvmem/core.c | 37 +
1 - 100 of 968 matches
Mail list logo
