Hi,
On Fri, Sep 08, 2017 at 09:25:45AM +1000, Stephen Rothwell wrote:
> Hi Al,
>
> After merging the vfs tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> kernel/signal.c: In function 'C_SYSC_rt_sigaction':
> kernel/signal.c:3405:19: warning: unused variable '
The following patch series is an ad hoc "cleanup" that I made
while perusing the code (I'm not well versed in this code, so I
would not be surprised if there were objections to the changes):
[1] net: __sock_cmsg_send(): Remove unused parameter `msg'
[2] net: inet_recvmsg(): Remove unnecessary
Date: Thu, 7 Sep 2017 03:21:38 +
Signed-off-by: Michael Witten
---
include/net/sock.h | 2 +-
net/core/sock.c| 4 ++--
net/ipv4/ip_sockglue.c | 2 +-
net/ipv6/datagram.c| 2 +-
4 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/include/net/sock.h b/include/net/sock
Date: Fri, 8 Sep 2017 00:47:49 +
The flag `MSG_DONTWAIT' is handled by passing an argument through
the dedicated parameter `nonblock' of the function `tcp_recvmsg()'.
Presumably because `MSG_DONTWAIT' is handled so explicitly, it is
unset in the collection of flags that are passed to `tcp_recv
Date: Thu, 7 Sep 2017 20:07:40 +
With this commit, the list's lock is locked/unlocked only once
for the duration of `skb_queue_purge()'.
Hitherto, the list's lock has been locked/unlocked every time
an item is dequeued; this seems not only inefficient, but also
incorrect, as the whole point of
Hello all,
The gscaler has hardware rotation limits. So this patch set support
the rotate hardware limits of gsc.
To avoid problems with bisectability, patches 1~4 must be merged and
then merged 5 and 6.
Changes for V3:
- Fixed of_match_node() to of_device_get_match_data() in drm gsc driver.
- A
Exynos 5250 and 5420 have different hardware rotation limits.
Since we have to distinguish between these two, we add different
compatible(samsung,exynos5250-gsc and samsung,exynos5420-gsc).
Signed-off-by: Hoegeun Kwon
---
Documentation/devicetree/bindings/media/exynos5-gsc.txt | 1 +
1 file chan
Exynos 5250 and 5420 have different hardware rotation limits. However,
currently it uses only one compatible - "exynos5-gsc". Since we have
to distinguish between these two, we add different compatible.
Signed-off-by: Hoegeun Kwon
---
arch/arm/boot/dts/exynos5250.dtsi | 8
arch/arm/boot
On Fri, 8 Sep 2017, Himanshi Jain wrote:
> Added space around(one on each side of) binary
I think that just around would be clear enough.
In the previous patches on this file, found with git log --oneline, a
subject line of staging: iio: ad7192: seems to be more popular when the
patch affects
The gscaler has hardware rotation limits that need to be hardcoded
into driver. Distinguish them and add them to the property list.
The hardware rotation limits are related to the cropped source size.
When swap occurs, use rot_max size instead of crop_max size.
Also the scaling limits are related
The hardware rotation limits of gsc depends on SOC (Exynos
5250/5420/5433). Distinguish them and add them to the driver data.
Signed-off-by: Hoegeun Kwon
---
drivers/media/platform/exynos-gsc/gsc-core.c | 96
1 file changed, 83 insertions(+), 13 deletions(-)
diff --
Currently, the compatible('samsung,exynos5-gsc') is not used.
Remove unnecessary compatible.
Signed-off-by: Hoegeun Kwon
---
arch/arm/boot/dts/exynos5250.dtsi | 8
arch/arm/boot/dts/exynos5420.dtsi | 4 ++--
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/arch/arm/boot/dt
Currently, the compatible('samsung,exynos5-gsc') is not used.
Remove unnecessary compatible.
Signed-off-by: Hoegeun Kwon
---
Documentation/devicetree/bindings/media/exynos5-gsc.txt | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/media
On 2017年09月08日 13:04, Heiko Stuebner wrote:
Am Freitag, 8. September 2017, 09:23:09 CEST schrieb Mark yao:
On 2017年09月07日 20:09, Heiko Stübner wrote:
Hi Mark,
Am Donnerstag, 7. September 2017, 18:16:29 CEST schrieb Mark yao:
Looks good for me, so:
Reviewed-by: Mark Yao
I'd like to apply the
On 08/09/2017 07:42, Nicolin Chen wrote:
On Thu, Sep 07, 2017 at 10:23:43PM -0700, Nicolin Chen wrote:
The set_sysclk() now is used to override the output bit clock rate.
But this is not a common way to implement a set_dai_sysclk(). And
this creates a problem when a general machine driver (simp
Hi Linus,
Very sorry that I had not responded quickly.
When I was digging into tool version dependency,
as you pointed out, gperf is a problem (but seemed one time breakage
for gperf 3.1)
flex seemed very stable for a long time.
bison seemed a bit problem if old version is used.
But, I did not
On (09/07/17 16:05), Luck, Tony wrote:
[..]
> >>if (not_a_function_descriptor(ptr))
> >>return ptr;
> >
> > I'm not sure if it's possible on ia64/ppc64/parisc64
> > to reliably detect if it's a function descriptor or not.
>
> Agreed. I don't know how to write this test (without cha
On (09/06/17 22:27), Helge Deller wrote:
> This patch series fixes the wrong usages of the %pF and %pS printk format
> specifiers throughout the kernel code.
>
> Both specifiers have the same result on most architectures. But on ia64, ppc64
> and parisc64 architectures the %pF specifier does an ex
Hi Mark,
On 6 September 2017 at 21:28, Mark Brown wrote:
> On Wed, Sep 06, 2017 at 07:26:51PM +0800, Baolin Wang wrote:
>> This patch adds one static ida variable to manage SPI bus number, moreover
>> we can get dynamic bus number from ida instead of one "dynamic" IDs, which
>> can be removed.
>
On Fri, 8 Sep 2017, Markus Trippelsdorf wrote:
CC+ Borislav. He might have access to such a beast
> On 2017.09.07 at 08:28 +0200, Markus Trippelsdorf wrote:
> > On 2017.09.06 at 15:15 +0200, Markus Trippelsdorf wrote:
> > > On 2017.09.06 at 14:52 +0200, Thomas Gleixner wrote:
> > > > On Tue, 5 Se
On 8 September 2017 05:47:52 BST, Himanshi Jain wrote:
>Added space around(one on each side of) binary
>operator(-) as preferred according to kernel
>coding style.
>
>Signed-off-by: Himanshi Jain
Take a closer look at that macro. It isn't doing what you think... To give a
hint, changing this
On Thu, Sep 07, 2017 at 10:59:49AM +0530, Archit Taneja wrote:
> Hi Benjamin,
>
> This should be pushed to drm-misc by you, right?
I applied it. I guess Philippe Cornu should also become drm-misc committer
instead of just acking a patch and hoping fairies will pick it up.
-Daniel
>
> Thanks,
>
shost->async_scan should be protected by mutex_lock, otherwise the check
of "called twice" won't work.
Signed-off-by: Ouyang Zhaowei
---
drivers/scsi/scsi_scan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/scsi_scan.c b/drivers/scsi/scsi_scan.c
index fd88dab.
From: rui_feng
Add support for new chip rts5260.
Signed-off-by: Rui Feng
---
drivers/mfd/Makefile | 2 +-
drivers/mfd/rts5260.c| 543 +++
drivers/mfd/rtsx_pcr.c | 8 +
drivers/mfd/rtsx_pcr.h | 1 +
include/linux/mfd/rtsx
On Wed, 6 Sep 2017, Dan Williams wrote:
> On Wed, Sep 6, 2017 at 10:59 PM, Thomas Gleixner wrote:
> >> commit 7c9ae7f053e9e896c24fd23595ba369a5fe322e1
> >
> > -ENOSUCHCOMMIT
>
> Sorry, that's still pending in -next.
Ok.
> >> Author: Carolyn Wyborny
> >> Date: Tue Jun 20 15:16:53 2017 -0700
>
This script extends testability of the Linux ACPI subsystem.
It is reported by QA teams that using the known validation tools, there are
still modules in the ACPI subsystem have low test coverage.
We confirmed that the coverage can be increased by doing more following
tests:
1. dynamic module loa
So this is upstream now but it will cause a crash on boot with older skiboots
with:
powernv-cpufreq: cpufreq pstate min 101 nominal 50 max 0
powernv-cpufreq: Workload Optimized Frequency is enabled in the platform
Disabling lock debugging due to kernel taint
Severe Machine check interrupt [Not re
* Andy Lutomirski wrote:
> More obviously, if CONFIG_DEBUG_VM=y, we'll trip over an assertion
> in the next context switch. The result of *that* is a failure to
> resume from suspend with probability 1 - 1/6^(cpus-1).
Nice fix, thanks!
On a related note, this bug could have been more debuggab
On Wed, Sep 06, 2017 at 04:33:02PM -0500, Josh Poimboeuf wrote:
> On Wed, Sep 06, 2017 at 12:26:13AM -0500, Miguel Bernal Marin wrote:
> > kernel/locking/rwsem.o: warning: objtool: downgrade_write()+0x22: call
> > without frame pointer save/setup
> >
> > The warning means gcc 7.2.0 placed the __d
* Andy Lutomirski wrote:
> On Wed, Sep 6, 2017 at 3:16 PM, Andi Kleen wrote:
> > Andy Lutomirski writes:
> >>
> >> - Lots of people (Linus included) have asked to convert the entry
> >>code to pop registers on exit instead of movqing them off the
> >>stack. This makes a bunch of prog
On Wed, 6 Sep 2017 23:45:02 +0200
Cyrille Pitchen wrote:
> spi_nor_read_sfdp() calls nor->read() to read the SFDP data.
> When the m25p80 driver is used (pretty common case), nor->read() is then
> implemented by the m25p80_read() function, which is likely to initialize a
> 'struct spi_transfer'
On Thu, Sep 7, 2017 at 12:24 PM, Julia Lawall wrote:
> One last detail. The subject line above is not in the same format as that
> of all of the other subject lines one commits affecting this file. You
> can use git log --oneline to see what others have done. It is not really
> possible to gues
> -Original Message-
> From: Colin King [mailto:colin.k...@canonical.com]
> Sent: Thursday, August 31, 2017 4:25 PM
> Subject: [PATCH] fsl/fman: make arrays port_ids static, reduces object
> code size
>
> From: Colin Ian King
>
> Don't populate the arrays port_ids on the stack, instead m
* Eric Biggers wrote:
> Thanks for fixing these! I don't have time to review these in detail, but I
> ran
> the crypto self-tests on the affected algorithms, and they all pass. I also
> benchmarked them before and after; the only noticable performance difference
> was
> that sha256-avx2 and
* Miguel Bernal Marin wrote:
> kernel/locking/rwsem.o: warning: objtool: up_read()+0x11: call without frame
> pointer save/setup
>
> The warning means gcc 7.2.0 placed the __up_read() inline asm (and its
> call instruction) before the frame pointer setup in up_read(),
> which breaks frame poin
On Thu, 7 Sep 2017 00:50:12 +0200
Cyrille Pitchen wrote:
> Le 06/09/2017 à 23:45, Cyrille Pitchen a écrit :
> > spi_nor_read_sfdp() calls nor->read() to read the SFDP data.
> > When the m25p80 driver is used (pretty common case), nor->read() is then
> > implemented by the m25p80_read() function,
I'm announcing the release of the 3.18.70 kernel.
All users of the 3.18 kernel series must upgrade.
The updated 3.18.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.18.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 49237a0442cd..124d821c2f89 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 18
-SUBLEVEL = 69
+SUBLEVEL = 70
EXTRAVERSION =
NAME = Diseased Newt
diff --git a/drivers/gpu/drm/ttm/ttm_page_alloc.c
b/drivers/gpu/drm/ttm/ttm_pag
+ Linus
On 6 September 2017 at 08:03, Adrian Hunter wrote:
> On 06/09/17 05:44, Shawn Lin wrote:
>> + Seraphime
>>
>> On 2017/9/6 3:47, Pavel Machek wrote:
>>> Hi!
>>>
>>> I tried to write to the MMC card; process hung and I got this in the
>>> dmesg.
>>
>>
>> A similar report for 4.13 cycle was
On Mon, Jun 19, 2017 at 12:24:13PM -0700, Kees Cook wrote:
> David, if you can Ack this, I'll carry it in my tree.
This didn't seem to make it anywhere and we got the sad blacklist
entry instead..
On AMD Family17h-based (EPYC) system, a logical NUMA node can contain
upto 8 cores (16 threads) with the following topology.
C0 | T0 T1 |||| T0 T1 | C4
||||
C1 | T0 T1 | L3 || L3 | T0 T1 | C5
On Thu, Sep 07, 2017 at 11:34:12AM +0530, Prateek Sood wrote:
> Remove circular dependency deadlock in a scenario where hotplug of CPU is
> being done while there is updation in cgroup and cpuset triggered from
> userspace.
>
> Example scenario:
> kworker/0:0 => kthreadd => init:729 => init:1 => k
On Wed, Sep 06, 2017 at 06:30:57AM -0700, Tony Lindgren wrote:
> Hi,
>
> * Joonsoo Kim [170905 16:32]:
> > I think that I made a mistake for configuration CONFIG_HIGHMEM=y and
> > CONFIG_HAVE_MEMBLOCK_NODE_MAP=y. In this case, the MOVABLE_ZONE can
> > be *!highmem*. Could you check that your conf
* Mike Galbraith wrote:
> On Wed, 2017-09-06 at 18:14 +0200, Peter Zijlstra wrote:
> > On Wed, Sep 06, 2017 at 11:03:33AM +0200, Peter Zijlstra wrote:
> > > On Wed, Sep 06, 2017 at 01:59:14AM -0700, Andy Lutomirski wrote:
> > > > > Any specifics on your setup?
> > > >
> > > > On further fiddlin
On Wed, 6 Sep 2017, Andy Lutomirski wrote:
> When Linux brings a CPU down and back up, it switches to init_mm and then
> loads swapper_pg_dir into CR3. With PCID enabled, this has the side effect
> of masking off the ASID bits in CR3.
>
> This can result in some confusion in the TLB handling cod
I'm announcing the release of the 4.4.87 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 1207bf6a0e7a..f6838187b568 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 4
-SUBLEVEL = 86
+SUBLEVEL = 87
EXTRAVERSION =
NAME = Blurry Fish Butt
diff --git a/arch/alpha/include/asm/types.h b/arch/alpha/include/asm/types.h
i
I'm announcing the release of the 4.9.48 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index a0abbfc15a49..cfa188b427b1 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 9
-SUBLEVEL = 47
+SUBLEVEL = 48
EXTRAVERSION =
NAME = Roaring Lionus
diff --git a/arch/alpha/include/asm/types.h b/arch/alpha/include/asm/types.h
ind
On Thu, 07 Sep 2017, Rafael J. Wysocki wrote:
> On Wednesday, September 6, 2017 12:52:09 PM CEST Lee Jones wrote:
> > > > In any case, I wouldn't mind it if you took the [3/3] from this series,
> > > > because
> > > > if there are any conflicts with it, they will be trivial to resolve.
> > > >
On Thu, Aug 31, 2017 at 10:01:30AM -0600, Alex Williamson wrote:
> On Thu, 31 Aug 2017 11:40:52 +0200
> Jan Glauber wrote:
>
> > On Wed, Aug 30, 2017 at 08:40:12AM -0600, Alex Williamson wrote:
> > > On Wed, 30 Aug 2017 16:24:54 +0200
> > > Jan Glauber wrote:
> > >
> > > > Root ports of cn8xx
>> @@ -336,21 +331,24 @@ static int snd_card_ymfpci_probe(struct pci_dev *pci,
>> legacy_ctrl &= ~YMFPCI_LEGACY_FMEN;
>> pci_write_config_word(pci, PCIR_DSXG_LEGACY,
>> legacy_ctrl);
>> } else if ((err = snd_opl3_hwdep_new(opl3, 0, 1, NULL)) <
The BIOS on SGI UV system will report a UV system table which describes
specific firmware capabilities available to the Linux kernel at runtime.
This UV system table only exists on SGI UV system. And it's detected
in efi_init() which is at very early stage.
So introduce a new helper function is_ea
On SGI UV system, kernel often hangs when KASLR is enabled. Disabling
KASLR makes kernel work well.
The back trace is:
kernel BUG at arch/x86/mm/init_64.c:311!
invalid opcode: [#1] SMP
[...]
RIP: 0010:__init_extra_mapping+0x188/0x196
[...]
Call Trace:
init_extra_mapping_uc+0x13/0x15
map_hi
This is v2 post RESEND. Add Mike's Acked-by to patch 2/2 as he suggested
in private mail. And update patches log slightly.
This patchset is trying to fix a bug that SGI UV system casually hang
during boot with KASLR enabled. The root cause is that mm KASLR adapts
size of the direct mapping section
On 07.09.2017 06:50, Coly Li wrote:
> On 2017/9/7 上午4:27, Helge Deller wrote:
>> Use the %pS instead of the %pF printk format specifier for printing symbols
>> from direct addresses. This is needed for the ia64, ppc64 and parisc64
>> architectures.
>>
>> Signed-off-by: Helge Deller
>> Cc: linux-bc
On Thu, 7 Sep 2017 15:23:55 +1000 Stephen Rothwell
wrote:
> Hi all,
>
> On Wed, 2 Aug 2017 16:31:45 +1000 Stephen Rothwell
> wrote:
> >
> > On Wed, 2 Aug 2017 15:45:54 +1000 Stephen Rothwell
> > wrote:
> > >
> > > On Tue, 01 Aug 2017 09:08:01 -0400 "Zi Yan"
> > > wrote:
> > > >
> > > >
I'm announcing the release of the 4.12.11 kernel.
All users of the 4.12 kernel series must upgrade.
The updated 4.12.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.12.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 6889ec6a091d..e7b2b54b032c 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 12
-SUBLEVEL = 10
+SUBLEVEL = 11
EXTRAVERSION =
NAME = Fearless Coyote
diff --git a/arch/alpha/include/asm/types.h b/arch/alpha/include/asm/types.h
i
Hello Paul,
Thank you for your response.
Can you give us hint what does this panic indicate? A random kernel memory
corruption? An improper use of an RCU primitive? A hardware issue?
This happened only once in one of the production systems, and we don't have
a reproduction scenario unfortuna
* Jiri Kosina wrote:
> On Wed, 6 Sep 2017, Andy Lutomirski wrote:
>
> > When Linux brings a CPU down and back up, it switches to init_mm and then
> > loads swapper_pg_dir into CR3. With PCID enabled, this has the side effect
> > of masking off the ASID bits in CR3.
> >
> > This can result in
Add a notify chain for process memory section, with
which other modules might do error recovery.
Signed-off-by: Xie XiuQi
---
drivers/acpi/apei/ghes.c | 10 ++
include/acpi/ghes.h | 8
2 files changed, 18 insertions(+)
diff --git a/drivers/acpi/apei/ghes.c b/drivers/acpi/
With ARM v8.2 RAS Extension, SEA are usually triggered when memory errors
are consumed. In some cases, if the error address is in a clean page or a
read-only page, there is a chance to recover. Such as error occurs in a
instruction page, we can reread this page from disk instead of killing
process.
Remove the local variable inflight_counter as it is never used.
Signed-off-by: Srishti Sharma
---
Changes in v5:
- Correct the format of the subject.
drivers/staging/ccree/ssi_cipher.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/staging/ccree/ssi_cipher.c
b/drivers/staging/cc
With ARM v8.2 RAS Extension, SEA are usually triggered when memory errors
are consumed. In some cases, if the error address is in a clean page or a
read-only page, there is a chance to recover. Such as error occurs in a
instruction page, we can reread this page from disk instead of killing
process.
On 2017/9/7 下午3:42, Helge Deller wrote:
> On 07.09.2017 06:50, Coly Li wrote:
>> On 2017/9/7 上午4:27, Helge Deller wrote:
>>> Use the %pS instead of the %pF printk format specifier for printing symbols
>>> from direct addresses. This is needed for the ia64, ppc64 and parisc64
>>> architectures.
>>>
On Thu, Sep 07, 2017 at 09:40:11AM +0200, Jan Glauber wrote:
> So what if we add an additional check like:
>
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index fdf65a6..389db4b 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -4389,6 +4389,9 @@ static bool pci_slot_resetab
In some platform, when SEA triggerred, physical address might be
reported by memory section, so we save it for error recovery later.
Signed-off-by: Xie XiuQi
---
arch/arm64/kernel/ras.c | 31 +++
1 file changed, 31 insertions(+)
diff --git a/arch/arm64/kernel/ras.c b
From: Luca Coelho
The LEDS_CMD command is only supported in some newer FW versions
(e.g. iwlwifi-8000C-31.ucode), so we can't send it to older versions
(such as iwlwifi-8000C-27.ucode).
To fix this, check for a new bit in the FW capabilities TLV that tells
when the command is supported.
Note th
Looks good. Thanks!
regards,
dan carpenter
On Tue, 05 Sep 2017, Lee Jones wrote:
> On Tue, 05 Sep 2017, 冯锐 wrote:
>
> > > > +static void rts5250_set_l1off_cfg_sub_d0(struct rtsx_pcr *pcr, int
> > > > +active) {
> > > > + struct rtsx_cr_option *option = &(pcr->option);
> > > > +
> > > > + u32 interrupt = rtsx_pci_readl(pcr, RTS
On Tue, 05 Sep 2017, Colin King wrote:
> From: Colin Ian King
>
> Don't populate the arrays vcore_val, vpll_val and vaux_val on the
> stack, instead make them static const. Makes the object code smaller
> by over 370 bytes:
>
> Before:
>text data bss dec hex filename
>
On Tue, 05 Sep 2017, Maciej Purski wrote:
> This patch adds muic of_compatible in order to use the muic device
> driver in device tree.
>
> Signed-off-by: Maciej Purski
> Reviewed-by: Chanwoo Choi
> Reviewed-by: Krzysztof Kozlowski
> Acked-by: Rob Herring
> Acked-for-MFD-by: Lee Jones
>
> -
The save_stack_trace() and save_stack_trace_tsk() wrappers of
__save_stack_trace() add themselves to the call stack, and thus appear in the
recorded stacktraces. This is redundant and wasteful when we have limited space
to record the useful part of the backtrace with e.g. page_owner functionality.
On Wed, 06 Sep 2017, Ray Jui wrote:
> Add binding document for Broadcom iProc's Chip Device Resource Unit
> (CDRU). Multiple iProc based chips have this CDRU block that contains
> miscellaneous registers for chip or device configurations. Start with
> Stingray specific compatible string for the in
Hello Helge,
On (09/07/17 08:01), Helge Deller wrote:
[..]
> > hm...
> > can we fix it in lib/vsprintf.c instead?
thanks for a quick reply.
> There is nothing to fix in vsprintf, because it is already providing
> both %pF and %pS for the two different architecture-specific API call
> implement
On Wed, 06 Sep 2017, Ray Jui wrote:
> Add binding document for Broadcom iProc's Multi-Host Bridge (MHB)
> block
>
> Signed-off-by: Ray Jui
> Reviewed-by: Scott Branden
> ---
> .../devicetree/bindings/mfd/brcm,iproc-mhb.txt | 18
> ++
> 1 file changed, 18 insertions(+)
On Mon, 04 Sep 2017, Takashi Iwai wrote:
> This patch adds the MFD driver for Dollar Cove (TI version) PMIC with
> ACPI INT33F5 that is found on some Intel Cherry Trail devices.
> The driver is based on the original work by Intel, found at:
> https://github.com/01org/ProductionKernelQuilts
>
>
Hi Cyrille,
On Wed, Sep 6, 2017 at 11:45 PM, Cyrille Pitchen
wrote:
> spi_nor_read_sfdp() calls nor->read() to read the SFDP data.
> When the m25p80 driver is used (pretty common case), nor->read() is then
> implemented by the m25p80_read() function, which is likely to initialize a
> 'struct spi_
On Mon, 04 Sep 2017, Takashi Iwai wrote:
> This patch adds the opregion driver for Dollar Cove TI PMIC on Intel
> Cherry Trail devices. The patch is based on the original work by
> Intel, found at:
> https://github.com/01org/ProductionKernelQuilts
> with many cleanups and rewrites.
>
> The
On 07/09/17 10:18, Ulf Hansson wrote:
> + Linus
>
> On 6 September 2017 at 08:03, Adrian Hunter wrote:
>> On 06/09/17 05:44, Shawn Lin wrote:
>>> + Seraphime
>>>
>>> On 2017/9/6 3:47, Pavel Machek wrote:
Hi!
I tried to write to the MMC card; process hung and I got this in the
From: Shu Wang
memory leak was found by kmemleak. exit_cifs_spnego
should be called before cifs module removed, or
cifs root_cred will not be released.
kmemleak report:
unreferenced object 0x880070a3ce40 (size 192):
backtrace:
kmemleak_alloc+0x4a/0xa0
kmem_cache_alloc+0xc7/0x1d0
Hi Linus,
Enjoy!
The following changes since commit 569dbb88e80deb68974ef6fdd6a13edb9d686261:
Linux 4.13 (2017-09-03 13:56:17 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git mfd-next-4.14
for you to fetch changes up to b01e9348e1065
* Linus Torvalds wrote:
> On Tue, Sep 5, 2017 at 2:40 PM, Ingo Molnar wrote:
> >
> > Hm, just as background, there are no regression reports I'm aware of
> > against any of these trees, plus most of the dangerous commits have
> > been in linux-next for at least two weeks - the majority of them
On 2017/9/7 12:46, Jaegeuk Kim wrote:
> This patch refactors get_lock_data_page() to handle encryption case directly.
> In order to do that, it introduces common f2fs_submit_page_read().
>
> Signed-off-by: Jaegeuk Kim
Good cleanup job.
Reviewed-by: Chao Yu
Thanks,
> ---
> fs/f2fs/data.c | 1
On (09/07/17 09:42), Helge Deller wrote:
> >> - seq_printf(f, "%p: %pF -> %pf p %p r %i ",
> >> + seq_printf(f, "%p: %pS -> %pf p %p r %i ",
> >> cl, (void *) cl->ip, cl->fn, cl->parent,
> >> r & CLOSURE_REMAINING_MASK);
> >>
> >> @@ -
On Thu, 07 Sep 2017 09:41:39 +0200,
SF Markus Elfring wrote:
>
> >> @@ -336,21 +331,24 @@ static int snd_card_ymfpci_probe(struct pci_dev *pci,
> >>legacy_ctrl &= ~YMFPCI_LEGACY_FMEN;
> >>pci_write_config_word(pci, PCIR_DSXG_LEGACY,
> >> legacy_ctrl);
> >>
* Ingo Molnar wrote:
>
> * Linus Torvalds wrote:
>
> > On Tue, Sep 5, 2017 at 2:40 PM, Ingo Molnar wrote:
> > >
> > > Hm, just as background, there are no regression reports I'm aware of
> > > against any of these trees, plus most of the dangerous commits have
> > > been in linux-next for at
2017-09-06 11:15 GMT+02:00 Jason Yan :
> Add a sysfs attr that LLDD can configure it for every host. We made
> a example in hisi_sas. Other LLDDs using libsas can implement it if
> they want.
>
> Suggested-by: Hannes Reinecke
> Signed-off-by: Jason Yan
> CC: John Garry
> CC: Johannes Thumshirn
From: Naresh Kamboju
on ARM and ARM64 devices kernel source tree is not available so
insmod "$SRC_TREE/lib/test_bpf.ko" is not working.
on these target devices the test_bpf.ko is installed under
/lib/modules/`uname -r`/kernel/lib/
so use modprobe dry run to check for missing test_bpf.ko module a
From: Naresh Kamboju
The test script works when kernel source and build module test_bpf.ko
present on the machine. This patch will check if module is present in
the path.
Signed-off-by: Naresh Kamboju
---
tools/testing/selftests/bpf/test_kmod.sh | 8 +---
1 file changed, 5 insertions(+), 3
On Thu, 7 Sep 2017, Srishti Sharma wrote:
> Remove the local variable inflight_counter as it is never used.
>
> Signed-off-by: Srishti Sharma
Acked-by: Julia Lawall
> ---
> Changes in v5:
> - Correct the format of the subject.
> drivers/staging/ccree/ssi_cipher.c | 3 ---
> 1 file changed,
Commit-ID: a731ebe6f17bff9e7ca12ef227f9da4d5bdf8425
Gitweb: http://git.kernel.org/tip/a731ebe6f17bff9e7ca12ef227f9da4d5bdf8425
Author: Peter Zijlstra
AuthorDate: Wed, 6 Sep 2017 12:51:31 +0200
Committer: Ingo Molnar
CommitDate: Thu, 7 Sep 2017 09:29:31 +0200
sched/fair: Fix wake_affine
2017-09-06 11:15 GMT+02:00 Jason Yan :
> Now libsas hotplug work is static, every sas event type has its own
> static work, LLDD driver queues the hotplug work into shost->work_q.
> If LLDD driver burst posts lots hotplug events to libsas, the hotplug
> events may pending in the workqueue like
>
>
On Wed, 06 Sep 2017 08:32:23 +0200,
SF Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Wed, 6 Sep 2017 08:18:30 +0200
>
> Add jump targets so that a bit of exception handling can be better reused
> at the end of these functions.
>
> This issue was detected by using the Coccinelle softwar
On Tue, 05 Sep 2017 22:36:17 +0200,
SF Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Tue, 5 Sep 2017 22:08:30 +0200
>
> Add a jump target so that a bit of common code can be better reused
> at the end of this function.
>
> This issue was detected by using the Coccinelle software.
>
>
From: Rui Feng
Enable power saving for RTS5250S as following steps:
1.Set 0xFE58 to enable clock power management.
2.Check cfg space whether support L1SS or not.
3.If support L1SS, set 0xFF03 to free clkreq.
4.When entering idle status, enable aspm
and set parameters for L1SS and LTR.
5.Wnen en
On Tue, 05 Sep 2017 22:38:16 +0200,
SF Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Tue, 5 Sep 2017 22:22:21 +0200
>
> Add a jump target so that a bit of exception handling can be better reused
> at the end of this function.
>
> This issue was detected by using the Coccinelle software
On Wed, 06 Sep 2017 15:16:29 +0200,
SF Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Wed, 6 Sep 2017 14:45:09 +0200
>
> Add a jump target so that a bit of exception handling can be better reused
> at the end of this function.
>
> This issue was detected by using the Coccinelle software
On Wed, 06 Sep 2017 15:17:38 +0200,
SF Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Wed, 6 Sep 2017 15:00:08 +0200
>
> Add a jump target so that a bit of exception handling can be better reused
> at the end of this function.
>
> This issue was detected by using the Coccinelle software
101 - 200 of 703 matches
Mail list logo
