Hi Philipp,
On Wed, 19 Jul 2017 17:25:46 +0200
Philipp Zabel wrote:
> 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
> cont
Hi Varadarajan,
On Tue, Jun 27, 2017 at 11:45 AM, Varadarajan Narayanan
wrote:
> Enable chip select support for QUP versions later than v1.
> The chip select support was broken in QUP version 1. Hence
> the chip select support was removed earlier in commit
> 4a8573abe965115bc5b064401fd669b74e9852
On 20/07/17 08:52, sean.w...@mediatek.com wrote:
From: Sean Wang
Potential dangerous invalid memory might be accessed if invalid mac value
reflected from the forward port field in rxd4 caused by possible potential
hardware defects. So added a simple sanity checker to avoid the kind of
situati
On 07/19/2017 12:24 PM, Colin King wrote:
From: Colin Ian King
Functions atmel_ecc_i2c_client_alloc and atmel_ecc_i2c_client_free are
local to the source and no not need to be in the global scope. Make
them static.
Cleans up sparse warnings:
symbol 'atmel_ecc_i2c_client_alloc' was not declar
On Wed, 19 Jul 2017, Philipp Zabel wrote:
> 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. Add the explic
On 07/14/2017, 07:22 PM, Josh Poimboeuf wrote:
> +void __unwind_start(struct unwind_state *state, struct task_struct *task,
> + struct pt_regs *regs, unsigned long *first_frame)
> +{
> + memset(state, 0, sizeof(*state));
> + state->task = task;
> +
> + /*
> + * Refu
On Wed, 19 Jul 2017, Philipp Zabel wrote:
> 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. After all driv
On Wed, 12 Jul 2017, Enric Balletbo i Serra wrote:
> From: Stephen Barber
>
> If the EC supports RTC host commands, expose an RTC device.
>
> Signed-off-by: Stephen Barber
> Signed-off-by: Enric Balletbo i Serra
> ---
> drivers/mfd/cros_ec.c | 18 ++
> 1 file changed, 18 inse
On 20-07-17, 01:17, Rafael J. Wysocki wrote:
> On Thu, Jul 20, 2017 at 12:54 AM, Florian Fainelli
> wrote:
> > Hi,
> >
> > We have a particular ARM CPU design that is drawing quite a lot of
> > current upon exit from WFI, and it does so in a way even before the
> > first instruction out of WFI is
On Thu 20-07-17 08:55:42, Vlastimil Babka wrote:
> On 07/14/2017 10:00 AM, Michal Hocko wrote:
> > From: Michal Hocko
> >
> > build_zonelists gradually builds zonelists from the nearest to the most
> > distant node. As we do not know how many populated zones we will have in
> > each node we rely
On Wed, Jul 19, 2017 at 10:42 PM, Waiman Long wrote:
> On 07/19/2017 04:24 PM, Miklos Szeredi wrote:
>> On Mon, Jul 17, 2017 at 3:39 PM, Waiman Long wrote:
>>> The number of positive dentries is limited by the number of files
>>> in the filesystems. The number of negative dentries, however,
>>> h
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
1183 384 01567 61f arch/x8
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by 'uncore.h' work with const
attribute_group. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
9361 216 88966525
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by and 'uncore.h'
work with const attribute_group. So mark the non-const structs as const.
Arvind Yadav (7):
[PATCH 1/7] perf: x86: intel: uncore: constify attribute_group structures.
[P
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by 'uncore.h' work with const
attribute_group. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
41584792 0895022
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
3614 545156057191657 x86/ker
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by 'uncore.h' work with const
attribute_group. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
15137 33528 0 48665be
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
3586 864 3244821182 x86/ker
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by 'uncore.h' work with const
attribute_group. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
82365992 1 1422937
Am 20.07.2017 00:16, schrieb Christophe JAILLET:
> If the 'memcmp' fails, free allocated resources as done in all other
> error handling paths.
>
> Signed-off-by: Christophe JAILLET
> ---
> Please review carefully, this patch looks "too obvious" to me!
> ---
> drivers/dma/ioat/init.c | 2 +-
>
On Wed, Jul 19, 2017 at 11:50 PM, wrote:
> --
> From: Arnd Bergmann
> Subject: kbuild: disable -Wformat-truncation warnings by default
>
> With x86 allmodconfig, we currently get 233 -Wformat-truncation warnings,
> which makes the entire warnin
On 07/14/2017 10:00 AM, Michal Hocko wrote:
> From: Michal Hocko
>
> build_all_zonelists has been (ab)using stop_machine to make sure that
> zonelists do not change while somebody is looking at them. This is
> is just a gross hack because a) it complicates the context from which
> we can call bui
Since we have tty_kopen, we no longer need to export tty_open_by_driver.
This patch makes this function static.
Signed-off-by: Okash Khawaja
---
drivers/tty/tty_io.c |3 +--
include/linux/tty.h |5 -
2 files changed, 1 insertion(+), 7 deletions(-)
--- a/drivers/tty/tty_io.c
+++ b/
The commit 12e84c71b7d4 ("tty: export tty_open_by_driver") exports
tty_open_by_device to allow tty to be opened from inside kernel which
works fine except that it doesn't handle contention with user space or
another kernel-space open of the same tty. For example, opening a tty
from user space while
Hi,
I have updated the patches so that the exclusivity flag is in tty_port.
When closing the struct - by calling tty_release_struct - we also need
to reset the flag. One way to do that is to reset the flag inside
tty_release_struct function, regardless of whether the tty was opened
through tty_kop
This patch replaces call to tty_open_by_driver with a tty_kopen and
uses tty_kclose instead of tty_release_struct to close it.
Signed-off-by: Okash Khawaja
---
drivers/staging/speakup/spk_ttyio.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/drivers/staging/speakup/spk_tty
The access mode checks for peripheral ownership for read/write
permissions should not be required. Every peripheral enabled for
this master is expected to have a read/write permissions. If there
is any such invalid access due to wrong configuration in boot loader
or device tree files, then it shoul
This patch cleans up the following.
- Rename the "pa" to "pmic_arb".
- Rename the spmi_pmic_arb *dev to spmi_pmic_arb *pmic_arb.
- Rename the pa_{read,write}_data() functions to
pmic_arb_{read,write}_data().
- Rename channel to APID.
- Rename the HWIRQ_*() macros to hwirq_to_*().
Signed-off-by:
* This patch series add the support for pmic arbiter hardware v5 along with
the few bug fixes and code cleanup.
* This new series is the combined series of
[PATCH V3 0/5]: spmi: pmic-arb: Fixup patches and
[PATCH V4 0/4]: spmi: pmic-arb: support for V5 HW and bug fixes, which are
being rev
Replace the writel_relaxed with __raw_writel to avoid byte swapping
in pmic_arb_write_data() function. That way the code is independent
of the CPU endianness.
Signed-off-by: Kiran Gunda
Reviewed-by: Stephen Boyd
---
drivers/spmi/spmi-pmic-arb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion
Optimize the qpnpint_irq_set_type() by using a local variable
to hold the handler type. Also clean up other variable usage.
Signed-off-by: Kiran Gunda
---
drivers/spmi/spmi-pmic-arb.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/drivers/spmi/spmi
If "core" memory resource is not specified, then the driver could
end up dereferencing a null pointer. Fix this issue.
Signed-off-by: Kiran Gunda
Reviewed-by: Stephen Boyd
---
drivers/spmi/spmi-pmic-arb.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/spmi/spmi-
From: David Collins
Add support for version 5 of the SPMI PMIC arbiter. It utilizes
different offsets for registers than those found on version 3.
Also, the procedure to determine if writing and IRQ access is
allowed for a given PPID changes for version 5.
Signed-off-by: David Collins
Signed-o
Currently the driver sets the pmic arbiter core interrupt as wakeup capable
irrespective of the child irqs which causes the system to wakeup
unnecessarily. To fix this, set the core interrupt as wakeup capable
only if any of the child irqs request for it. Do this by marking it as
wakeup capable in
From: Fenglin Wu
The opc parameter in pmic_arb_write_cmd() function is defined with type
u8 and it's always greater than or equal to 0. Checking that it's not
less than 0 is redundant and it can cause a forbidden warning during
compilation. Remove the check.
Signed-off-by: Fenglin Wu
Signed-off
Add support for HiSilicon Hi6421v530 PMIC. Hi6421v530 communicates with
main SoC via memory-mapped I/O.
Hi6421v530 and Hi6421 are PMIC chips from the same vendor, HiSilicon,
but at different revisions. They share the same memory-mapped I/O
design. They differ in integrated devices, such as regulat
Update dev_err messages to make them more readable.
Signed-off-by: Guodong Xu
Acked-by: Arnd Bergmann
---
drivers/mfd/hi6421-pmic-core.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/mfd/hi6421-pmic-core.c b/drivers/mfd/hi6421-pmic-core.c
index ad9e3d8..b1139
Change license text to a shorter form of GPLv2.
Signed-off-by: Guodong Xu
Acked-by: Arnd Bergmann
---
drivers/mfd/hi6421-pmic-core.c | 13 ++---
1 file changed, 2 insertions(+), 11 deletions(-)
diff --git a/drivers/mfd/hi6421-pmic-core.c b/drivers/mfd/hi6421-pmic-core.c
index 3fd703f..
This patchset adds driver for HiSilicon Hi6421v530 PMIC.
Mainline kernel already has driver support to a similar chip, Hi6421.
Hi6421 and Hi6421v530 are both from the same vendor, HiSilicon, but
they are at different revisions. They both use the same Memory-mapped
I/O method to communicate with Ma
Returning the output value from a function, when it is possible, is the
better and cleaner way than passing it by the pointer. Hence, modify
the ppid_to_apid mapping function to return apid instead of passing
it by a pointer. While at it, pass the ppid as function parameter to
ppid_to_apid mapping
Modify the pmic_arb version ops to return an __iomem pointer
to the address instead of an offset. That way we do not need to
care about the base address changes in the new HW version.
Signed-off-by: Kiran Gunda
Reviewed-by: Stephen Boyd
---
drivers/spmi/spmi-pmic-arb.c | 93
Allocate the correct memory size (max_pmic_peripherals) for the
mapping_table that holds the apid to ppid mapping. Also use a local
variable for mapping_table for better alignment of the code.
Signed-off-by: Kiran Gunda
---
drivers/spmi/spmi-pmic-arb.c | 11 +--
1 file changed, 5 inserti
Clean up the pmic_arb_find_apid() by using the local
variables to improve the code readability.
Signed-off-by: Kiran Gunda
---
drivers/spmi/spmi-pmic-arb.c | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/drivers/spmi/spmi-pmic-arb.c b/drivers/spmi/spmi-pmic-ar
On Wed, Jul 19, 2017 at 11:47 PM, Christophe JAILLET
wrote:
> In commit 0f987e25cb8a, the source processing has been moved in front of
> the destination processing, but the error handling path has not been
> modified accordingly.
> Free resources in the correct order to avoid some leaks.
>
> Fixes
> >
> > On Wed, Jul 05, 2017 at 01:06:54AM -0700, Tony Lindgren wrote:
> > > > > Not sure if this really is a regression as we've always had a bogus
> > > > > wl1271-nvs.bin in linux-firmware.git. Sure would be nice to fix it,
> > > > > but going back to using a generic wl1271-nvs.bin sure does not
2017-07-19 08:35-0500, Brijesh Singh:
> On 07/19/2017 06:19 AM, Radim Krčmář wrote:
> > 2017-07-17 16:32-0500, Brijesh Singh:
> > > Hi Paolo and Radim
> > >
> > > Any comments on this patch, I could not find it in 4.13-2 branch.
> > >
> > > Please let me know if you want to fix something, or want
Hi Franklin,
On 07/20/2017 01:36 AM, Franklin S Cooper Jr wrote:
+#ifdef CONFIG_OF
+void of_transceiver_is_fixed(struct net_device *dev)
+{
(..)
+}
+EXPORT_SYMBOL(of_transceiver_is_fixed);
+#endif
I'm not sure about the naming here.
As this is a CAN transceiver related option it should b
That's an inverted uuid_equal check. I'll send a fix ASAP.
Switch thunderbolt to the new uuid type.
Signed-off-by: Christoph Hellwig
---
drivers/thunderbolt/switch.c | 8
drivers/thunderbolt/tb.h | 4 ++--
drivers/thunderbolt/tb_msgs.h | 12 ++--
3 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/drivers/thunderbol
Everything uses uuid_t now.
Signed-off-by: Christoph Hellwig
Reviewed-by: Amir Goldstein
---
include/linux/uuid.h | 14 --
1 file changed, 14 deletions(-)
diff --git a/include/linux/uuid.h b/include/linux/uuid.h
index 2251e1925ea4..33b0bdbb613c 100644
--- a/include/linux/uuid.h
+++
Fixes: df33767d ("uuid: hoist helpers uuid_equal() and uuid_copy() from xfs")
Reported-by: kernel test robot
Signed-off-by: Christoph Hellwig
---
lib/test_uuid.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/test_uuid.c b/lib/test_uuid.c
index 478c049630b5..cd819c397dc7
2017-07-19 16:40-0700, Wanpeng Li:
> From: Wanpeng Li
>
> This can be reproduced by EPT=1, unrestricted_guest=N,
> emulate_invalid_state=Y
> or EPT=0, the trace of kvm-unit-tests/taskswitch2.flat is like below, it
> tries
> to emulate invalid guest state task-switch:
>
> kvm_exit: reason TAS
Hi all,
this series removes fixes a bug in the previous uuid pull request and
removes the the uuid_be type. I had planned to send the
last patch for -rc1 already but held off to avoid merge conflicts
in linux-next.
In the meantime the thunderbolt code added a few new instances, so
patch once rem
On Mon, Jul 17, 2017 at 01:59:46AM +0300, Kirill A. Shutemov wrote:
> Hi,
>
> As Ingo requested, I'm resending the rebased patchset after merge window to be
> queued for v4.14.
>
> The patches was reordered and few more fixes added: for Xen and
> dump_pagetables.
>
> Please consider applying.
On Mon 2017-07-17 13:06:28, Florian Fainelli wrote:
> Have the core suspend/resume framework store the system-wide suspend
> state (suspend_state_t) we are about to enter, and expose it to drivers
> via suspend_target_state() in order to retrieve that. The state is
> assigned in suspend_devices_and
On Mon 2017-07-17 23:28:08, Enric Balletbo i Serra wrote:
> Hardware needs a delay between setting an initial (non-zero) PWM and
> enabling the backlight using GPIO. The post-pwm-on-delay-us specifies
> this delay in micro seconds. Hardware also needs a delay between disabing
> the backlight using
2017-07-20 15:57 GMT+08:00 Radim Krčmář :
> 2017-07-19 16:40-0700, Wanpeng Li:
>> From: Wanpeng Li
>>
>> This can be reproduced by EPT=1, unrestricted_guest=N,
>> emulate_invalid_state=Y
>> or EPT=0, the trace of kvm-unit-tests/taskswitch2.flat is like below, it
>> tries
>> to emulate invalid gu
On 07/14/2017 10:00 AM, Michal Hocko wrote:
> From: Michal Hocko
>
> f52407ce2dea ("memory hotplug: alloc page from other node in memory
> online") has introduced N_HIGH_MEMORY checks to only use NUMA aware
> allocations when there is some memory present because the respective
> node might not ha
Hi!
> >--- a/drivers/video/backlight/pwm_bl.c
> >+++ b/drivers/video/backlight/pwm_bl.c
> >@@ -10,6 +10,7 @@
> > * published by the Free Software Foundation.
> > */
> >+#include
> > #include
> > #include
> > #include
> >@@ -35,6 +36,7 @@ struct pwm_bl_data {
> > struct gpio_desc
On Wed, Jul 19, 2017 at 01:05:35PM +0100, Carlos Palminha wrote:
> Add missing __iomem annotation to fix sparse warning:
> - incorrect type in return expression (different address spaces)
How is this going to shut up sparse without a __force?
And once you add the __force please also add a comment
On Mon 2017-07-17 23:28:11, Enric Balletbo i Serra wrote:
> The minnie devices comes with an AUO B101EAN01 panel which is different
> from default veyron devices, thus the power on/off timing sequence is
> slightly different. The datasheet specifies a pwm delay of 200 ms, so
> update the PMW delay
On Thu, 20 Jul 2017, Li, Aubrey wrote:
> Don't get me wrong, even if a fast path is acceptable, we still need to
> figure out if the coming idle is short and when to switch. I'm just worried
> about if irq timings is not an ideal statistics, we have to skip it too.
There is no ideal solution ever.
From: Wanpeng Li
This can be reproduced by EPT=1, unrestricted_guest=N, emulate_invalid_state=Y
or EPT=0, the trace of kvm-unit-tests/taskswitch2.flat is like below, it tries
to emulate invalid guest state task-switch:
kvm_exit: reason TASK_SWITCH rip 0x0 info 4058 0
kvm_emulate_insn: 4200
On Thu, Jul 20, 2017 at 12:51:45PM +0530, Arvind Yadav wrote:
> attribute_group are not supposed to change at runtime. All functions
> working with attribute_group provided by work with
> const attribute_group. So mark the non-const structs as const.
>
> File size before:
>text data
On July 19, 2017 10:10:18 PM PDT, Greg Kroah-Hartman
wrote:
>On Wed, Jul 19, 2017 at 05:24:33PM -0700, Dmitry Torokhov wrote:
>> Many drivers create additional driver-specific device attributes when
>> binding to the device, and providing managed version of
>> device_create_group() will simplify
On Wed, Jul 19, 2017 at 04:10:50PM -0400, Ilia Mirkin wrote:
> I believe the solution is to not call drm_crtc_vblank_off for atomic
> modesetting in nouveau_display_fini. I think Ben's working on it.
Yes, the goal of vblank_on/off was very much to not paper over driver bugs
with clever tricks like
On Wed 19-07-17 15:33:32, Vlastimil Babka wrote:
> On 07/14/2017 10:00 AM, Michal Hocko wrote:
[...]
> > @@ -5146,19 +5145,14 @@ build_all_zonelists_init(void)
> > * unless system_state == SYSTEM_BOOTING.
> > *
> > * __ref due to (1) call of __meminit annotated setup_zone_pageset
>
> Isn't t
On Wed, 19 Jul 2017, Mani, Rajmohan wrote:
> Hi Lee,
>
> > > On Fri, 09 Jun 2017, Mani, Rajmohan wrote:
> > >
> > > > Hi Andy,
> > > >
> > > > > On Tue, Jun 06, 2017 at 03:59:49PM +0300, Andy Shevchenko wrote:
> > > > > > On Tue, Jun 6, 2017 at 2:55 PM, Rajmohan Mani
> > > > > wrote:
> > > > > >
On Thu, Jul 20, 2017 at 09:24:21AM +0200, Arnd Bergmann wrote:
> On Wed, Jul 19, 2017 at 11:50 PM, wrote:
> > --
> > From: Arnd Bergmann
> > Subject: kbuild: disable -Wformat-truncation warnings by default
> >
> > With x86 allmodconfig, we curr
Hi,
On Thursday 20 July 2017 01:42 PM, Borislav Petkov wrote:
On Thu, Jul 20, 2017 at 12:51:45PM +0530, Arvind Yadav wrote:
attribute_group are not supposed to change at runtime. All functions
working with attribute_group provided by work with
const attribute_group. So mark the non-const stru
On Wed, Jul 19, 2017 at 10:30:43AM +0200, Marcus Wolf wrote:
> Hi Greg,
>
> I am surprised and happy about getting all the feedback and ideas how to
> improve. Wow!
>
> Can you tell me, how this is going on? Do I need to collect all those patches,
> evaluate and test them or is it done automati
On Thu, Jul 20, 2017 at 01:12:56AM -0700, Dmitry Torokhov wrote:
> On July 19, 2017 10:10:18 PM PDT, Greg Kroah-Hartman
> wrote:
> >On Wed, Jul 19, 2017 at 05:24:33PM -0700, Dmitry Torokhov wrote:
> >> Many drivers create additional driver-specific device attributes when
> >> binding to the devic
On Wed 19-07-17 09:39:50, Mike Kravetz wrote:
> On 07/13/2017 12:11 PM, Vlastimil Babka wrote:
> > [+CC linux-api]
> >
> > On 07/13/2017 05:58 PM, Mike Kravetz wrote:
> >> mremap will create a 'duplicate' mapping if old_size == 0 is
> >> specified. Such duplicate mappings make no sense for privat
Hi!
> >
> > pr_info("My so important log message %lld\n",
> > ktime_get_real_seconds());
>
> Legacy (these prints have been in Android tree since 2013) for all our
> battery and power analysis tools are keyed off RTC format. There is some
> momentum, default should be epoch seconds/nanosec
在 2017-07-20 06:59，Ondřej Jirman 写道：
Hi,
Icenowy Zheng píše v Út 04. 04. 2017 v 17:50 +0800:
From: Icenowy Zheng
Now we have driver for the PRCM CCU, switch to use it instead of
old-style clock nodes for apb0-related clocks in sunxi-h3-h5.dtsi .
The mux 3 of R_CCU is still the internal oscil
> +#if defined(CONFIG_RTC_SHOW_TIME_RTC)
> + {
> + struct rtc_time tm;
> +
> + rtc_time64_to_tm(ts.tv_sec, &tm);
> + pr_info("%s %d-%02d-%02d %02d:%02d:%02d.%09lu UTC\n",
> + prefix_msg ? prefix_msg : "Time:",
> + tm.t
On Wed, Jul 19, 2017 at 10:39:28AM -0700, Matthias Kaehlcke wrote:
> Commit a21960339c8c ("drm/i915: Consistently use enum pipe for PCH
> transcoders") misses some pieces, due to a problem with the patch
> format, this patch adds the remaining bits.
>
> Fixes: a21960339c8c ("drm/i915: Consistently
On Thu, Jul 20, 2017 at 01:48:17PM +0530, Arvind Yadav wrote:
> It's just show, how much bytes move from data segment to text segment.
> ~arvind
3614 545156057191657 x86/kernel/cpu/microcode/core.o
3614 + 545 = 4159
3742 417156057191657 x86/k
Hi Vladimir,
On 07/19/2017 11:20 PM, Vladimir Zapolskiy wrote:
> Hello Gabriel,
>
> On 07/19/2017 05:25 PM, gabriel.fernan...@st.com wrote:
>> From: Gabriel Fernandez
>>
>> This patch enables clocks for STM32H743 boards.
>>
>> Signed-off-by: Gabriel Fernandez
>>
>> for MFD changes:
>> Acked-by:
* Arnaldo Carvalho de Melo wrote:
> Hi Ingo,
>
> Unusually big one, please conside pulling, details on the signed tag,
>
> - Arnaldo
>
> Test results at the end of this message, as usual.
>
> The following changes since commit 4b1303d0b01440f224cf81493b7e8e43d9b4965e:
>
> perf symbo
Add "mediatek,mt2712-nor" for nor flash node's compatible.
Signed-off-by: Guochun Mao
---
.../devicetree/bindings/mtd/mtk-quadspi.txt|1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/mtd/mtk-quadspi.txt
b/Documentation/devicetree/bindings/mtd/mtk-q
Guochun Mao (1):
Documentation: mtk-quadspi: update DT bindings
Documentation/devicetree/bindings/mtd/mtk-quadspi.txt | 1 +
1 file changed, 1 insertion(+)
--
1.9.1
* kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> master
> head: c981f0b3fb08ee58aacb208fe7f45628af420bba
> commit: 79e6b917e69a34d45e83e72f1e9bb7487d5f5832 [1341/1811] x86/build: Fix
> stack alignment for CLang
> config: x86_64-randco
For family17h, current cpu_core_id is directly taken from the value
CPUID_Fn801E_EBX[7:0] (CoreId), which is the physical ID of the
core within a die. However, on system with downcore configuration
(where not all physical cores within a die are available),
this could result in the case where cp
Commit-ID: e708e35ba6d89ff785b225cd07dcccab04fa954a
Gitweb: http://git.kernel.org/tip/e708e35ba6d89ff785b225cd07dcccab04fa954a
Author: Seunghun Han
AuthorDate: Tue, 18 Jul 2017 18:20:44 +0900
Committer: Ingo Molnar
CommitDate: Thu, 20 Jul 2017 10:28:10 +0200
x86/ioapic: Pass the correc
On Thu, Jul 20, 2017 at 03:29:28AM -0500, Suravee Suthikulpanit wrote:
> For family17h, current cpu_core_id is directly taken from the value
> CPUID_Fn801E_EBX[7:0] (CoreId), which is the physical ID of the
> core within a die. However, on system with downcore configuration
> (where not all phy
Hi,
> Am 18.07.2017 um 21:52 schrieb Sakari Ailus :
>
> On Tue, Jul 18, 2017 at 12:53:12PM +, Hugues FRUCHET wrote:
>>
>>
>> On 07/18/2017 02:17 PM, H. Nikolaus Schaller wrote:
>>> Hi,
>>>
Am 18.07.2017 um 13:59 schrieb Hans Verkuil :
On 12/07/17 22:01, Sylwester Nawrocki w
Hi Ard,
On 20/07/17 06:35, Ard Biesheuvel wrote:
> On 20 July 2017 at 00:32, Laura Abbott wrote:
>> I didn't notice any performance impact but I also wasn't trying that
>> hard. I did try this with a different configuration and ran into
>> stackspace errors almost immediately:
>>
>> [ 0.358026] s
Commit-ID: 69fb09f6ccdb2f070557fd1f4c56c4d646694c8e
Gitweb: http://git.kernel.org/tip/69fb09f6ccdb2f070557fd1f4c56c4d646694c8e
Author: Jin Yao
AuthorDate: Fri, 7 Jul 2017 13:06:34 +0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 18 Jul 2017 23:11:25 -0300
perf annotate: Check
Commit-ID: 7e63a13a266da652f82731b845b5c35dd866ec7e
Gitweb: http://git.kernel.org/tip/7e63a13a266da652f82731b845b5c35dd866ec7e
Author: Jin Yao
AuthorDate: Fri, 7 Jul 2017 13:06:35 +0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 18 Jul 2017 23:13:49 -0300
perf annotate: Imple
On 07/06/2017 05:53 PM, Pierre-Yves MORDRET wrote:
> This patchset adds support for the I2C controller embedded in STM32F7xx SoC.
> It enables I2C transfer in interrupt mode with Standard-mode, Fast-mode and
> Fast-mode+ bus speed.
Gentle ping for driver review since DT Bindings has been acked b
Commit-ID: 274e86fdd379992f90f37fab8df3f640c50fd2cb
Gitweb: http://git.kernel.org/tip/274e86fdd379992f90f37fab8df3f640c50fd2cb
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 14 Jul 2017 09:38:38 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 18 Jul 2017 23:13:51 -0300
pe
Commit-ID: 83a516943136456b9983a0cc8ab4fa5a59860898
Gitweb: http://git.kernel.org/tip/83a516943136456b9983a0cc8ab4fa5a59860898
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 13 Jul 2017 17:14:11 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 18 Jul 2017 23:13:50 -0300
pe
Commit-ID: 3bda69c1c3993a2bddbae01397d12bfef6054011
Gitweb: http://git.kernel.org/tip/3bda69c1c3993a2bddbae01397d12bfef6054011
Author: Alexander Shishkin
AuthorDate: Tue, 18 Jul 2017 14:08:34 +0300
Committer: Ingo Molnar
CommitDate: Thu, 20 Jul 2017 09:43:02 +0200
perf/core: Fix schedu
Commit-ID: 5ca55ab6def81f8cd19a8b88f2ba4abe1aed34cc
Gitweb: http://git.kernel.org/tip/5ca55ab6def81f8cd19a8b88f2ba4abe1aed34cc
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 14 Jul 2017 16:25:35 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 18 Jul 2017 23:13:52 -0300
pe
Commit-ID: 0e7f0b6c2371d41e9bd902fe863be2ec4b6d4e31
Gitweb: http://git.kernel.org/tip/0e7f0b6c2371d41e9bd902fe863be2ec4b6d4e31
Author: Krzysztof Kozlowski
AuthorDate: Thu, 20 Jul 2017 07:01:25 +0200
Committer: Ingo Molnar
CommitDate: Thu, 20 Jul 2017 10:28:19 +0200
x86/defconfig: Remov
Commit-ID: 9cb7cf86440229fd6e6ad1718712742c344653d8
Gitweb: http://git.kernel.org/tip/9cb7cf86440229fd6e6ad1718712742c344653d8
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 14 Jul 2017 09:44:50 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 18 Jul 2017 23:13:52 -0300
pe
Commit-ID: ca3cf049d2430ac83eff5c32af7b86bb2d1285bf
Gitweb: http://git.kernel.org/tip/ca3cf049d2430ac83eff5c32af7b86bb2d1285bf
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 13 Jul 2017 17:15:24 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 18 Jul 2017 23:13:50 -0300
to
Commit-ID: f9f83b3344f9ed6e1d33a87810f38eca5ed6a14f
Gitweb: http://git.kernel.org/tip/f9f83b3344f9ed6e1d33a87810f38eca5ed6a14f
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 14 Jul 2017 10:13:56 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 18 Jul 2017 23:13:53 -0300
pe
Commit-ID: 5dde91edbf6776daba0981c5bc47f1240427e05c
Gitweb: http://git.kernel.org/tip/5dde91edbf6776daba0981c5bc47f1240427e05c
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 14 Jul 2017 10:34:16 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 18 Jul 2017 23:13:54 -0300
pe
1 - 100 of 969 matches
Mail list logo
