Correct CPU supply name to meet cpufreq-dt driver's
requirement for voltage scaling.
Signed-off-by: Anson Huang
Reviewed-by: Fabio Estevam
---
changes since V1:
fix the "No newline at end of file" caused by vim editor.
arch/arm/boot/dts/imx7d-cl-som-imx7.dts | 2 +-
arch/arm/boot/dts/im
Hi Daniel,
On 15 May 2018 at 18:27, Daniel Lezcano wrote:
> On Mon, May 14, 2018 at 04:55:26PM +0800, Baolin Wang wrote:
>> Hi,
>>
>> We will meet below issues when compensating the suspend time for the
>> timekeeping.
>>
>> 1. We have too many different ways of dealing with persistent timekeepi
> From: Matthew Wilcox [mailto:wi...@infradead.org]
> Sent: Wednesday, May 16, 2018 12:20 AM>
> > > > > Then there's the problem of reconnecting the page cache (which is
> > > > > pointed to by ephemeral data structures like inodes and dentries) to
> > > > > the new inodes.
> > > > Yes, it is not
From: Florian Fainelli Sent: 2018年5月16日 7:56
> A number of drivers have the following pattern:
>
> if (np)
> of_mdiobus_register()
> else
> mdiobus_register()
>
> which the implementation of of_mdiobus_register() now takes care of.
> Remove that pattern in drivers that strictly adher
Hi all,
On Thu, 3 May 2018 08:36:54 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the rockchip tree got a conflict in:
>
> arch/arm64/configs/defconfig
>
> between commits:
>
> 93f7bfd930c0 ("arm64: defconfig: makes SND_SIMPLE_CARD to module")
> ddf3fa8b8a16 ("arm64: def
From: Yao Chen
Before Version Patches
==
patch v3
https://www.spinics.net/lists/linux-pci/msg72322.html
patch v2
https://www.spinics.net/lists/kernel/msg2797610.html
patch v1
https://www.spinics.net/lists/kernel/msg2796410.html
Changes between V4 and V3
=
From: Yao Chen
Add support for MSI.
Signed-off-by: Yao Chen
Cc: Xiaowei Song
---
drivers/pci/dwc/pcie-kirin.c | 51
1 file changed, 51 insertions(+)
diff --git a/drivers/pci/dwc/pcie-kirin.c b/drivers/pci/dwc/pcie-kirin.c
index d2970a0..00ca4e5 10
From: Florian Fainelli Sent: 2018年5月16日 7:48
> The Freescale FEC driver builds fine with COMPILE_TEST, so make that
> possible.
>
> Signed-off-by: Florian Fainelli
Acked-by: Fugang Duan
> ---
> drivers/net/ethernet/freescale/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
2018-05-16 5:56 GMT+08:00 Jim Mattson :
> I'd prefer to let the kvm module have the final say as to whether or
> not to allow userspace to do this.
I have an IRC discussion with Paolo, it seems that he didn't like the
original idea of the patchset.
Regards,
Wanpeng Li
>
> On Fri, May 11, 2018 at
On Wed, 2018-04-11 at 20:36 +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Pan Bian
>
>
> [ Upstream commit 35378ce143071c2a6bad4b59a000e9b9f8f6ea67 ]
>
> In functions cx25840_initialize(), cx231x
This patch introduces ops structure for sgmii, This by ensures that
we do not need dummy functions in case of emulation platforms.
Signed-off-by: Hemanth Puranik
---
drivers/net/ethernet/qualcomm/emac/emac-mac.c | 5 +-
drivers/net/ethernet/qualcomm/emac/emac-sgmii.c | 128 ++
Hi Andrew,
2018-05-16 7:59 GMT+09:00 Andrew Morton :
> On Tue, 15 May 2018 11:22:05 +0900 Masahiro Yamada
> wrote:
>
>> This header file is not exported. It is safe to reference types
>> without double-underscore prefix.
>>
>
> It may be safe to do this, but why is it desirable?
It is shorter
On Tue, May 15, 2018 at 9:06 AM, Bartosz Golaszewski wrote:
> 2018-05-14 15:37 GMT+02:00 Rob Herring :
>> On Fri, May 11, 2018 at 11:20 AM, Bartosz Golaszewski wrote:
>>> From: Bartosz Golaszewski
>>>
>>> This introduces the core part of support for early platform drivers
>>> and devices.
>>>
>>
On 5/15/18 5:44 PM, Adam Ford wrote:
On Tue, May 15, 2018 at 4:25 AM, Bartosz Golaszewski wrote:
2018-05-14 2:40 GMT+02:00 Adam Ford :
On Wed, May 9, 2018 at 12:25 PM, David Lechner wrote:
This series converts mach-davinci to use the common clock framework.
The series works like this, the f
Hi Neil,
I love your patch! Yet something to improve:
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.17-rc5 next-20180515]
[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
On Wed, 2018-04-11 at 20:36 +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Thomas Bogendoerfer
>
>
> [ Upstream commit e279e6d98e0cf2c2fe008b3c29042b92f0e17b1d ]
>
> sccnxp driver doesn't get the
Parsing `ls` is fragile at best and _will_ fail when $tree
contains spaces. Replace this with a glob-generated string
and directly assign it to $ALLSOURCE_ARCHS; use a subshell
so `cd` doesn't affect the current working directory.
Signed-off-by: Joey Pabalinas
1 file changed, 1 insertion(+), 4
On Tue, May 15, 2018 at 3:21 PM, Jason Gunthorpe wrote:
> On Sun, May 13, 2018 at 09:00:41AM +0200, Christophe JAILLET wrote:
>> When 'kvzalloc()' is used to allocate memory, 'kvfree()' must be used to
>> free it.
>>
>> Signed-off-by: Christophe JAILLET
>> ---
>> v1 -> v2: More places to update h
On Fri, May 11, 2018 at 06:43:19AM -0400, Oza Pawandeep wrote:
> This patch set brings in error handling support for DPC
>
> The current implementation of AER and error message broadcasting to the
> EP driver is tightly coupled and limited to AER service driver.
> It is important to factor out bro
On Fri, May 11, 2018 at 06:43:24AM -0400, Oza Pawandeep wrote:
> This patch factors out error reporting callbacks, which are currently
> tightly coupled with AER.
>
> DPC should be able to register callbacks and attempt recovery when DPC
> trigger event occurs.
>
> Signed-off-by: Oza Pawandeep
On 05/15/2018 06:56 PM, Florian Fainelli wrote:
A number of drivers have the following pattern:
if (np)
of_mdiobus_register()
else
mdiobus_register()
which the implementation of of_mdiobus_register() now takes care of.
Remove that pattern in drivers that strictly adhere to it.
On Fri, May 11, 2018 at 06:43:22AM -0400, Oza Pawandeep wrote:
> This patch alters the behavior of handling of ERR_FATAL, where removal
> of devices is initiated, followed by reset link, followed by
> re-enumeration.
>
> So the errors are handled in a different way as follows:
> ERR_NONFATAL => ca
When the device_node specified is NULL, fall back to mdiobus_register().
We have a number of drivers having a similar pattern which is:
if (np)
of_mdiobus_register()
else
mdiobus_register()
so incorporate that behavior within the core of_mdiobus_register()
function. This is also c
Hi all,
This patch series updates of_mdiobus_register() such that when the device_node
argument is NULL, it calls mdiobus_register() directly. This is consistent with
the behavior of of_mdiobus_register() when CONFIG_OF=n.
I only converted the most obvious drivers, there are others that have a mu
stub_probe() calls put_busid_priv() in an error path when device isn't
found in the busid_table. Fix it by making put_busid_priv() safe to be
called with null struct bus_id_priv pointer.
This problem happens when "usbip bind" is run without loading usbip_host
driver and then running modprobe. The
Something is majorly messed up with my SMTP server. Only half of the patches
in this series were sent out and the ones that did go out were random.
I keeping getting this as replies for the one's that didn't go out:
https://support.google.com/mail/answer/6596?visit_id=1-636620224226493206-28842143
A number of drivers have the following pattern:
if (np)
of_mdiobus_register()
else
mdiobus_register()
which the implementation of of_mdiobus_register() now takes care of.
Remove that pattern in drivers that strictly adhere to it.
Signed-off-by: Florian Fainelli
---
drivers/net/
On Fri, May 11, 2018 at 05:22:08PM +0530, p...@codeaurora.org wrote:
> On 2018-05-11 16:13, Oza Pawandeep wrote:
> > DPC driver implements link_reset callback, and calls
> > pci_do_fatal_recovery().
> >
> > Which follows standard path of ERR_FATAL recovery.
> >
> > Signed-off-by: Oza Pawandeep
>
Most of the TI drivers build just fine with COMPILE_TEST, cpmac (AR7) is
the exception because it uses a header file from
arch/mips/include/asm/mach-ar7/ar7.h.
Signed-off-by: Florian Fainelli
---
drivers/net/ethernet/ti/Kconfig | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
Those drivers build just fine with COMPILE_TEST, so make that possible.
Signed-off-by: Florian Fainelli
---
drivers/net/phy/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/phy/Kconfig b/drivers/net/phy/Kconfig
index 0e2305ccc91f..343989f9f9d9 100644
--
Hi David,
This patch series includes more drivers to be build tested with COMPILE_TEST
enabled. This helps cover some of the issues I just ran into with missing
a driver *sigh*.
Florian Fainelli (3):
net: ethernet: ti: Allow most drivers with COMPILE_TEST
net: ethernet: freescale: Allow FEC w
The Freescale FEC driver builds fine with COMPILE_TEST, so make that
possible.
Signed-off-by: Florian Fainelli
---
drivers/net/ethernet/freescale/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/freescale/Kconfig
b/drivers/net/ethernet/freescale/K
Hi David,
Today's linux-next merge of the btrfs-kdave tree got a conflict in:
fs/btrfs/props.c
between commit:
f764b4f4bb26 ("btrfs: property: Set incompat flag if lzo/zstd compression is
set")
from the btrfs-fixes tree and commit:
e37739baf401 ("btrfs: allow setting zstd level")
from
On Tue, 15 May 2018, Kirill A. Shutemov wrote:
> On Sun, May 13, 2018 at 09:55:00PM +, Thomas Gleixner wrote:
> > On Fri, 11 May 2018, Kirill A. Shutemov wrote:
> > > --- a/arch/x86/kernel/cpu/common.c
> > > +++ b/arch/x86/kernel/cpu/common.c
> > > @@ -1008,6 +1008,12 @@ static void __init ear
I am Maria-Elisabeth Schaeffler, a German citizen, wife of late George
W.Schaeffler, 75 years old. You can see here:
en.wikipedia.org/wiki/Maria-Elisabeth_Schaeffler I intend to give to you a
portion of my Wealth as a free-will financial donation to you.
Respond now to partake.
Regards
Maria-Elis
Quoting Neil Armstrong (2018-04-26 01:49:29)
> On 25/04/2018 18:33, Jerome Brunet wrote:
> > +#endif /*__AXG_AUDIO_CLKC_H */
> >
>
> Acked-by: Neil Armstrong
Please trim replies.
This fixes klockworks warnings: Pointer 'dev' returned from call to
function 'bus_find_device' at line 179 may be NULL and will be dereferenced
at line 181.
cpsw-phy-sel.c:179: 'dev' is assigned the return value from function
'bus_find_device'.
bus.c:342: 'bus_find_device' explicitly retu
On Tue, May 15, 2018 at 3:58 PM Alexey Dobriyan wrote:
> jb resume_kernel # not returning to v8086
or userspace
> -
> -ENTRY(resume_userspace)
I went back in history, and we used to have multiple "jmp resume_userspace"
including even the vm86.c code (in a different
This patch submission got completely screwed up, sorry, please ignore. I'll
repost soon. There's something messed up with my SMTP server too.
On Tue, May 15, 2018 at 03:45:54PM -0700, Joel Fernandes (Google) wrote:
> I'm able to reproduce a lockdep splat with config options:
> CONFIG_PROVE_LOCKING
There are a couple of whitespace issues around the function
get_random_bytes_arch(). In preparation for patching this function
let's clean them up.
Signed-off-by: Tobin C. Harding
Acked-by: Theodore Ts'o
---
drivers/char/random.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --
Hi all,
Commits
f412e8307d0a ("drm/amd/display: Couple bug fixes in stats module")
e09b6473c605 ("drm/amd/display: Rename encoder_info_packet to dc_info_packet")
87943159f409 ("drm/amd/display: Only program MSA_TIMING_PARAM if it changed")
are missing a Signed-off-by from their author.
--
Currently the function get_random_bytes_arch() has return value 'void'.
If the hw RNG fails we currently fall back to using get_random_bytes().
This defeats the purpose of requesting random material from the hw RNG
in the first place.
There are currently no intree users of get_random_bytes_arch().
Currently we must wait for enough entropy to become available before
hashed pointers can be printed. We can remove this wait by using the
hw RNG if available.
Use hw RNG to get keying material.
Suggested-by: Kees Cook
Signed-off-by: Tobin C. Harding
Reviewed-by: Steven Rostedt (VMware)
---
l
Currently if an attempt is made to print a pointer before there is
enough entropy then '(ptrval)' is printed. This makes debugging
stack traces during early boot difficult.
One partial solution to this problem is to use the hw RNG if it is
available.
Patch 1 - Whitespace fixes.
Patch 2 -
On Wed, 2018-04-11 at 20:35 +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> > From: Will Deacon
>
>
> [ Upstream commit 5f16a046f8e144c294ef98cd29d9458b5f8273e5 ]
>
> FUTEX_OP_OPARG_SHIFT instructs the f
On Tue, May 08, 2018 at 04:50:16PM +0800, Lidong Chen wrote:
> The userspace may invoke ibv_reg_mr and ibv_dereg_mr by different threads.
> If when ibv_dereg_mr invoke and the thread which invoked ibv_reg_mr has
> exited, get_pid_task will return NULL, ib_umem_release does not decrease
> mm->pinned
Hi all,
Today's linux-next merge of the mips-james tree got a conflict in:
arch/mips/boot/dts/xilfpga/Makefile
between commit:
a5a92abbce56 ("MIPS: xilfpga: Stop generating useless dtb.o")
from the mips-fixes tree and commit:
fca3aa166422 ("MIPS: dts: Avoid unneeded built-in.a in DTS di
On 05/15/2018 06:07 PM, Andy Shevchenko wrote:
On Wed, May 16, 2018 at 2:01 AM, Grygorii Strashko
wrote:
This fixes klockworks warnings: Pointer 'dev' returned from call to
function 'bus_find_device' at line 179 may be NULL and will be dereferenced
at line 181.
+ dev_err(dev,
On Tue, May 15, 2018 at 4:00 PM Steven Rostedt wrote:
> If it is that if statement you don't like. We can get rid of it. On
> early boot, the code is called from preemptable context, it's only
> later that it is not. So we know when we can call it directly and when
> we need to have a work queue.
On Wed, May 16, 2018 at 2:01 AM, Grygorii Strashko
wrote:
> This fixes klockworks warnings: Pointer 'dev' returned from call to
> function 'bus_find_device' at line 179 may be NULL and will be dereferenced
> at line 181.
> + dev_err(dev, "unable to find platform device for %s\n",
>
Side note: doing some grepping, I find some other sequences that are a bit
scary, like this:
arch/x86/kernel/acpi/wakeup_32.S-.data
arch/x86/kernel/acpi/wakeup_32.S-ALIGN
arch/x86/kernel/acpi/wakeup_32.S:ENTRY(saved_magic) .long 0
arch/x86/kernel/acpi/wakeup_32.S:ENTRY(saved_eip) .long
Quoting Marcin Ziemianowicz (2018-05-08 21:32:05)
> On Mon, Apr 30, 2018 at 07:58:47AM +0200, Boris Brezillon wrote:
> > On Sun, 29 Apr 2018 15:01:11 -0400
> > Marcin Ziemianowicz wrote:
> >
> > > When a USB device is connected to the USB host port on the SAM9N12 then
> > > you get "-62" error wh
On Mon, May 14, 2018 at 08:46:03PM -0700, Paul E. McKenney wrote:
> On Mon, May 14, 2018 at 05:57:09PM -0700, Joel Fernandes wrote:
> > On Mon, May 14, 2018 at 11:38:23AM -0700, Paul E. McKenney wrote:
> > > On Sun, May 13, 2018 at 08:15:39PM -0700, Joel Fernandes (Google) wrote:
> > > > In recent
We had several issues that would make the programming of IPv6 rules both
inconsistent and error prone:
- the chain ID that we would be asking the hardware to put in the
packet's Broadcom tag would be off by one, it would return one of the
two indexes, but not the one user-space specified
- wh
When we let the kernel pick up a rule location with RX_CLS_LOC_ANY, we
would be able to overwrite the last rules because of a number of issues.
The IPv4 code path would not be checking that rule_index is within
bounds, and it would also only be allowed to pick up rules from range
0..126 instead of
It was possible to delete only one half of an IPv6, which would leave
the second half still programmed and possibly in use. Instead of
checking for the unused bitmap, we need to check the unique bitmap, and
refuse any deletion that does not match that criteria. We also need to
move that check from
This fixes klockworks warnings: Pointer 'dev' returned from call to
function 'bus_find_device' at line 179 may be NULL and will be dereferenced
at line 181.
cpsw-phy-sel.c:179: 'dev' is assigned the return value from function
'bus_find_device'.
bus.c:342: 'bus_find_device' explicitly retu
Hi David,
This patch series fixes a number of usability issues with the SF2 Compact Field
Processor code:
- we would not be properly bound checking the location when we let the kernel
automatically place rules with RX_CLS_LOC_ANY
- when using IPv6 rules and user space specifies a location iden
On 05/15/2018 03:57 PM, Grygorii Strashko wrote:
>
>
> On 05/15/2018 04:59 PM, Florian Fainelli wrote:
>> A number of drivers have the following pattern:
>>
>> if (np)
>> of_mdiobus_register()
>> else
>> mdiobus_register()
>>
>> which the implementation of of_mdiobus_register() now takes
On Tue, 15 May 2018 18:41:17 -0400
Steven Rostedt wrote:
> On Tue, 15 May 2018 15:31:37 -0700
> Linus Torvalds wrote:
>
> > > we could always do this:
> >
> > Ugh. I think I prefer the barriers.
>
If it is that if statement you don't like. We can get rid of it. On
early boot, the code
On Tue, 15 May 2018 11:22:05 +0900 Masahiro Yamada
wrote:
> This header file is not exported. It is safe to reference types
> without double-underscore prefix.
>
It may be safe to do this, but why is it desirable?
> index be15897..9834e90 100644
> --- a/include/linux/types.h
> +++ b/include/
Use INT3 instead of NOP. All that padding between functions is
an illegal area, no legitimate code should jump into it.
I've checked x86_64 allyesconfig disassembly, all changes looks sane:
INT3 is only used after RET or unconditional JMP.
On i386:
* promote ret_from_exception into ENTRY as it ha
On 05/15/2018 04:59 PM, Florian Fainelli wrote:
A number of drivers have the following pattern:
if (np)
of_mdiobus_register()
else
mdiobus_register()
which the implementation of of_mdiobus_register() now takes care of.
Remove that pattern in drivers that strictly adhere to it.
On Tue, May 15, 2018 at 3:29 PM, Thomas Gleixner wrote:
> On Tue, 15 May 2018, Andrew Morton wrote:
>> On Mon, 14 May 2018 22:00:38 -0500 "Gustavo A. R. Silva"
>> wrote:
>>
>> > resource can be controlled by user-space, hence leading to a
>> > potential exploitation of the Spectre variant 1 vuln
On Tue, May 15, 2018 at 12:08:01PM -0700, Paul E. McKenney wrote:
> On Tue, May 15, 2018 at 11:41:15AM -0700, Joel Fernandes wrote:
> > On Tue, May 15, 2018 at 05:55:07AM -0700, Paul E. McKenney wrote:
> > > On Tue, May 15, 2018 at 12:02:43AM -0700, Joel Fernandes wrote:
> > > > Hi Paul,
> > > > Go
On Tue, May 15, 2018 at 3:43 PM Josh Poimboeuf wrote:
> Glancing through the 32-bit and 64-bit entry code, I didn't see any more
> cases. At least it will fail loudly if any such cases do still exist.
\Will it? Do we have objtool checks for it now?
Because without static checks, there could be
The next patch in this series introduces a call to cmpxchg64()
in the block layer core for those architectures on which this
functionality is available. Make it possible to test whether
cmpxchg64() is available by introducing CONFIG_ARCH_HAVE_CMPXCHG64.
Signed-off-by: Bart Van Assche
Cc: Catalin
Recently the blk-mq timeout handling code was reworked. See also Tejun
Heo, "[PATCHSET v4] blk-mq: reimplement timeout handling", 08 Jan 2018
(https://www.mail-archive.com/linux-block@vger.kernel.org/msg16985.html).
This patch reworks the blk-mq timeout handling code again. The timeout
handling cod
The next patch in this series introduces a call to cmpxchg64()
in the block layer core for those architectures on which this
functionality is available. Make it possible to test whether
cmpxchg64() is available by introducing CONFIG_ARCH_HAVE_CMPXCHG64.
Signed-off-by: Bart Van Assche
Cc: Catalin
Recently the blk-mq timeout handling code was reworked. See also Tejun
Heo, "[PATCHSET v4] blk-mq: reimplement timeout handling", 08 Jan 2018
(https://www.mail-archive.com/linux-block@vger.kernel.org/msg16985.html).
This patch reworks the blk-mq timeout handling code again. The timeout
handling cod
Hello Jens,
This is the ninth incarnation of the blk-mq timeout handling rework. All
previously posted comments have been addressed. Please consider this patch
series for inclusion in the upstream kernel.
Bart.
Changes compared to v8:
- Split into two patches.
- Moved the spin_lock_init() call f
Hello Jens,
This is the tenth incarnation of the blk-mq timeout handling rework. All
previously posted comments should have been addressed. Please consider this
patch series for inclusion in the upstream kernel.
Bart.
Changes compared to v9:
- Addressed multiple comments related to patch 1/2: ad
On Tue, May 15, 2018 at 03:27:34PM -0700, Linus Torvalds wrote:
> On Tue, May 15, 2018 at 2:43 PM Alexey Dobriyan wrote:
>
> > It crashed into the middle of the padding.
>
> No, the beginning of the padding. "int3" will push the return address on
> the stack, so when it points to the second 'int
From: Paul McKenney
This is needed for a future tracepoint patch that uses srcu, and to make
sure it doesn't call into lockdep.
tracepoint code already calls notrace variants for rcu_read_lock_sched
so this patch does the same for srcu which will be used in a later
patch. Keeps it consistent wit
I'm able to reproduce a lockdep splat with config options:
CONFIG_PROVE_LOCKING=y,
CONFIG_DEBUG_LOCK_ALLOC=y and
CONFIG_PREEMPTIRQ_EVENTS=y
$ echo 1 > /d/tracing/events/preemptirq/preempt_enable/enable
---
kernel/softirq.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/k
Split reset functions into seperate functions in preparation
of future patches that need to do tracer specific reset.
Cc: Steven Rostedt
Cc: Peter Zilstra
Cc: Ingo Molnar
Cc: Mathieu Desnoyers
Cc: Tom Zanussi
Cc: Namhyung Kim
Cc: Thomas Glexiner
Cc: Boqun Feng
Cc: Paul McKenney
Cc: Freder
On Tue, May 15, 2018 at 4:25 AM, Bartosz Golaszewski wrote:
> 2018-05-14 2:40 GMT+02:00 Adam Ford :
>> On Wed, May 9, 2018 at 12:25 PM, David Lechner wrote:
>>> This series converts mach-davinci to use the common clock framework.
>>>
>>> The series works like this, the first 3 patches fix some is
The regset API documented in defines -ENODEV as the
result of the `->active' handler to be used where the feature requested
is not available on the hardware found. However code handling core file
note generation in `fill_thread_core_info' interpretes any non-zero
result from the `->active' ha
On Tue, May 15, 2018 at 03:28:19PM -0700, Linus Torvalds wrote:
> On Tue, May 15, 2018 at 3:22 PM Josh Poimboeuf wrote:
>
> > The padding isn't needed there, and the resume_userspace symbol is never
> > used, so wouldn't this fix it?
>
> This looks like the correct fix for this case, but are we
On Tue, 15 May 2018 15:31:37 -0700
Linus Torvalds wrote:
> > we could always do this:
>
> Ugh. I think I prefer the barriers.
But the ugliness is only at boot up, where the early printing is
important. The benefit of this is here:
@@ -1709,7 +1717,7 @@ static char *ptr_to_id(char *buf, char
Define an NT_MIPS_FP_MODE core file note and implement a corresponding
regset holding the state handled by PR_SET_FP_MODE and PR_GET_FP_MODE
prctl(2) requests. This lets debug software correctly interpret the
contents of floating-point general registers both in live debugging and
in core files
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/15/2018 04:25 PM, valdis.kletni...@vt.edu wrote:
> On Tue, 15 May 2018 15:49:15 -0600, Al Stone said:
>
>> Not off-hand. Could you please send me a copy of
>> /sys/firmware/acpi/tables/APIC
>
> cat /sys/firmware/acpi/tables/APIC | od -x 000
Linus,
Some of the ftrace internal events use a zero for a data size of
a field event. This is increasingly important for the histogram trigger
work that is being extended.
While auditing trace events, I found that a couple of the xen events
were used as just marking that a function was called,
Define an NT_MIPS_DSP core file note type and implement a corresponding
regset holding the DSP ASE register context, following the layout of the
`mips_dsp_state' structure, except for the DSPControl register stored as
a 64-bit rather than 32-bit quantity in a 64-bit note.
The lack of DSP ASE re
On Tue, May 15, 2018 at 02:53:52PM -0700, Nadav Amit wrote:
> Josh Triplett wrote:
>
> > On Tue, May 15, 2018 at 07:11:08AM -0700, Nadav Amit wrote:
> >> GCC considers the number of statements in inlined assembly blocks,
> >> according to new-lines and semicolons, as an indication to the cost of
Use the `unsigned long' rather than `__u32' type for DSP accumulator
registers, like with the regular MIPS multiply/divide accumulator and
general-purpose registers, as all are 64-bit in 64-bit implementations
and using a 32-bit data type leads to contents truncation on context
saving.
Update
Hi,
For years, quite oddly, we have been missing DSP ASE register state from
core files. These days regsets are used to define what goes into a core
file, so here's a change adding one.
As a side effect ptrace(2) can now also access this regset, however no
complementing client implementatio
On Tue, May 15, 2018 at 1:10 PM Steven Rostedt wrote:
> The work queue looks to run immediately.
2ms is definitely not "immediately". It's just "soon".
The whole - and _only_ reason we're doing all these changes is that people
wanted reliable object hashes from very early bootup tracing, so I th
On Tue, May 15, 2018 at 3:25 PM Thomas Gleixner wrote:
> On Wed, 16 May 2018, Alexey Dobriyan wrote:
> --- a/arch/x86/entry/entry_32.S
> +++ b/arch/x86/entry/entry_32.S
> @@ -338,6 +338,11 @@ END(ret_from_fork)
> cmpl$USER_RPL, %eax
> jb resume_kernel
On Tue, 15 May 2018, Andrew Morton wrote:
> On Mon, 14 May 2018 22:00:38 -0500 "Gustavo A. R. Silva"
> wrote:
>
> > resource can be controlled by user-space, hence leading to a
> > potential exploitation of the Spectre variant 1 vulnerability.
> >
> > This issue was detected with the help of Sm
On Tue, May 15, 2018 at 3:22 PM Josh Poimboeuf wrote:
> The padding isn't needed there, and the resume_userspace symbol is never
> used, so wouldn't this fix it?
This looks like the correct fix for this case, but are we sure there aren't
other cases where we have this same "fall through to an EN
On Tue, May 15, 2018 at 2:43 PM Alexey Dobriyan wrote:
> It crashed into the middle of the padding.
No, the beginning of the padding. "int3" will push the return address on
the stack, so when it points to the second 'int3' instruction, it's because
the first one triggered.
Linus
On Wed, May 16, 2018 at 1:24 AM, Andy Shevchenko
wrote:
> On Wed, May 16, 2018 at 1:08 AM, Dan Murphy wrote:
>> On 05/15/2018 04:56 PM, Andy Shevchenko wrote:
+static const struct lm3601x_max_timeouts strobe_timeouts[] = {
+ { 4, 0x00 },
+ { 8, 0x01 },
+
On Tue, 15 May 2018, Josh Poimboeuf wrote:
> On Wed, May 16, 2018 at 12:43:37AM +0300, Alexey Dobriyan wrote:
> > On Tue, May 15, 2018 at 09:25:53PM +, Anvin, H Peter wrote:
> > > Why is that a problem?
> > > Code: 00 00 00 eb e6 cc cc cc cc cc cc cc cc cc cc cc cc cc fa 8d b6 00
> > > 00 00 0
On Wed, 16 May 2018, Alexey Dobriyan wrote:
> On Tue, May 15, 2018 at 09:25:53PM +, Anvin, H Peter wrote:
> > Why is that a problem?
> > Code: 00 00 00 eb e6 cc cc cc cc cc cc cc cc cc cc cc cc cc fa 8d b6 00 00
> > 00 00 e8 5d e8 8f ff 8b 44 24 34 83 e0 03 83 f8 03 72 28 cc cc
> > cc c
On Tue, May 15, 2018 at 05:35:46PM -0400, Steven Rostedt wrote:
> On Wed, 16 May 2018 07:17:06 +1000
> "Tobin C. Harding" wrote:
>
> > > > -void get_random_bytes_arch(void *buf, int nbytes)
> > > > +int __must_check get_random_bytes_arch(void *buf, int nbytes)
> > > > {
> > > > char *p =
On Tue, 15 May 2018 15:49:15 -0600, Al Stone said:
> Not off-hand. Could you please send me a copy of
> /sys/firmware/acpi/tables/APIC
cat /sys/firmware/acpi/tables/APIC | od -x
000 5041 4349 0072 3903 4544 4c4c 2020
020 4243 3358 2020 0020 2009 0107 4d41 2049
040 0013 0001 000
On Wed, May 16, 2018 at 1:08 AM, Dan Murphy wrote:
> On 05/15/2018 04:56 PM, Andy Shevchenko wrote:
>> On Tue, May 15, 2018 at 6:43 PM, Dan Murphy wrote:
>>> + depends on LEDS_CLASS && I2C && OF
>>
>> What is OF specific in this driver?
>
> as3645a_led_class_setup has a "of" dependency
So
From: Thor Thayer
Add qspi_clock
The qspi_clk frequency is updated by U-Boot before starting Linux.
Add QSPI interface node.
Add QSPI flash memory child node.
Setup the QSPI memory in 2 partitions.
Signed-off-by: Thor Thayer
---
v2 s/_/-/ in qspi-clk
rename flash node.
use partit
Quoting sean.w...@mediatek.com (2018-04-27 01:14:44)
> From: Sean Wang
>
> Just add binding for a required clock referenced by Mali-450 on MT7623
> or MT2701 SoC.
>
> Cc: devicet...@vger.kernel.org
> Signed-off-by: Sean Wang
> ---
Applied to clk-next
101 - 200 of 1093 matches
Mail list logo