On Mon, 10 Dec 2018 23:05:47 +0530, Manivannan Sadhasivam wrote:
> From: Andreas Färber
>
> Add an initial binding for the UART in RDA Micro RDA8810PL SoC.
>
> Signed-off-by: Andreas Färber
> Signed-off-by: Manivannan Sadhasivam
> ---
> .../bindings/serial/rda,8810pl-uart.txt | 17
On Sun, Dec 02, 2018 at 06:57:35AM +, Grumbach, Emmanuel wrote:
> > On Fri, Nov 09, 2018 at 03:43:06PM -0600, Bjorn Helgaas wrote:
> > > -- Forwarded message -
> > > From:
> > > Date: Fri, Nov 9, 2018 at 4:10 AM
> > > Subject: [Bug 201647] New: Intel Wireless card 3165 does
On Mon, 10 Dec 2018 23:05:44 +0530, Manivannan Sadhasivam wrote:
> Document RDA Micro RDA8810PL SoC timer.
>
> Signed-off-by: Manivannan Sadhasivam
> ---
> .../bindings/timer/rda,8810pl-timer.txt | 20 +++
> 1 file changed, 20 insertions(+)
> create mode 100644
>
On Mon, 2018-12-10 at 13:23 -0800, Dan Williams wrote:
> On Mon, Dec 10, 2018 at 1:15 PM Dan Williams wrote:
> >
> > On Mon, Dec 10, 2018 at 12:58 PM Alexander Duyck
> > wrote:
>
> [..]
> > > Also the context for the two functions seems to be a bit different. In
> > > the case of
On Mon, 10 Dec 2018 13:04:25 +0200, Stefan Popa wrote:
> Document support for AD7606 Analog to Digital Converter.
>
> Signed-off-by: Stefan Popa
> ---
> Changes in v2:
> - fixed indentation issues.
> - used gpios instead of gpio.
> - added vendor prefix for
On Thu, 29 Nov 2018 01:50:04 +, Anson Huang wrote:
> NXP i.MX8QXP is an ARMv8 SoC with a Cortex-M4 core inside as
> system controller, the system controller is in charge of system
> power, clock and secure RTC etc. management, Linux kernel
> has to communicate with system controller via MU
Hi Arnd,
Should be prefixed with "spi: atmel-quadspi: " now ;-).
On Mon, 10 Dec 2018 21:38:16 +0100
Arnd Bergmann wrote:
> I ran into a link-time error with the atmel-quadspi driver on the
> EBSA110 platform:
>
> drivers/mtd/built-in.o: In function `atmel_qspi_run_command':
>
Tie syscall information to all CONFIG_CHANGE calls since they are all a
result of user actions.
Exclude user records from syscall context:
Since the function audit_log_common_recv_msg() is shared by a number of
AUDIT_CONFIG_CHANGE and the entire range of AUDIT_USER_* record types,
and since the
On Mon, 10 Dec 2018 13:56:30 +, Srinivas Kandagatla wrote:
> Access to GICR_WAKER is restricted on msm8996 SoC in Hypervisor.
> There are many devices out there with this restriction in place
> and there has been no update to this firmware since last few years,
> making those devices totally
Make a number of changes to normalize CONFIG_CHANGE records by adding
missing op= fields, providing more information in existing op fields
(optional last patch) and connecting all records to existing audit
events. The user record needs special-casing since its content isn't
directly related to
Give a clue as to the source of mark, watch and tree rule changes.
See: https://github.com/linux-audit/audit-kernel/issues/50
See: https://github.com/linux-audit/audit-kernel/issues/59
Signed-off-by: Richard Guy Briggs
---
kernel/audit.h | 4 ++--
kernel/audit_fsnotify.c | 2 +-
The failure to add an audit rule due to audit locked gives no clue
what CONFIG_CHANGE operation failed.
Similarly the set operation is the only other operation that doesn't
give the "op=" field to indicate the action.
All other CONFIG_CHANGE records include an op= field to give a clue as
to what
On Sun, 9 Dec 2018 14:26:07 +, Abel Vesa wrote:
> From: Lucas Stach
>
> This adds the basic DTS for the i.MX8MQ.
> For now only the following peripherals are supported:
> - IOMUXC (pin controller)
> - CCM (clock controller)
> - GPIO
> - UART
> - uSDHC (SD/eMMC controller)
> - FEC (ethernet
Since the context is derived from the task parameter handed to
__audit_free(), hand the context to audit_kill_trees() so it can be used
to associate with a syscall record. This requires adding the context
parameter to kill_rules() rather than using the current audit_context.
The callers of
With ti-sysc, we need to now have the device tree properties for
ti,no-reset-on-init and ti,no-idle-on-init at the module level instead
of the child device level.
Let's check for these properties at the child device level to enable
quirks, and warn about moving the properties to the module level.
Until the board specific dts files are updated to have hwmod
flags at the interconnect target module level, we want to keep
things working both for old and new dts files.
So let's also check the first child for hwmod flags. The module
flags are for the whole module, so only the first child should
Missatge de Guenter Roeck del dia dl., 10 de des.
2018 a les 22:50:
>
> On Mon, Dec 10, 2018 at 1:27 PM Enric Balletbo Serra
> wrote:
> >
> > Missatge de Guenter Roeck del dia dl., 10 de des.
> > 2018 a les 19:34:
> > >
> > > On Mon, Dec 10, 2018 at 10:22 AM Enric Balletbo i Serra
> > > wrote:
Hi Andrey,
On Mon, 10 Dec 2018 22:14:57 +0100 Andrey Konovalov
wrote:
>
> Is this a patch against linux-next? The issue has been addressed by
> v13 of the patchset, which is now in the mm tree and should end up in
> the linux-next soon AFAIU.
It may be in the mmots series, but it is not (yet)
* Arnd Bergmann [181210 21:59]:
> WARNING: vmlinux.o(.text+0x27530): Section mismatch in reference from the
> function am43xx_suspend_init() to the function .init.text:am43xx_map_scu()
> The function am43xx_suspend_init() references
> the function __init am43xx_map_scu().
> This is often because
Arnd Bergmann, le lun. 10 déc. 2018 22:41:50 +0100, a ecrit:
> In this driver, both function the same way, but we want to eventually
> kill off semaphores, so a completion is the better choice here.
>
> Signed-off-by: Arnd Bergmann
Reviewed-by: Samuel Thibault
> ---
>
On 2018-12-10 22:02, Wolfram Sang wrote:
> Some drivers open code handling of suspended adapters. It should be
> handled by the core, though, to ensure generic handling. This patch adds
> the flag and an accessor function.
>
> Signed-off-by: Wolfram Sang
> ---
> drivers/i2c/i2c-core-base.c | 1
Hi Arnd,
On Mon, 10 Dec 2018 21:53:02 +0100 Arnd Bergmann wrote:
>
> A recent change dropped the only user of the variable, which should
> now be removed as well to avoid this warning:
>
> arch/x86/mm/init_32.c: In function 'arch_remove_memory':
> arch/x86/mm/init_32.c:867:15: error: unused
WARNING: vmlinux.o(.text+0x19f90): Section mismatch in reference from the
function littleton_init_lcd() to the function .init.text:pxa_set_fb_info()
The function littleton_init_lcd() references
the function __init pxa_set_fb_info().
This is often because littleton_init_lcd lacks a __init
On 10/12/2018 22:57, Arnd Bergmann wrote:
> When STM32_THERMAL is enabled, this overrides all previously
> enabled files in the same directory, as seen from this link failure:
>
> ERROR: "st_thermal_pm_ops" [drivers/thermal/st/st_thermal_syscfg.ko]
> undefined!
> ERROR: "st_thermal_register"
WARNING: vmlinux.o(.text+0x13250): Section mismatch in reference from the
function acs5k_i2c_init() to the (unknown reference) .init.data:(unknown)
The function acs5k_i2c_init() references
the (unknown reference) __initdata (unknown).
This is often because acs5k_i2c_init lacks a __initdata
WARNING: vmlinux.o(.text+0x27530): Section mismatch in reference from the
function am43xx_suspend_init() to the function .init.text:am43xx_map_scu()
The function am43xx_suspend_init() references
the function __init am43xx_map_scu().
This is often because am43xx_suspend_init lacks a __init
WARNING: vmlinux.o(.text+0x39ecc): Section mismatch in reference from the
function tegra114_gic_cpu_pm_registration() to the (unknown reference)
.init.rodata:(unknown)
The function tegra114_gic_cpu_pm_registration() references
the (unknown reference) __initconst (unknown).
This is often because
When STM32_THERMAL is enabled, this overrides all previously
enabled files in the same directory, as seen from this link failure:
ERROR: "st_thermal_pm_ops" [drivers/thermal/st/st_thermal_syscfg.ko] undefined!
ERROR: "st_thermal_register" [drivers/thermal/st/st_thermal_syscfg.ko]
undefined!
ppp and hamradio have copies of the same code that uses a semaphore
in place of a completion for historic reasons. Make it use the
proper interface instead in all copies.
Signed-off-by: Arnd Bergmann
---
drivers/net/hamradio/6pack.c | 10 +-
drivers/net/hamradio/mkiss.c | 8
Hi all,
Today's linux-next merge of the arm64 tree got conflicts in:
Documentation/arm64/silicon-errata.txt
arch/arm64/Kconfig
between commit:
ce8c80c536da ("arm64: Add workaround for Cortex-A76 erratum 1286807")
from Linus' tree and commit:
a457b0f7f50d ("arm64: Add
On Sun, 9 Dec 2018, Borislav Petkov wrote:
> On Mon, Dec 03, 2018 at 11:23:49AM +, Andrew Cooper wrote:
> > Right, but the documentation also states that where it says package, it
> > means "Node" in AMD's terminology, and the information in CPUID is per
> > socket, not per node.
> >
> > My
For this use case, completions and semaphores are equivalent,
but semaphores are an awkward interface that should generally
be avoided, so use the completion instead.
Signed-off-by: Arnd Bergmann
---
arch/powerpc/kernel/eeh_event.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
On 2018-12-10 22:03, Wolfram Sang wrote:
> Because the adapter will be set up before every transaction anyhow, we
> just need to mark it as adapted to the I2C core.
mark it as "suspended", not "adapted"?
Cheers,
Peter
>
> Signed-off-by: Hiromitsu Yamasaki
> Signed-off-by: Wolfram Sang
> ---
In this usage, the two are completely equivalent, but the
completion documents better what is going on, and we generally
try to avoid semaphores these days.
Signed-off-by: Arnd Bergmann
---
drivers/gpu/host1x/cdma.c | 6 +++---
drivers/gpu/host1x/cdma.h | 4 ++--
2 files changed, 5
On Fri, Dec 07, 2018 at 11:07:05AM -0800, Christoph Hellwig wrote:
> This works is based on the dma-mapping tree, so you probably want to
> want this git tree for testing:
>
> git://git.infradead.org/users/hch/misc.git dma-direct-calls.2
Pulled this tree. Got HEAD
33b9fc015171
On Mon, Dec 10, 2018 at 1:27 PM Enric Balletbo Serra
wrote:
>
> Missatge de Guenter Roeck del dia dl., 10 de des.
> 2018 a les 19:34:
> >
> > On Mon, Dec 10, 2018 at 10:22 AM Enric Balletbo i Serra
> > wrote:
> > >
> > > Hi Guenter,
> > >
> > > On 10/12/18 19:13, Guenter Roeck wrote:
> > > > On
The sem_exit variable is conceptually a completion, so it should
be called that.
Similarly, the semOperations semaphore is a simple mutex, and
can be changed into that, respectively.
With both converted, the ibmphp_hpc_initvars() function is no longer
used and can be removed.
Signed-off-by:
Hi Jacopo
Let's see what I have done
On Sun, Dec 9, 2018 at 8:39 PM jacopo mondi wrote:
>
> Hi Michael, Jagan, Hans,
>
> On Sat, Dec 08, 2018 at 06:07:04PM +0100, Michael Nazzareno Trimarchi wrote:
> > Hi
> >
> > Down you have my tentative of connection
> >
> > I need to hack a bit to have
On 12/10/18 2:34 PM, Arnd Bergmann wrote:
> The "cmd_slot_unal" semaphore is never used in a blocking way
> but only as an atomic counter. Change the code to using
> atomic_dec_if_positive() as a better API.
Looks good to me. We should also convert the return to blk-mq
when we hit failure here to
In this driver, both function the same way, but we want to eventually
kill off semaphores, so a completion is the better choice here.
Signed-off-by: Arnd Bergmann
---
drivers/staging/speakup/spk_ttyio.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git
Make the cpu cgroup controller bypassable in the default hierarchy so
that cpu controller could be activated only in those cgroups that really
need it instead of all the cgroups down to the lowest level that need it.
Signed-off-by: Waiman Long
---
kernel/sched/core.c | 1 +
1 file changed, 1
This semaphore is used like a mutex, so it should use the regular
mutex API, as we do in the other copies of this driver.
Signed-off-by: Arnd Bergmann
---
drivers/staging/rtl8723bs/core/rtw_cmd.c | 4 +-
drivers/staging/rtl8723bs/core/rtw_pwrctrl.c | 73 +--
Bypassable controllers set to bypass mode in the parent's
"cgroup.subtree_control" can now be optionally enabled by writing the
controller name with the '+' prefix to "cgroup.controllers". Using the
'#' prefix will reset it back to the bypass state.
This capability allows a cgroup parent to
Hi Boris,
On 12/10/2018 1:04 PM, Borislav Petkov wrote:
> On Mon, Dec 10, 2018 at 12:42:14PM -0800, Reinette Chatre wrote:
>> Would you be ok if the above is changed to
>>
>> if (id < 0)
>> return ERR_PTR(-ENOENT);
>>
>> as part of this patch?
>
> Yap.
>
>> Looking at
syzbot has found a reproducer for the following crash on:
HEAD commit:40e020c129cf Linux 4.20-rc6
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=1296c56d40
kernel config: https://syzkaller.appspot.com/x/.config?x=c8970c89a0efbb23
dashboard link:
On November 28, 2018 10:24:04 AM GMT+01:00, Thierry Reding
wrote:
>On Thu, Nov 01, 2018 at 10:41:52AM +0200, Peter De Schrijver wrote:
>> On Thu, Nov 01, 2018 at 02:52:29AM +0100, Marcel Ziswiler wrote:
>> > From: Marcel Ziswiler
>> >
>> > As UARTB and VFIR share their clock enable bit it
The cgroup-v2.rst file is updated to document the new bypass mode.
Signed-off-by: Waiman Long
---
Documentation/admin-guide/cgroup-v2.rst | 66 -
1 file changed, 48 insertions(+), 18 deletions(-)
diff --git a/Documentation/admin-guide/cgroup-v2.rst
v5:
- Fix a bug in css_create() reported by Dan Carpenter.
v4:
- Rebased to the latest for-4.21 branch of cgroup tree.
- Make each controller explicitly opt in to become bypassable by
setting the bypassable cgroup_subsys flag. Currently, only cpu
controller is made bypassable.
-
This driver uses many semaphores, most of them are equivalent to
completions. The other copies of this driver got moved over to
completions a while ago, so do the same here.
In this usage scenario, the two are equivalent, so the behavior
should not change.
Signed-off-by: Arnd Bergmann
---
The newly added cgroup controller masks (subtree_bypass and
enable_ss_mask) are now being reported in the debug.masks controller
file.
Signed-off-by: Waiman Long
---
kernel/cgroup/debug.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kernel/cgroup/debug.c b/kernel/cgroup/debug.c
index
A controller in the default hierarchy is bypassable if the bypassable
flag is set in its cgroup_subsys structure. The special prefix '#'
attached to a bypassable controller name can now be written into the
cgroup.subtree_control file to set that controller in bypass mode in
all the child cgroups.
Nothing uses the semaphores any more in this driver, so remove
all references to that type.
Signed-off-by: Arnd Bergmann
---
drivers/staging/rtl8723bs/core/rtw_pwrctrl.c| 1 -
drivers/staging/rtl8723bs/include/osdep_service_linux.h | 2 --
drivers/staging/rtl8723bs/include/rtw_io.h
On Mon, Dec 10, 2018 at 1:21 PM Peter Zijlstra wrote:
>
> On Mon, Dec 10, 2018 at 12:30:23PM +0100, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Add two new metrics for CPU idle states, "above" and "below", to count
> > the number of times the given state had been asked for (or
On 10.12.18 г. 21:05 ч., Andy Gross wrote:
On Mon, Dec 10, 2018 at 02:20:47PM +0200, Stanimir Varbanov wrote:
Hi Andy,
On 12/8/18 7:13 AM, Andy Gross wrote:
The following changes since commit b601f73130a375c912d9f2ec93c5f3cea5d6a3da:
drm: msm: Check cmd_db_read_aux_data() for failure
Hi,
On 10/12/2018 17:15:29+, tudor.amba...@microchip.com wrote:
> From: Cyrille Pitchen
>
> This patch configures the QSPI0 controller pin muxing and declares
> a jedec,spi-nor memory.
>
> sama5d2 Xplained RevB and RevC use the Macronix MX25L25673G flash
> memory which advertises a maximum
The "cmd_slot_unal" semaphore is never used in a blocking way
but only as an atomic counter. Change the code to using
atomic_dec_if_positive() as a better API.
Signed-off-by: Arnd Bergmann
---
drivers/block/mtip32xx/mtip32xx.c | 6 +++---
drivers/block/mtip32xx/mtip32xx.h | 4 ++--
2 files
On Mon, 10 Dec 2018 13:03:33 +0200
Stefan Popa wrote:
> Move ad7606 ADC driver out of staging and into the mainline.
>
> Signed-off-by: Stefan Popa
Looks good to me. I'll let it sit for a few days though to give
time for a final review from anyone else who wants to and for
Rob to take a
The event_wait semaphore has completion semantics, so we can
change it over to the completion interface for clarity without
changing the behavior.
Signed-off-by: Arnd Bergmann
---
drivers/scsi/aacraid/aacraid.h | 3 ++-
drivers/scsi/aacraid/commctrl.c | 1 -
drivers/scsi/aacraid/commsup.c |
The wait_sem member is used like a completion, so we should
use the respective API. The behavior is unchanged.
Signed-off-by: Arnd Bergmann
---
drivers/scsi/aacraid/aacraid.h | 2 +-
drivers/scsi/aacraid/commctrl.c | 4 ++--
drivers/scsi/aacraid/commsup.c | 4 ++--
3 files changed, 5
On Mon, 10 Dec 2018, Peter Zijlstra wrote:
> On Mon, Dec 10, 2018 at 08:52:28AM -0500, Qian Cai wrote:
> > Booting this Huawei TaiShan 2280 arm64 server generated this lockdep
> > warning.
> >
> > [0.00] lockdep_assert_cpus_held+0x50/0x60
> > [0.00]
I have been misled by comments in asm-generic/ptrace.h into thinking
that frame_pointer() is universally available across architectures,
which resulted in a wrong design decision.
Add a comment about frame_pointer in a hope that it will help others
to avoid this mistake in the future.
Cc: Oleg
On Mon, 2018-12-10 at 22:28 +0100, Arnd Bergmann wrote:
> On Mon, Dec 10, 2018 at 10:01 PM Bart Van Assche
> wrote:
> >
> > On Mon, 2018-12-10 at 21:51 +0100, Arnd Bergmann wrote:
> > > In what seems to be a mismatch between the scsi-fixes branch and
> > > the scsi-mkp/for-next branch, a newly
On Mon, Dec 10, 2018 at 12:30 PM Dmitry V. Levin wrote:
> On Mon, Dec 10, 2018 at 11:24:02PM +0300, Dmitry V. Levin wrote:
> > On Mon, Dec 10, 2018 at 12:14:37PM -0800, Max Filippov wrote:
> > > On Mon, Dec 10, 2018 at 4:53 AM Dmitry V. Levin wrote:
> > > > On Sun, Dec 09, 2018 at 09:02:50PM
On Mon, Dec 10, 2018 at 10:01 PM Bart Van Assche wrote:
>
> On Mon, 2018-12-10 at 21:51 +0100, Arnd Bergmann wrote:
> > In what seems to be a mismatch between the scsi-fixes branch and
> > the scsi-mkp/for-next branch, a newly introduced variable from
> > one patch got obsoleted in another one:
>
On Mon, 10 Dec 2018, Arnd Bergmann wrote:
> A recent change dropped the only user of the variable, which should
> now be removed as well to avoid this warning:
>
> arch/x86/mm/init_32.c: In function 'arch_remove_memory':
> arch/x86/mm/init_32.c:867:15: error: unused variable 'zone'
>
On Sat, 8 Dec 2018 22:10:43 +0100
Greg KH wrote:
> On Sat, Dec 08, 2018 at 04:56:45PM -0200, Marcelo Schmitt wrote:
> > Parts of this work came from contributions of Alexandru Ardelean and
> > Dragos Bogdan, I and Gabriel would like to thank for the insights
> > provided by their previous
On Sat, 8 Dec 2018 16:19:59 -0200
Marcelo Schmitt wrote:
> Add a devicetree documentation for the ad5933 and ad5934 impedance
> converter, network analyzer.
>
> Signed-off-by: Marcelo Schmitt
> Signed-off-by: Gabriel Capella
> Co-Developed-by: Gabriel Capella
Device tree binding patches need
Missatge de Guenter Roeck del dia dl., 10 de des.
2018 a les 19:34:
>
> On Mon, Dec 10, 2018 at 10:22 AM Enric Balletbo i Serra
> wrote:
> >
> > Hi Guenter,
> >
> > On 10/12/18 19:13, Guenter Roeck wrote:
> > > On Tue, Nov 27, 2018 at 4:19 AM Enric Balletbo i Serra
> > > wrote:
> > >>
> > >>
On Mon, Dec 10, 2018 at 1:00 PM Arnd Bergmann wrote:
>
> Without CONFIG_PM_SLEEP, we get annoyting warnings about unused functions:
>
> drivers/pinctrl/qcom/pinctrl-msm.c:1082:12: error: 'msm_pinctrl_resume'
> defined but not used [-Werror=unused-function]
> static int msm_pinctrl_resume(struct
On Mon, Dec 10, 2018 at 10:15 PM Andrey Konovalov wrote:
>
> On Mon, Dec 10, 2018 at 9:59 PM Arnd Bergmann wrote:
> >
> > Building with CONFIG_KASAN=y when neither KASAN_GENERIC nor KASAN_SW_TAGS
> > can be selected leads to a build error:
> >
> > arch/arm64/mm/kasan_init.c: In function
On Mon, 10 Dec 2018, Robin Murphy wrote:
> dma-debug is now capable of adding new entries to its pool on-demand if
> the initial preallocation was insufficient, so the IOMMU_LEAK logic no
> longer needs to explicitly change the pool size. This does lose it the
> ability to save a couple of
On Mon, 10 Dec 2018 15:48:07 -0300
Arnaldo Carvalho de Melo wrote:
> Em Mon, Dec 10, 2018 at 01:45:22PM -0500, Steven Rostedt escreveu:
> > From: "Steven Rostedt (VMware)"
> >
> > In the case that a bprintk event has a dereferenced pointer that is stored
> > as a string, and there's more
On 12/10/18 2:11 PM, David Miller wrote:
Cc: sta...@vger.kernel.org
Signed-off-by: Gustavo A. R. Silva
Applied and queued up for -stable.
Please do not CC: stable for networking bug fixes, thank you.
OK. I've got it.
Thanks
--
Gustavo
On Mon, 10 Dec 2018 21:09:20 +
Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: .
>
> The bot has tested the following trees: v4.19.8, v4.14.87, v4.9.144,
> v4.4.166, v3.18.128,
>
>
On Mon, 10 Dec 2018, Vitaly Kuznetsov wrote:
> BIT(13) in HYPERV_CPUID_FEATURES.EBX is described as "ConfigureProfiler" in
> TLFS v4.0 but starting 5.0 it is replaced with 'Reserved'. As we don't
> currently us it in kernel it can just be dropped.
>
> Signed-off-by: Vitaly Kuznetsov
>
On Mon, 10 Dec 2018, Vitaly Kuznetsov wrote:
> hyperv-tlfs.h is a bit messy: CPUID feature bits are not always sorted,
> it's hard to get which CPUID they belong to, some items are duplicated
> (e.g. HV_X64_MSR_CRASH_CTL_NOTIFY/HV_CRASH_CTL_CRASH_NOTIFY).
>
> Do some housekeeping work. While on
On Mon, Dec 10, 2018 at 1:15 PM Dan Williams wrote:
>
> On Mon, Dec 10, 2018 at 12:58 PM Alexander Duyck
> wrote:
[..]
> > Also the context for the two functions seems to be a bit different. In
> > the case of __device_attach_driver the device_lock is already held. In
> > __driver_attach the
The user triggers the creation of a pseudo-locked region when writing
the requested schemata to the schemata resctrl file. The pseudo-locking
of a region is required to be done on a CPU that is associated with the
cache on which the pseudo-locked region will reside. In order to run the
locking
This is one of only two files that initialize a semaphore to a negative
value. We don't really need the two semaphores here at all, but can do
the same thing in more conventional and more effient way, by using a
single waitqueue and an atomic thread counter.
This gets us a little bit closer to
On Mon, 10 Dec 2018 15:25:32 +0100
Martin Kepplinger wrote:
> mma9551_gpio_config()'s switch statement sets the uninitialized pol_mask
> variable but doesn't have default settings. Said function can therefore
> be called in a way to use the uninitialized variable (at least in case
> enum
Corentin Labbe writes:
> This patchs adds a missing dependency on REGMAP_MMIO.
> This cause the following build failure on SPARC:
> drivers/soc/amlogic/meson-clk-measure.o: In function `meson_msr_probe':
> meson-clk-measure.c:(.text+0xc4): undefined reference to
> `__devm_regmap_init_mmio_clk'
Corentin Labbe writes:
> While sending a patch for drivers/soc/amlogic/Kconfig, I saw that
> getmaintainer.pl give nobody for it.
> This patchs adds drivers/soc/amlogic/ to amlogic maintainers.
>
> Signed-off-by: Corentin Labbe
nit: in Subject, I did a s/driver/drivers/
now queued for v4.21
On Mon, 10 Dec 2018, Sasha Levin wrote:
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
>
> The bot has tested the following trees: v4.19.8, v4.14.87, v4.9.144,
> v4.4.166, v3.18.128,
>
> v4.19.8:
Neil Armstrong writes:
> This patchset adds :
> - Optional reset properties in the midgard bindings
> - Mali T820 Node in Amlogic Meson GXM DTSI
>
> Christian Hewitt (1):
> arm64: dts: meson-gxm: Add Mali-T820 node
>
> Neil Armstrong (1):
> dt-bindings: gpu: mali-midgard: Add resets property
On Mon, Dec 10, 2018 at 12:58 PM Alexander Duyck
wrote:
>
> On Mon, 2018-12-10 at 11:43 -0800, Dan Williams wrote:
> > On Mon, Dec 10, 2018 at 11:35 AM Alexander Duyck
> > wrote:
> > >
> > > On Mon, 2018-12-10 at 10:58 -0800, Dan Williams wrote:
> > > > On Wed, Dec 5, 2018 at 9:25 AM Alexander
On Mon, Dec 10, 2018 at 9:59 PM Arnd Bergmann wrote:
>
> Building with CONFIG_KASAN=y when neither KASAN_GENERIC nor KASAN_SW_TAGS
> can be selected leads to a build error:
>
> arch/arm64/mm/kasan_init.c: In function 'kasan_pte_populate':
> arch/arm64/mm/kasan_init.c:106:28: error:
-Original Message-
> > makedumpfile doesn't have any switch which dumps VMCOREINFO from kcore
> > for now. (I'm thinking to have makedumpfile dump it as debug message,
> > though.)
>
> Might be useful as people are looking into using VMCOREINFO when
> debugging a live kernel...
Now
I had started the removal of semaphores in this driver without knowing
that Nicolas Saenz Julienne also worked on this. In case of the "remote
event" infrastructure, my solution seemed significantly better, so I'm
proposing this as a change on top.
The problem with using either semaphores or
Commit-ID: f4abaa98c4575cc06ea5e1a593e3bc2c8de8ef48
Gitweb: https://git.kernel.org/tip/f4abaa98c4575cc06ea5e1a593e3bc2c8de8ef48
Author: Michal Hocko
AuthorDate: Tue, 13 Nov 2018 19:49:10 +0100
Committer: Thomas Gleixner
CommitDate: Mon, 10 Dec 2018 22:07:02 +0100
x86/speculation/l1tf:
On 12/10/18 12:00 PM, Tim Chen wrote:
>> @@ -528,6 +538,9 @@ phys_addr_t swiotlb_tbl_map_single(struct device *hwdev,
>> dev_warn(hwdev, "swiotlb buffer is full (sz: %zd bytes)\n",
>> size);
>> return SWIOTLB_MAP_ERROR;
>> found:
>> +#ifdef CONFIG_DEBUG_FS
>> +io_tlb_used
Finally, here is the implementation Hans and I agreed on. Plus, all potential
users I could spot already converted. Renesas R-Car driver was added on top.
This series was tested on a Renesas Lager board (R-Car H2). I had to hack some
error cases into the code to verify the workings. I couldn't
On Mon, Dec 10, 2018 at 12:42:14PM -0800, Reinette Chatre wrote:
> Would you be ok if the above is changed to
>
> if (id < 0)
> return ERR_PTR(-ENOENT);
>
> as part of this patch?
Yap.
> Looking at rdtgroup_mondata_show() is does seem as though ENOENT is the
> actual intended error
Using the new 'is_suspended' flag, we now reject new transfers if the
adapter is already marked suspended.
Signed-off-by: Wolfram Sang
---
drivers/i2c/i2c-core-base.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/i2c/i2c-core-base.c b/drivers/i2c/i2c-core-base.c
index
On Mon, 10 Dec 2018 10:04:22 PST (-0800), paul.bur...@mips.com wrote:
Hi Dmitry,
On Mon, Dec 10, 2018 at 07:09:40PM +0300, Dmitry V. Levin wrote:
We decided to add .frame_pointer to struct ptrace_syscall_info just for
consistency with .instruction_pointer and .stack_pointer; I must have been
Rejecting transfers should be handled by the core.
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-brcmstb.c | 13 ++---
1 file changed, 2 insertions(+), 11 deletions(-)
diff --git a/drivers/i2c/busses/i2c-brcmstb.c b/drivers/i2c/busses/i2c-brcmstb.c
index
On Mon, 10 Dec 2018 at 22:03, Wolfram Sang
wrote:
>
> This flag was defined and checked but never set a value. Remove it.
>
> Signed-off-by: Wolfram Sang
Acked-by: Ard Biesheuvel
> ---
> drivers/i2c/busses/i2c-synquacer.c | 5 -
> 1 file changed, 5 deletions(-)
>
> diff --git
Rejecting transfers should be handled by the core. Also, this will
ensure proper locking which was forgotten in this open coded version
and make sure resume mark is set after enabling clocks (not before).
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-zx2967.c | 8 ++--
1 file
The pointer to a device is usually named 'dev'. These 'pdev' here look
much like copy errors. Fix them to avoid confusion.
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-sprd.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git
Rejecting transfers should be handled by the core. Also, this will
ensure proper locking which was forgotten in this open coded version.
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-exynos5.c | 11 ++-
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git
Rejecting transfers should be handled by the core. Also, this will
ensure proper locking which was forgotten in this open coded version.
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-s3c2410.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git
301 - 400 of 1203 matches
Mail list logo
