On Mon, Apr 29, 2019 at 4:21 PM Linus Torvalds
wrote:
>
> On Mon, Apr 29, 2019 at 12:55 PM Jann Horn wrote:
> >
> > ... I guess that already has a name, and it's called vfork(). (Well,
> > except that the Linux vfork() isn't a real vfork().)
>
> What?
>
> Linux vfork() is very much a real
> -Original Message-
> From: Jisheng Zhang [mailto:jisheng.zh...@synaptics.com]
> Sent: 2019年4月22日 15:55
> To: Gustavo Pimentel ; Z.q. Hou
>
> Cc: Vidya Sagar ; bhelg...@google.com;
> robh...@kernel.org; mark.rutl...@arm.com; thierry.red...@gmail.com;
> jonath...@nvidia.com;
On Tue, 23 Apr 2019 23:21:00 PDT (-0700), Christoph Hellwig wrote:
}
+
+bool arch_match_cpu_phys_id(int cpu, u64 phys_id)
+{
+ return phys_id == cpuid_to_hartid_map(cpu);
+}
/* Unsupported */
Please keep an empty line after function bodys.
Otherwise looks good:
Reviewed-by: Christoph
Hi Doug,
On Mon, 29 Apr 2019 18:21:32 -0400 Doug Ledford wrote:
>
> Sorry, I forgot to back that head commit out. Once Linus committed his
> fix the one in the rdma tree was superfluous (and wrong anyway).
No worries - I even managed to choose the correct one by chance! :-)
--
Cheers,
Hi Arnd,
Thanks a lot for your comments!
> -Original Message-
> From: Arnd Bergmann [mailto:a...@arndb.de]
> Sent: 2019年4月12日 22:42
> To: Z.q. Hou
> Cc: linux-...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> devicet...@vger.kernel.org; linux-kernel@vger.kernel.org;
>
Hi Arnd,
Thanks a lot for your comments!
> -Original Message-
> From: Arnd Bergmann [mailto:a...@arndb.de]
> Sent: 2019年4月12日 22:39
> To: Z.q. Hou
> Cc: linux-...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> devicet...@vger.kernel.org; linux-kernel@vger.kernel.org;
>
Hi Dmitry,
Looks good to me. But, just I have one minor comment
about '8' divider value in the tegra_devfreq_get_dev_status().
On the next version, you better to add the comment about the meaning
of '8' divider value.
Reviewed-by: Chanwoo Choi
On 19. 4. 18. 오전 7:29, Dmitry Osipenko wrote:
>
Hi all,
After merging the clk tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/clk/imx/clk-pllv3.c:453:21: warning: this statement may fall through
[-Wimplicit-fallthrough=]
pll->denom_offset = PLL_IMX7_DENOM_OFFSET;
^
Currently error return from kobject_init_and_add() is not followed by a
call to kobject_put(). This means there is a memory leak.
Add call to kobject_put() in error path of kobject_init_and_add().
Signed-off-by: Tobin C. Harding
---
Resend with SOB tag.
kernel/sched/cpufreq_schedutil.c | 1
Quoting Mike Looijmans (2019-04-27 02:42:56)
> On 27-04-19 02:44, Stephen Boyd wrote:
> > Quoting Mike Looijmans (2019-04-25 23:51:15)
> >> On 26-04-19 01:04, Stephen Boyd wrote:
> +
> +Optional properties:
> +- silabs,pll-m-num, silabs,pll-m-den: Numerator and denominator for PLL
>
The correct cleanup function after a call to kobject_init_and_add() has
succeeded is kobject_del() _not_ kobject_put(). kobject_del() calls
kobject_put().
Use correct cleanup function when removing a kobject.
Signed-off-by: Tobin C. Harding
---
kernel/livepatch/core.c | 8 +++-
1 file
Hi,
Currently there are a few places in kernel/livepatch/ which do not
correctly use kobject_init_and_add().
An error return from kobject_init_and_add() requires a call to
kobject_put().
The cleanup function after a successful call to kobject_init_and_add()
is kobject_del().
This set is part
Currently error return from kobject_init_and_add() is not followed by a
call to kobject_put(). This means there is a memory leak.
Add call to kobject_put() in error path of kobject_init_and_add().
Signed-off-by: Tobin C. Harding
---
kernel/livepatch/core.c | 12 +---
1 file changed, 9
Hi,
On 19. 4. 18. 오전 7:29, Dmitry Osipenko wrote:
> Reset hardware, disable ACTMON clock, release OPP's and handle all
> possible error cases correctly, maintaining the correct tear down
> order. Also use devm_platform_ioremap_resource() which is now available
> in the kernel.
>
> Signed-off-by:
On Mon, Apr 29, 2019 at 05:10:24PM -0700, Matthias Kaehlcke wrote:
> From: Balakrishna Godavarthi
>
> From: Balakrishna Godavarthi
>
> Latest qualcomm chips are not sending an command complete event for
> every firmware packet sent to chip. They only respond with a vendor
> specific event for
Currently error return from kobject_init_and_add() is not followed by a
call to kobject_put(). This means there is a memory leak.
Add call to kobject_put() in error path of kobject_init_and_add().
---
kernel/sched/cpufreq_schedutil.c | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Balakrishna Godavarthi
From: Balakrishna Godavarthi
Latest qualcomm chips are not sending an command complete event for
every firmware packet sent to chip. They only respond with a vendor
specific event for the last firmware packet. This optimization will
decrease the BT ON time. Due to
From: Randy Dunlap
Print a "begin trace" + oops ID number to match the current
"end trace" + oops ID number.
Example:
[ 193.314027] ---[ begin trace cf01af0ff0925003 ]---
[ 193.314032] general protection fault: [#1] PREEMPT SMP KASAN PTI
[ 193.314046] CPU: 2 PID: 2884 Comm: bash
On Mon, Apr 29, 2019 at 03:22:09PM -0700, Linus Torvalds wrote:
> On Mon, Apr 29, 2019 at 3:08 PM Sean Christopherson
> wrote:
> >
> > FWIW, Lakemont (Quark) doesn't block NMI/SMI in the STI shadow, but I'm
> > not sure that counters the "horrible errata" statement ;-). SMI+RSM saves
> > and
On 19. 4. 18. 오전 7:29, Dmitry Osipenko wrote:
> There is no guarantee that interrupt handling isn't running in parallel
> with tegra_actmon_disable_interrupts(), hence it is necessary to protect
> DEV_CTRL register accesses and clear IRQ status with ACTMON's IRQ being
> disabled in the Interrupt
Hi Matteo,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on net/master]
[also build test WARNING on v5.1-rc7]
[cannot apply to next-20190429]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
On Tue, 23 Apr 2019 17:02:26 PDT (-0700), atish.pa...@wdc.com wrote:
nosmp command line option sets max_cpus to zero. No secondary harts
will boot if this is enabled. But present cpu mask will still point to
all possible masks.
Fix present cpu mask for nosmp usecase.
Signed-off-by: Atish Patra
Hi Shawn,
Today's linux-next merge of the imx-mxs tree got a conflict in:
arch/arm64/configs/defconfig
between commit:
7b0d021fbe41 ("arm64: defconfig: enable PCIE_ALTERA")
from the arm-soc tree and commit:
2b4fd225df89 ("arm64: defconfig: Enable CONFIG_SPI_IMX")
from the imx-mxs
Hi Matteo,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on net/master]
[also build test WARNING on v5.1-rc7]
[cannot apply to next-20190429]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
On Tue, 23 Apr 2019 16:25:06 PDT (-0700), atish.pa...@wdc.com wrote:
Currently, last stage boot loaders such as U-Boot can accept only
uImage which is an unnecessary additional step in automating boot flows.
Add a simple image header that boot loaders can parse and directly
load kernel flat
On Tue, 23 Apr 2019 23:20:20 PDT (-0700), Christoph Hellwig wrote:
On Tue, Apr 23, 2019 at 02:22:53PM -0700, Nick Desaulniers wrote:
Towards the goal of removing cc-ldoption, it seems that --hash-style=
was added to binutils 2.17.50.0.2 in 2006. The minimal required version
of binutils for the
On Mon, Apr 29, 2019 at 04:21:31PM -0700, Matthias Kaehlcke wrote:
> Firmware download to the WCN3990 often fails with a 'TLV response size
> mismatch' error:
>
> [ 133.064659] Bluetooth: hci0: setting up wcn3990
> [ 133.489150] Bluetooth: hci0: QCA controller version 0x02140201
> [
Hi all,
After merging the arm-soc tree, today's linux-next build
(x86_64 allmodconfig) produced this warning:
drivers/clocksource/timer-ixp4xx.c:78:20: warning: 'ixp4xx_read_sched_clock'
defined but not used [-Wunused-function]
static u64 notrace ixp4xx_read_sched_clock(void)
On Mon, 29 Apr 2019 04:55:26 PDT (-0700), Christoph Hellwig wrote:
Any comments? It would be nice to get this in for this merge window
to make my life simpler with the RISC-V tree next merge window..
On Tue, Apr 23, 2019 at 06:30:57PM +0200, Christoph Hellwig wrote:
Hi all,
these two patches
Firmware download to the WCN3990 often fails with a 'TLV response size
mismatch' error:
[ 133.064659] Bluetooth: hci0: setting up wcn3990
[ 133.489150] Bluetooth: hci0: QCA controller version 0x02140201
[ 133.495245] Bluetooth: hci0: QCA Downloading qca/crbtfw21.tlv
[ 133.507214] Bluetooth:
Rename STATE_IN_BAND_SLEEP_ENABLED to QCA_IBS_ENABLED. The constant
represents a flag (multiple flags can be set at once), not a unique
state of the controller or driver.
Also make the flag an enum value instead of a pre-processor constant
(more flags will be added to the enum group by another
Hi Mike,
> >This barrier only applies to the read-modify-write operations; in
> >particular, it does not apply to the atomic_read() primitive.
> >
> >Replace the barrier with an smp_mb().
>
> This is one of a couple of barrier issues that we are currently looking into.
>
> See:
>
> [PATCH
On Tue, Apr 16, 2019 at 04:58:12PM +0200, Fabien Dessenne wrote:
> Document the ML-AHB interconnect for stm32 SoCs.
>
> Signed-off-by: Fabien Dessenne
> ---
> .../devicetree/bindings/arm/stm32/mlahb.txt| 37
> ++
> 1 file changed, 37 insertions(+)
> create mode
This is very interesting. How does the code handle cgroup hierarchies?
For example, if we have:
cgroup0 is the cgroup root
cgroup1 whose parent is cgroup0
cgroup2 whose parent is cgroup1
we have task0 running in cgroup0, task1 in cgroup1, task2 in cgroup2
and then a perf command line like:
perf
Quoting Stephen Rothwell (2019-04-29 14:40:24)
> Hi all,
>
> Commit
>
> 01d0a541ff4b ("clk: imx: correct i.MX7D AV PLL num/denom offset")
>
> is missing a Signed-off-by from its committer.
>
Thanks. Fixed.
Quoting Paul Walmsley (2019-04-29 12:42:07)
> Hi Stephen,
>
> On Fri, 26 Apr 2019, Paul Walmsley wrote:
>
> > On Fri, 26 Apr 2019, Stephen Boyd wrote:
> >
> > > Quoting Paul Walmsley (2019-04-11 01:27:32)
> > > > Add common library code for the Analog Bits Wide-Range PLL (WRPLL) IP
> > > >
Quoting Paul Cercueil (2019-04-29 13:53:11)
> Hi Stephen,
>
> Le jeu. 18 avril 2019 à 23:58, Stephen Boyd a
> écrit :
> > Quoting Paul Cercueil (2019-04-17 04:24:20)
> >> The pixel clock is directly connected to the output of the PLL, and
> >> not
> >> to the /2 divider.
> >>
> >> Cc:
Quoting Paul Walmsley (2019-04-11 01:27:36)
> diff --git a/drivers/clk/sifive/Makefile b/drivers/clk/sifive/Makefile
> new file mode 100644
> index ..74d58a4c0756
> --- /dev/null
> +++ b/drivers/clk/sifive/Makefile
> @@ -0,0 +1 @@
Any SPDX for this file?
>
Quoting Paul Walmsley (2019-04-11 01:27:34)
> Add DT binding documentation for the Linux driver for the SiFive
> PRCI clock & reset control IP block, as found on the SiFive
> FU540 chip.
>
> This version includes changes requested by Stephen Boyd
> and Rob Herring , and
> fixes some errors in
Hi James,
What's the best way forward with this? I'm still not entirely clear on
how it can be implemented purely as an LSM, but if you have ideas on
what sort of implementation you'd prefer I'm happy to work on that.
--
The following changes since commit 6a1afffb08ce5f9fb9ccc20f7ab24846c0142984:
selinux: fix NULL dereference in policydb_destroy()
(2019-03-18 12:19:48 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
tags/selinux-pr-20190429
for you
Most of these are hand-written, but xilinx-xadc.py is auto-generated by
binding_to_py.py as an example of the use of that tool.
This is part of a proof-of-concept device-tree validator. See the patch
on the dtc mailing list for details:
RFC: Python-based device-tree validation
Signed-off-by:
Sure, I will.
Thanks,
> -Original Message-
> From: Linux-nvme [mailto:linux-nvme-boun...@lists.infradead.org] On
> Behalf Of Chaitanya Kulkarni
> Sent: Tuesday, April 30, 2019 7:14 AM
> To: Minwoo Im
> Cc: linux-kernel@vger.kernel.org; Christoph Hellwig; linux-
>
On Mon, Apr 29, 2019 at 10:52 AM Greg KH wrote:
> On Mon, Apr 29, 2019 at 10:47:00AM -0400, Paul Moore wrote:
> > On Mon, Apr 29, 2019 at 10:09 AM Greg KH wrote:
> > > On Mon, Apr 29, 2019 at 10:02:29AM -0400, Paul Moore wrote:
> > > > On Mon, Apr 29, 2019 at 8:40 AM Greg KH
> > > > wrote:
> >
On Mon, Apr 29, 2019 at 11:00:05AM +0200, Ludovic Desroches wrote:
> Hello Raag,
>
> On Tue, Apr 23, 2019 at 01:06:48PM +0530, Raag Jadav wrote:
> > External E-Mail
> >
> >
> > Performing i2c write operation while SDA or SCL line is held
> > or grounded by slave device, we go into infinite
Hi Mathieu,
On Thu, Apr 25, 2019 at 10:21:32AM -0400, Mathieu Desnoyers wrote:
> I've tried to figure out if we could find a way to have RSEQ_SIG left
> undefined
> if it's not on the plain mips environment, but could not find anything that
> would be #defined on plain mips, but #undefined on
On Mon, Apr 29, 2019 at 3:08 PM Sean Christopherson
wrote:
>
> FWIW, Lakemont (Quark) doesn't block NMI/SMI in the STI shadow, but I'm
> not sure that counters the "horrible errata" statement ;-). SMI+RSM saves
> and restores STI blocking in that case, but AFAICT NMI has no such
> protection and
On Tue, Apr 16, 2019 at 01:42:15PM +0800, Jitao Shi wrote:
> Update device tree binding documentation for the dsi for
> Mediatek MT8183 SoCs.
>
> Signed-off-by: Jitao Shi
> ---
> .../devicetree/bindings/display/mediatek/mediatek,dsi.txt | 2 +-
> 1 file changed, 1 insertion(+), 1
In the sysctl code the proc_dointvec_minmax() function is often used to
validate the user supplied value between an allowed range. This function
uses the extra1 and extra2 members from struct ctl_table as minimum and
maximum allowed value.
On sysctl handler declaration, in every source file there
Enablement of AMD's Secure Memory Encryption feature is determined
very early after start_kernel() is entered. Part of this procedure
involves scanning the command line for the parameter 'mem_encrypt'.
To determine intended state, the function sme_enable() uses library
functions
On Tue, Apr 23, 2019 at 5:28 AM Matteo Croce wrote:
>
> On April 19, 2019 10:07:14 AM GMT+09:00, Matthew Wilcox
> wrote:
> > On Fri, Apr 19, 2019 at 09:17:17AM +0900, Matteo Croce wrote:
> > > > extern const int sysctl_zero;
> > > > /* comment goes here */
> > > > #define SYSCTL_ZERO ((void
On Tue, 2019-04-30 at 08:13 +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the rdma-fixes tree got a conflict in:
>
> drivers/infiniband/core/uverbs_main.c
>
> between commit:
>
> 6a5c5d26c4c6 ("rdma: fix build errors on s390 and MIPS due to bad ZERO_PAGE
> use")
On Mon, Apr 15, 2019 at 01:43:54PM +0300, Georgi Djakov wrote:
> The Qualcomm QCS404 platform has several buses that could be controlled
> and tuned according to the bandwidth demand.
>
> Signed-off-by: Georgi Djakov
> ---
>
> v2:
> - No changes.
>
> .../bindings/interconnect/qcom,qcs404.txt
Hi Minwoo,
Can you please resend this patch with the suggested change ?
On 04/29/2019 10:58 AM, kbuild test robot wrote:
> From: kbuild test robot
>
> drivers/nvme/target/discovery.c:375:1-3: WARNING: PTR_ERR_OR_ZERO can be used
>
>
> Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
Hi all,
Today's linux-next merge of the rdma-fixes tree got a conflict in:
drivers/infiniband/core/uverbs_main.c
between commit:
6a5c5d26c4c6 ("rdma: fix build errors on s390 and MIPS due to bad ZERO_PAGE
use")
from Linus' tree and commit:
d79a26b99f5f ("RDMA/uverbs: Fix compilation
On Sun, Apr 14, 2019 at 10:26:33PM -0300, Matheus Castello wrote:
> For configure low level state of charge threshold alert signaled from
> max17040 we add "maxim,alert-soc-level" property.
>
> Signed-off-by: Matheus Castello
> ---
> .../power/supply/max17040_battery.txt | 24
On Mon, Apr 29, 2019 at 11:57 AM Andy Lutomirski wrote:
> >
> > Otherwise you could never trust the whole sti shadow thing - and it very
> > much is part of the architecture.
>
> Is this documented somewhere?
Btw, if you really don't trust the sti shadow despite it going all the
way back to the
The pull request you sent on Mon, 29 Apr 2019 12:58:36 -0700:
> https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git
> tags/seccomp-v5.1-rc8
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/83a50840e72a5a964b4704fcdc2fbb2d771015ab
Thank you!
--
On Mon, Apr 29, 2019 at 01:16:10PM -0700, Linus Torvalds wrote:
> On Mon, Apr 29, 2019 at 12:02 PM Linus Torvalds
> wrote:
> >
> > If nmi were to break it, it would be a cpu bug. I'm pretty sure I've
> > seen the "shadow stops even nmi" documented for some uarch, but as
> > mentioned it's not
On Mon, 29 Apr 2019 14:38:35 -0700
Linus Torvalds wrote:
> On Mon, Apr 29, 2019 at 1:30 PM Steven Rostedt wrote:
> >
> > The update from "call custom_trampoline" to "call iterator_trampoline"
> > is where we have an issue.
>
> So it has never worked. Just tell people that they have two
On Mon, 29 Apr 2019 22:36:30 +0200,
Mika Westerberg wrote:
>
> On Mon, Apr 29, 2019 at 11:13:47PM +0300, Mika Westerberg wrote:
> > On Mon, Apr 29, 2019 at 10:03:00PM +0200, Michael Hirmke wrote:
> > > Hi all,
> > >
> > > >On Mon, Apr 29, 2019 at 09:47:15PM +0200, Takashi Iwai wrote:
> > > >>
On Sun, Apr 14, 2019 at 11:20:07PM +0300, Dmitry Osipenko wrote:
> Add device-tree binding for NVIDIA Tegra30 External Memory Controller.
> The binding is based on the Tegra124 EMC binding since hardware is
> similar, although there are couple significant differences.
My comments on Tegra124
> On Mon, Apr 15, 2019 at 02:30:30PM -0700, Sowjanya Komatineni wrote:
> > This patch exports spi_set_cs of the spi core to allow SPI masters to
> > use when gpio based chip select is needed.
>
> This isn't really what I meant when I said it'd be good to use the core GPIO
> code - this function
On Sun, 21 Apr 2019 at 06:46, Leo Yan wrote:
>
> On Sat, Apr 20, 2019 at 10:00:35PM +0800, Wanglai Shi wrote:
> > This patch adds DT bindings for the CoreSight trace components
> > on hi3660, which is used by 96boards Hikey960.
> >
> > Signed-off-by: Wanglai Shi
>
> Reviewed this patch and
Thank you for your feedback Wolfram. I have addressed your comments.
Concerning your questions:
"Why can't we use i2c_smbus_write_block_data()?"
i2c_smbus_write_block_data() does not allow me to pass the
requester_i2c_addr argument. Instead, it uses the
client->addr.
The client->addr in this
Support receiving IPMB requests on a Satellite MC from the BMC.
Once a response is ready, this driver will send back a response
to the BMC via the IPMB channel.
Signed-off-by: Asmaa Mnebhi
---
drivers/char/ipmi/Kconfig| 8 +
drivers/char/ipmi/Makefile | 1 +
In rxrpc_destroy_all_calls(), there are two phases: (1) make sure the
->calls list is empty, emitting error messages if not, and (2) wait for the
RCU cleanup to happen on outstanding calls (ie. ->nr_calls becomes 0).
To avoid taking the call_lock, the function prechecks ->calls and if empty,
it
On Sun 28-04-19 13:39:21, Chengguang Xu wrote:
> Set init_needed flag only when successfully getting dquot,
> so that we can skip unnecessary subsequent operation.
>
> Signed-off-by: Chengguang Xu
Thanks for the patch but I don't think it's really useful. It will be very
rare that we race with
Dear Friend,
I know this means of communication may not be morally right to you as a person
but I also have had a great thought about it and I have come to this conclusion
which I am about to share with you.
INTRODUCTION: I am a banker and in one way or the other was hoping you will
cooperate
From: Prakhar Srivastava
added a new ima policy func buffer_check, and ima hook to
measure the buffer hash into ima logs.
Signed-off-by: Prakhar Srivastava
---
Documentation/ABI/testing/ima_policy | 1 +
include/linux/ima.h | 5 ++
security/integrity/ima/ima.h | 1
From: Prakhar Srivastava
add the buffer to the xattr for a buffer case
Signed-off-by: Prakhar Srivastava
---
security/integrity/ima/ima_main.c | 37 ---
security/integrity/ima/ima_template_lib.c | 3 +-
security/integrity/integrity.h| 1 +
3 files
From: Prakhar Srivastava
added LSM hook to call ima_buffer_check
Signed-off-by: Prakhar Srivastava
---
include/linux/lsm_hooks.h | 3 +++
include/linux/security.h | 3 +++
kernel/kexec_internal.h | 4 +++-
security/security.c | 6 ++
4 files changed, 15 insertions(+), 1
Hi Greg and Tejun,
is it acceptable for a driver to expose sysfs attr files for ECDSA
signature generation?
The thing is that
1. AFAIK there isn't another API for userspace to do this.
There were attempts in 2015 to expose akcipher via netlink to
userspace, but the patchseries were
From: Prakhar Srivastava
For Kexec scenario(kexec_file_load) cmdline args are passed to the
next kerenel. These cmldine args used to load the next kernel can
have undesired/unwanted configs. To guard against any unwanted cmdline
args being passed to the next kernel. The current kernel should
From: Prakhar Srivastava
prepend the kernel file name to kexec_cmdline
before measuring the buffer.
Signed-off-by: Prakhar Srivastava
---
kernel/kexec_core.c | 57 +
kernel/kexec_file.c | 14 +++
2 files changed, 71 insertions(+)
diff
Hi Ulf,
In commit
98bc384ce704 ("mmc: core: fix possible use after free of host")
Fixes tag
Fixes: 1ed21719448("mmc: core: fix error path in mmc_host_alloc")
has these problem(s):
- missing space between the SHA1 and the subject
- SHA1 should be at least 12 digits long
Can be
On Fri 26-04-19 11:08:44, Matthew Garrett wrote:
> On Thu, Apr 25, 2019 at 10:25 PM Michal Hocko wrote:
> >
> > On Thu 25-04-19 13:39:01, Matthew Garrett wrote:
> > > Yes, given MADV_DONTDUMP doesn't imply mlock I thought it'd be more
> > > consistent to keep those independent.
> >
> > Do we want
On Mon 29-04-19 10:13:32, Shakeel Butt wrote:
[...]
> /*
>* For queues with unlimited length lost events are not expected and
>* can possibly have security implications. Avoid losing events when
>* memory is short.
> + *
> + * Note: __GFP_NOFAIL takes
Hi all,
Commit
01d0a541ff4b ("clk: imx: correct i.MX7D AV PLL num/denom offset")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgpgu5hjejj3R.pgp
Description: OpenPGP digital signature
Hi Mark,
I don't see below patches that I see as applied in latest linux-next.
Can you please confirm if they are applied?
Applied "spi: tegra114: fix PIO transfer" to the spi tree
Applied "spi: expand mode support" to the spi tree
Thanks
Sowjanya
> The patch
> spi: tegra114: fix PIO
On Mon, Apr 29, 2019 at 1:38 PM Florian Weimer wrote:
>
> In Linux-as-the-ABI (as opposed to Linux-as-the-implementation), vfork
> is sometimes implemented as fork, so applications cannot rely on the
> vfork behavior regarding the stopped parent and the shared address
> space.
What broken
On Mon, Apr 29, 2019 at 1:30 PM Steven Rostedt wrote:
>
> The update from "call custom_trampoline" to "call iterator_trampoline"
> is where we have an issue.
So it has never worked. Just tell people that they have two chocies:
- you do the careful rewriting, which takes more time
- you do it
On 29.04.19 21:44, Frank Rowand wrote:
> On 4/16/19 12:57 PM, Enrico Weigelt, metux IT consult wrote:
>> we don't need to build in oftree probing stuff when oftree isn't
>> enabled at all.
>>
>> Signed-off-by: Enrico Weigelt, metux IT consult
>> ---
>> drivers/input/keyboard/gpio_keys_polled.c |
On Fri, Apr 12, 2019 at 05:02:11PM +1200, Chris Packham wrote:
> Add binding documentation for spi-mux-gpio which is a slightly more
> complicated hardware implementation of using gpios to steer SPI chip
> selects.
>
> Signed-off-by: Chris Packham
> ---
>
CONFIG_DEBUG_TLBFLUSH was added in
'commit 3df3212f9722 ("x86/tlb: add tlb_flushall_shift knob into debugfs")'
to support tlb_flushall_shift knob. The knob was removed in
'commit e9f4e0a9fe27 ("x86/mm: Rip out complicated, out-of-date, buggy
TLB flushing")'.
However, the debug option was never
The TLB flush counters under vmstat seems to be very helpful while
debugging TLB flush performance in RISC-V.
Add the Kconfig option only for debug kernels.
Signed-off-by: Atish Patra
---
arch/riscv/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/riscv/Kconfig
The TLB flush counters under vmstat seems to be very helpful while
debugging TLB flush performance in RISC-V.
Update the counters in every TLB flush methods respectively.
Signed-off-by: Atish Patra
---
arch/riscv/include/asm/tlbflush.h | 5 +
arch/riscv/mm/tlbflush.c | 12
On 4/29/19 1:06 PM, Ingo Molnar wrote:
* Atish Patra wrote:
CONFIG_DEBUG_TLBFLUSH was added in 'commit 3df3212f9722 ("x86/tlb: add
tlb_flushall_shift knob into debugfs")' to support tlb_flushall_shift
knob. The knob was removed in 'commit e9f4e0a9fe27 ("x86/mm: Rip out
complicated,
The RISC-V patch (2/3) is based on Gary's TLB flush patch series
https://patchwork.kernel.org/project/linux-riscv/list/?series=97315
The x86 kconfig fix patch(1/3) can be applied separately.
Chnages from v2->v3:
1. Fixed typos and commit text formatting.
Changes from v1->v2:
1. Move the arch
>-Original Message-
>From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma-
>ow...@vger.kernel.org] On Behalf Of Andrea Parri
>Sent: Monday, April 29, 2019 4:15 PM
>To: linux-kernel@vger.kernel.org
>Cc: Andrea Parri ;
>sta...@vger.kernel.org; Dalessandro, Dennis
>; Marciniszyn, Mike
>;
804::dhcp root=/dev/ram0 user=lkp
> job=/lkp/jobs/scheduled/vm-snb-quantal-ia32-804/trinity-300s-quantal-core-i386-2019-04-26.cgz-02519fa3c43-20190429-62375-116iczn-1.yaml
> ARCH=x86_64 kconfig=x86_64-randconfig-s3-04261012
> branch=linux-devel/devel-hourly-2019042607
> commit=02519fa3c431
On 4/29/19 3:51 PM, Borislav Petkov wrote:
> [CAUTION: External Email]
>
> On Mon, Apr 29, 2019 at 08:16:07PM +, Gary R Hook wrote:
>> Yes, option 4 would be a combination of using a local copy of strncmp()
>
> Why the local copy?
Seemed suitable, since it's tiny. But I'm not married to the
On Thu, 11 Apr 2019 14:38:47 -0500, Dan Murphy wrote:
> Introduce the bindings for the Texas Instruments LP5036, LP5030, LP5024 and
> the LP5018
> RGB LED device driver. The LP5036/3024/18 can control RGB LEDs individually
> or as part of a control bank group. These devices have the ability
>
On Mon 29-04-19 13:31:58, Debabrata Banerjee wrote:
> Fixes:
> commit 1e381f60dad9 ("ext4: do not allow journal_opts for fs w/o journal")
>
> Instead of removing EXT4_MOUNT_JOURNAL_CHECKSUM from s_def_mount_opt as
> I assume was intended, all other options were blown away leading to
>
Davidlohr Bueso wrote:
> On Sun, 28 Apr 2019, Eric Wong wrote:
>
> > Just running one test won't trigger since it needs a busy
> > machine; but:
> >
> > make test/mgmt_auto_adjust.log
> > (and "rm make test/mgmt_auto_adjust.log" if you want to rerun)
>
> fyi no luck reproducing on both
On Mon, Apr 29, 2019 at 10:50 PM Florian Weimer wrote:
>
> * Jann Horn:
>
> >> int clone_temporary(int (*fn)(void *arg), void *arg, pid_t *child_pid,
> >> )
> >>
> >> and then you'd use it like this to fork off a child process:
> >>
> >> int spawn_shell_subprocess_(void *arg) {
> >> char
Hi Stephen,
Le jeu. 18 avril 2019 à 23:58, Stephen Boyd a
écrit :
Quoting Paul Cercueil (2019-04-17 04:24:20)
The pixel clock is directly connected to the output of the PLL, and
not
to the /2 divider.
Cc: sta...@vger.kernel.org
Fixes: 226dfa4726eb ("clk: Add Ingenic jz4725b CGU
On Mon, Apr 15, 2019 at 05:04:19PM +0100, Suzuki K Poulose wrote:
> Coresight device connections are a bit complicated and is not
> exposed currently to the user. One has to look at the platform
> descriptions (DT bindings or ACPI bindings) to make an understanding.
> Given the new naming scheme,
* Jann Horn:
>> int clone_temporary(int (*fn)(void *arg), void *arg, pid_t *child_pid,
>> )
>>
>> and then you'd use it like this to fork off a child process:
>>
>> int spawn_shell_subprocess_(void *arg) {
>> char *cmdline = arg;
>> execl("/bin/sh", "sh", "-c", cmdline);
>> return -1;
>> }
On Mon, Apr 29, 2019 at 08:16:07PM +, Gary R Hook wrote:
> Yes, option 4 would be a combination of using a local copy of strncmp()
Why the local copy?
> and disabling instrumentation (KASAN, KCOV, whatever) for
> arch/x86/lib/cmdline.c when SME is enabled.
I think this should suffice. You
101 - 200 of 755 matches
Mail list logo
