On Mon, 29 Apr 2019, Matthew Garrett wrote:
> 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.
It can't be implemented
On Fri, May 3, 2019 at 3:20 AM Ingo Molnar wrote:
> So what might work better is if we defined a Rust dialect that used C
> syntax. I.e. the end result would be something like the 'c2rust' or
> 'citrus' projects, where code like this would be directly translatable to
> Rust:
>
> void gz_compress(F
On Thu, May 02, 2019 at 04:52:21PM -0400, Joel Savitz wrote:
>
> +static int prctl_get_tasksize(void __user * uaddr)
> +{
> + unsigned long task_size = TASK_SIZE;
> + return copy_to_user(uaddr, &task_size, sizeof(unsigned long))
> + ? -EFAULT : 0;
> +}
Won't be possib
From: "Gustavo L. F. Walbon"
The issue was showing "Mitigation" message via sysfs whatever the state of
"RFI Flush", but it should show "Vulnerable" when it is disabled.
If you have "L1D private" feature enabled and not "RFI Flush" you are
vulnerable to meltdown attacks.
"RFI Flush" is the key
On 5/2/2019 5:47 AM, Maxim Levitsky wrote:
Note that currently the number of hw queues reserved for mdev,
has to be pre determined on module load.
(I used to allocate the queues dynamicaly on demand, but
recent changes to allocate polled/read queues made
this somewhat difficult, so I dropped
Hi!
> On Tue, Apr 16, 2019 at 10:42:30AM +0200, Enric Balletbo i Serra wrote:
> > On 16/4/19 9:19, Pavel Machek wrote:
> > >> This patch exposes a new property, similar to input current limit, to
> > >> re-configure the maximum voltage from the external supply at runtime
> > >> based on system-lev
On Thu, 2 May 2019 20:37:31 +0200
Viktor Rosendahl wrote:
> > Instead of this being turned into a nop, don't have a kconfig option
> > but instead have this call into the trace_irqsoff.c code, and depending
> > on what the options are, it should stop it. Of course, this would need
> > to be smar
On Thu, May 02, 2019 at 05:01:38PM -0400, Waiman Long wrote:
>
> What did you change in v2 versus v1?
Seems unsigned long long has been changed to unsigned long.
[...]
> >
> > >>Better, if you can avoid cast.
> > >>Would compiler warn if you use for example rol16(client->addr, 1) &
> GENMASK(7, 0); or something like it?
> > I thought it wouldn't be too much of an issue to use typecast here since
> > other
> existing ipmi drivers use typecasting: bt-bmc.c,
On Thu, May 2, 2019 at 2:07 PM James Morris wrote:
> One possible direction is to (as previously mentioned) assign IDs to each
> callsite and be able to check this ID against a simple policy array
> (allow/deny). The default policy choices could be reduced to 'all' or
> 'none' during kconfig, and
Hi Tim,
Missatge de Tim Wawrzynczak del dia dj., 2
de maig 2019 a les 18:10:
>
> The new debugfs entry 'uptime' is being made available to userspace so that
> a userspace daemon can synchronize EC logs with host time.
>
> Signed-off-by: Tim Wawrzynczak
> ---
> Enric, is there something I can do
On Thu, 2019-05-02 at 15:12 -0600, Heitke, Kenneth wrote:
>
> On 5/2/2019 5:47 AM, Maxim Levitsky wrote:
> > Note that currently the number of hw queues reserved for mdev,
> > has to be pre determined on module load.
> >
> > (I used to allocate the queues dynamicaly on demand, but
> > recent chan
Yes, this the change, thanks to the suggestion of Yury Norov.
I also now explicitly mention the expected userspace destination type
in the manpage patch.
Best,
Joel Savitz
On Thu, May 2, 2019 at 5:10 PM Cyrill Gorcunov wrote:
>
> On Thu, May 02, 2019 at 05:01:38PM -0400, Waiman Long wrote:
> >
On Thu, May 02, 2019 at 04:52:21PM -0400, Joel Savitz wrote:
> When PR_GET_TASK_SIZE is passed to prctl, the kernel will attempt to
> copy the value of TASK_SIZE to the userspace address in arg2.
>
> Suggested-by: Alexey Dobriyan
> Signed-off-by: Joel Savitz
> ---
> include/uapi/linux/prctl.h |
The code was setting the bit 21 of the CPCCR register to use a divider
of 2 for the "pll half" clock, and clearing the bit to use a divider
of 1.
This is the opposite of how this register field works: a cleared bit
means that the /2 divider is used, and a set bit means that the divider
is 1.
Rest
The main clocks (cclk, h0clk, h1clk, h2clk, c1clk, pclk) were using
incorrect dividers, and thus reported an incorrect rate.
Signed-off-by: Paul Cercueil
---
drivers/clk/ingenic/jz4770-cgu.c | 34 ++--
1 file changed, 28 insertions(+), 6 deletions(-)
diff --git a/dri
Some clocks provided on Ingenic SoCs have dividers, whose hardware value
as written in the register cannot be expressed as an affine function
to the actual divider value.
For instance, for the CPU clock on the JZ4770, the dividers are coded as
follows:
--
| Bits | Div
The main clocks (cclk, hclk, pclk, mclk, lcd) were using
incorrect dividers, and thus reported an incorrect rate.
Signed-off-by: Paul Cercueil
---
drivers/clk/ingenic/jz4740-cgu.c | 29 -
1 file changed, 24 insertions(+), 5 deletions(-)
diff --git a/drivers/clk/ingen
The main clocks (cclk, hclk, pclk, mclk, ipu) were using
incorrect dividers, and thus reported an incorrect rate.
Signed-off-by: Paul Cercueil
---
drivers/clk/ingenic/jz4725b-cgu.c | 29 -
1 file changed, 24 insertions(+), 5 deletions(-)
diff --git a/drivers/clk/inge
On Thu, May 02, 2019 at 04:52:20PM -0400, Joel Savitz wrote:
> In the mainline kernel, there is no quick mechanism to get the virtual
> memory size of the current process from userspace.
>
> Despite the current state of affairs, this information is available to the
> user through several means, on
On 4/8/19 9:26 AM, Will Deacon wrote:
> On Fri, Apr 05, 2019 at 09:50:47AM -0700, Florian Fainelli wrote:
>> Broadcom's Brahma-B53 CPUs support the same type of events that the
>> Cortex-A53 supports, recognize its CPUID and map it to the cortex-a53
>> events.
>>
>> Signed-off-by: Florian Fainelli
> -Original Message-
> From: Asmaa Mnebhi
> Sent: Thursday, May 02, 2019 9:38 PM
> To: miny...@acm.org; w...@the-dreams.de; Vadim Pasternak
> ; Michael Shych
> Cc: Asmaa Mnebhi ; linux-kernel@vger.kernel.org;
> linux-...@vger.kernel.org
> Subject: [PATCH v5 1/1] Add support for IPMB dr
On Tue, 30 Apr 2019 20:58:59 +0200, Nicolas Saenz Julienne wrote:
> Some devices might not provide an interrupt line for the touchscreen.
> In that case the driver defaults to using a polled interface.
>
> Signed-off-by: Nicolas Saenz Julienne
> ---
> .../devicetree/bindings/input/touchscreen/ed
On Thu, May 02, 2019 at 01:49:29PM -0700, Linus Torvalds wrote:
> We *could* also make this kernel-mode-only do_int3() be a special
> function, and do something like
I think I prefer the variant we have now. The int3_emulate_*() things
work uniformly and as expected on 32 and 64 bit (it would eve
чт, 2 мая 2019 г. в 14:23, Joel Savitz :
>
> Yes, this the change, thanks to the suggestion of Yury Norov.
Joel, could you please stop top-posting?
> I also now explicitly mention the expected userspace destination type
> in the manpage patch.
>
> Best,
> Joel Savitz
>
>
> On Thu, May 2, 2019 at
Hi all,
Commit
b835a4a3faec ("btrfs: use the existing reserved items for our first prop for
inheritance")
is missing a Signed-off-by from its author.
--
Cheers,
Stephen Rothwell
pgppTZ2xbpCF9.pgp
Description: OpenPGP digital signature
On Wed, 1 May 2019 17:14:05 -0700, Bjorn Andersson wrote:
> The Qualcomm PCIe2 PHY is a Synopsys based PCIe PHY found in a number of
> Qualcomm platforms, add a binding to describe this.
>
> Signed-off-by: Bjorn Andersson
> ---
>
> Changes since v2:
> - Add #clock-cells
>
> .../bindings/phy/q
On Thu, May 2, 2019 at 7:45 AM Geert Uytterhoeven
wrote:
>
> There is no need to print a backtrace or other error message if
> kzalloc(), kmemdup(), or devm_kzalloc() fails, as the memory allocation
> core already takes care of that.
>
> Signed-off-by: Geert Uytterhoeven
> ---
> drivers/of/unitt
On 4/11/19 6:01 AM, John Garry wrote:
> On 07/04/2019 22:34, Florian Fainelli wrote:
>> The Cortex-A72 supports all ARMv8 recommended events up to the
>> RC_ST_SPEC (0x91) event, create an appropriate JSON file for mapping
>> those events and update the mapfile.csv for matching the Cortex-A72 MIDR
Since recent high resolution scrolling changes the A4Tech driver must
check for the "REL_WHEEL_HI_RES" usage code.
Fixes: 2dc702c991e3774af9d7ce410eef410ca9e2357e (HID: input: use the
Resolution Multiplier for high-resolution scrolling)
Signed-off-by: Błażej Szczygieł
---
drivers/hid/hid-a4tech
> Won't be possible to use put_user here? Something like
>
> static int prctl_get_tasksize(unsigned long __user *uaddr)
> {
> return put_user(TASK_SIZE, uaddr) ? -EFAULT : 0;
> }
What would be the benefit of using put_user() over copy_to_user() in
this context?
чт, 2 мая 2019 г. в 13:52, Joel Savitz :
>
> When PR_GET_TASK_SIZE is passed to prctl, the kernel will attempt to
> copy the value of TASK_SIZE to the userspace address in arg2.
>
> Suggested-by: Alexey Dobriyan
> Signed-off-by: Joel Savitz
> ---
> include/uapi/linux/prctl.h | 3 +++
> kernel/s
Hi Daniel,
On Thu, 2 May 2019 22:09:49 +0200 Daniel Lezcano
wrote:
>
> Yes, I picked the patch and it was merged it via the tip tree [1] as
> requested by Marc Zyngier [2] and notified [3].
>
> In any case, this patch should have go through my tree initially, so if
> it is found somewhere else
Quoting Paul Walmsley (2019-04-30 13:50:58)
> Add common library code for the Analog Bits Wide-Range PLL (WRPLL) IP
> block, as implemented in TSMC CLN28HPC.
>
> There is no bus interface or register target associated with this PLL.
> This library is intended to be used by drivers for IP blocks th
Quoting Paul Walmsley (2019-04-30 13:51:00)
> Add driver code for the SiFive FU540 PRCI IP block. This IP block
> handles reset and clock control for the SiFive FU540 device and
> implements SoC-level clock tree controls and dividers.
>
> Based on code written by Wesley Terpstra :
> https://githu
чт, 2 мая 2019 г. в 13:52, Joel Savitz :
>
> Add a short explanation of the new PR_GET_TASK_SIZE option for the benefit
> of future generations.
>
> Signed-off-by: Joel Savitz
> ---
> man2/prctl.2 | 9 +
> 1 file changed, 9 insertions(+)
>
> diff --git a/man2/prctl.2 b/man2/prctl.2
> inde
Dear Saravanan Sekar,
On Thu, May 2, 2019 at 8:14 PM Saravanan Sekar wrote:
>
> Add support to output level control for the analog high power output
> drivers HPOUT and HPCOM.
>
> Signed-off-by: Saravanan Sekar
> ---
>
> Notes:
> Changes in V3:
> -Fixed compilation error
>
> Changes
stable-rc/linux-4.19.y boot: 123 boots: 1 failed, 119 passed with 3 offline
(v4.19.38-73-gdb2d00a74567)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.19.38-73-gdb2d00a74567/
Full Build Summary:
https://kernelci.org/build/stable-rc/branch/linux-4.19
On Thu, 2 May 2019 22:21:46 +0200
Peter Zijlstra wrote:
> On Thu, May 02, 2019 at 11:43:37AM -0700, Linus Torvalds wrote:
> > What would it look like with the "int3-from-kernel is special"
> > modification?
>
> Something like so; it boots; but I could've made some horrible mistake
> (again).
Downstream Chrome OS kernels use the builtin DDC bus from dw_hdmi on
veyron. This is the only way to get them to negotiate HDCP.
Although HDCP isn't currently all supported upstream, it still seems
like it makes sense to use dw_hdmi's builtin I2C. Maybe eventually we
can get HDCP negotiation wor
The Wilco Embedded Controller is able to send telemetry data
which is useful for enterprise applications. A daemon running on
the OS sends a command to the EC via a write() to a char device,
and can read the response with a read(). The write() request is
verified by the driver to ensure that it is
Veyron uses the builtin i2c controller that's part of dw-hdmi. Hook
up the unwedging feature.
Signed-off-by: Douglas Anderson
---
arch/arm/boot/dts/rk3288-veyron.dtsi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/rk3288-veyron.dtsi
b/arch/arm/boot/dts
This adds the "unwedge" pinctrl entries introduced by a recent dw_hdmi
change that can unwedge the dw_hdmi i2c bus in some cases. It's
expected that any boards using this would add:
pinctrl-names = "default", "unwedge";
pinctrl-0 = <&hdmi_ddc>;
pinctrl-1 = <&hdmi_ddc_unwedge>;
Note that th
The 0xF6 command, intended to send and receive 256 byte payloads to
and from the EC, is not needed. The 0xF5 command for 32 byte
payloads is sufficient. This patch removes support for the 0xF6
command and 256 byte payloads.
Signed-off-by: Nick Crews
---
Documentation/ABI/testing/debugfs-wilco-ec
On Thu, May 02, 2019 at 09:14:46PM +, Vadim Pasternak wrote:
> [...]
> > >
> > > >>Better, if you can avoid cast.
> > > >>Would compiler warn if you use for example rol16(client->addr, 1) &
> > GENMASK(7, 0); or something like it?
> > > I thought it wouldn't be too much of an issue to use type
On Thu, May 02 2019, Miklos Szeredi wrote:
> On Thu, May 2, 2019 at 10:05 AM Andreas Gruenbacher
> wrote:
>>
>> On Thu, 2 May 2019 at 05:57, NeilBrown wrote:
>> > On Wed, May 01 2019, Amir Goldstein wrote:
>> > > On Wed, May 1, 2019 at 10:03 PM NeilBrown wrote:
>> > >> On Tue, Dec 06 2016, J.
stable-rc/linux-4.9.y boot: 104 boots: 2 failed, 99 passed with 3 offline
(v4.9.172-33-gd35bcd092304)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.172-33-gd35bcd092304/
Full Build Summary:
https://kernelci.org/build/stable-rc/branch/linux-4.9.y/k
On Thu, May 02 2019, Amir Goldstein wrote:
> On Thu, May 2, 2019 at 12:35 AM NeilBrown wrote:
>>
>>
>> If the upper and lower layers use incompatible ACL formats, it is not
>> possible to copy the ACL xttr from one to the other, so overlayfs
>> cannot work with them.
>> This happens particularly
On Thu, May 2, 2019 at 3:46 PM Pavel Tatashin wrote:
>
> Hi Dan,
>
> How do you test these patches? Do you have any instructions?
Yes, I briefly mentioned this in the cover letter, but here is the
test I am using:
>
> I see for example that check_hotplug_memory_range() still enforces
> memory_bl
On Thu, May 02, 2019 at 09:12:18AM -0700, Linus Torvalds wrote:
> On Thu, May 2, 2019 at 1:27 AM Jan Glauber wrote:
> >
> > I'll see how x86 runs the same testcase, I thought that playing
> > cacheline ping-pong is not the optimal use case for any CPU.
>
> Oh, ping-pong is always bad.
>
> But fr
On Thu, 2 May 2019, Matthew Garrett wrote:
> On Thu, May 2, 2019 at 2:07 PM James Morris wrote:
> > One possible direction is to (as previously mentioned) assign IDs to each
> > callsite and be able to check this ID against a simple policy array
> > (allow/deny). The default policy choices could
h function it appears in
Caused by commit
7c36ec8a90a8 ("clk: Remove CLK_IS_BASIC clk flag")
I have used the clk tree from next-20190502 for today. (The above commit
does not revert cleanly.)
--
Cheers,
Stephen Rothwell
pgpxaBeDvQuVg.pgp
Description: OpenPGP digital signature
On Thu, May 02 2019, Andreas Gruenbacher wrote:
> On Thu, 2 May 2019 at 05:57, NeilBrown wrote:
>> On Wed, May 01 2019, Amir Goldstein wrote:
>> > On Wed, May 1, 2019 at 10:03 PM NeilBrown wrote:
>> >> On Tue, Dec 06 2016, J. Bruce Fields wrote:
>> >> > On Tue, Dec 06, 2016 at 02:18:31PM +0100,
On Thu, 2 May 2019 18:52:25 -0400
Steven Rostedt wrote:
> On Thu, 2 May 2019 22:21:46 +0200
> Peter Zijlstra wrote:
>
> > On Thu, May 02, 2019 at 11:43:37AM -0700, Linus Torvalds wrote:
> > > What would it look like with the "int3-from-kernel is special"
> > > modification?
> >
> > Some
The Cortex-A57 and Cortex-A72 both support all ARMv8 recommended events
up to the RC_ST_SPEC (0x91) event with the exception of:
- L1D_CACHE_REFILL_INNER (0x44)
- L1D_CACHE_REFILL_OUTER (0x45)
- L1D_TLB_RD (0x4E)
- L1D_TLB_WR (0x4F)
- L2D_TLB_REFILL_RD (0x5C)
- L2D_TLB_REFILL_WR (0x5D)
- L2D_TLB_R
On Thu, 2 May 2019 19:31:29 -0400
Steven Rostedt wrote:
> Digging a little further, I pinpointed it out to being kretprobes. The
> problem I believe is the use of kernel_stack_pointer() which does some
> magic on x86_32. kretprobes uses this to hijack the return address of
> the function (much li
Em Thu, May 02, 2019 at 02:28:02PM -0700, Florian Fainelli escreveu:
> On 4/8/19 9:26 AM, Will Deacon wrote:
> > On Fri, Apr 05, 2019 at 09:50:47AM -0700, Florian Fainelli wrote:
> >> Broadcom's Brahma-B53 CPUs support the same type of events that the
> >> Cortex-A53 supports, recognize its CPUID a
Eric,
Can you please help test this?
If this solves your problem, I can post the fix.
Thanks,
- Deepa
-8<---
Subject: [PATCH] signal: Adjust error codes according to restore_user_sigmask()
For all the syscalls that receive a sigmask from the userland,
the user sigmask is to be in eff
stable-rc/linux-4.14.y boot: 122 boots: 1 failed, 121 passed
(v4.14.115-50-ga4aa5bff0752)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.115-50-ga4aa5bff0752/
Full Build Summary:
https://kernelci.org/build/stable-rc/branch/linux-4.14.y/kernel/v4.
On 5/1/19 4:27 PM, Tim Chen wrote:
> On 4/28/19 11:15 PM, Aaron Lu wrote:
>> On Tue, Apr 23, 2019 at 04:18:16PM +, Vineeth Remanan Pillai wrote:
>>> +/*
>>> + * Find left-most (aka, highest priority) task matching @cookie.
>>> + */
>>> +struct task_struct *sched_core_find(struct rq *rq, unsigne
Hi David,
After merging the btrfs-kdave tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
fs/btrfs/props.c: In function 'inherit_props':
fs/btrfs/props.c:389:4: warning: 'num_bytes' may be used uninitialized in this
function [-Wmaybe-uninitialized]
btrfs_block_rsv_r
From: Leo Yan
The traceevent lib is used by the perf tool, and when executing
perf test -v 6
it outputs error log on the ARM64 platform:
running test 33 '*:*'trace-cmd: No such file or directory
[...]
trace-cmd: Invalid argument
The trace event parsing code originally came from trac
o-5.1-20190502
for you to fetch changes up to 7e221b811f1472d0c58c7d4e0fe84fcacd22580a:
perf tools: Remove needless asm/unistd.h include fixing build in some places
(2019-05-02 16:00:20 -0400)
perf/urgent fixes:
tools UAPI:
Ar
From: Thomas Richter
An -ENOMEM error is not reported in the GTK GUI. Instead this error
message pops up on the screen:
[root@m35lp76 perf]# ./perf report -i perf.data.error68-1
Processing events... [974K/3M]
Error:failed to process sample
0xf4198 [0x8]: failed to pro
From: Arnaldo Carvalho de Melo
To pick up the changes from:
2b27924bb1d4 ("KVM: nVMX: always use early vmcs check when EPT is disabled")
That causes this object in the tools/perf build process to be rebuilt:
CC /tmp/build/perf/arch/x86/util/kvm-stat.o
But it isn't using VMX_ABORT_ p
From: Leo Yan
Since cs_etm_queue::prev_packet is allocated for all cases, it will
never be NULL pointer; now validity checking prev_packet is pointless,
remove all of them.
Signed-off-by: Leo Yan
Tested-by: Robert Walker
Cc: Alexander Shishkin
Cc: Jiri Olsa
Cc: Mathieu Poirier
Cc: Mike Leac
From: Arnaldo Carvalho de Melo
We were including sys/syscall.h and asm/unistd.h, since sys/syscall.h
includes asm/unistd.h, sometimes this leads to the redefinition of
defines, breaking the build.
Noticed on ARC with uCLibc.
Cc: Adrian Hunter
Cc: Arnaldo Carvalho de Melo
Cc: Arnd Bergmann
Cc
From: Arnaldo Carvalho de Melo
Thomas Backlund reported that the perf build was failing on the Mageia 7
distro, that is because it uses:
cat /tmp/build/perf/feature/test-disassembler-four-args.make.output
/usr/bin/ld: /usr/lib64/libbfd.a(plugin.o): in function `try_load_plugin':
/home/iurt
From: Leo Yan
Robert Walker reported a segmentation fault is observed when process
CoreSight trace data; this issue can be easily reproduced by the command
'perf report --itrace=i1000i' for decoding tracing data.
If neither the 'b' flag (synthesize branches events) nor 'l' flag
(synthesize last
From: Thadeu Lima de Souza Cascardo
Commit 6987561c9e86 ("perf annotate: Enable annotation of BPF programs") adds
support for BPF programs annotations but the new code does not build on 32-bit.
Signed-off-by: Thadeu Lima de Souza Cascardo
Acked-by: Song Liu
Fixes: 6987561c9e86 ("perf annotate:
Hi Dmitry,
On 19. 5. 2. 오전 8:37, Dmitry Osipenko wrote:
> Changelog:
>
> v4: Addressed all review comments that were made by Chanwoo Choi to v3:
>
> - changed the driver removal order to match the probe exactly
> - added clarifying comment for 1/8 ratio to the Tegra20 driver
>
> Cha
> On May 2, 2019, at 4:19 PM, James Morris wrote:
>
>> On Thu, 2 May 2019, Matthew Garrett wrote:
>>
>>> On Thu, May 2, 2019 at 2:07 PM James Morris wrote:
>>> One possible direction is to (as previously mentioned) assign IDs to each
>>> callsite and be able to check this ID against a simple
Hi Gaël,
The patch1 was already applied to devfreq.git
and then it was applied to linux-pm.git through
pull request of devfreq.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=bleeding-edge&id=adfe3b76608ffe547af5a74415f15499b798f32a
On 19. 5. 3. 오전 2:58, Gaël
Hi
Also, this patch was applied to linux-pm.git for for v5.2-rc1.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=bleeding-edge&id=adfe3b76608ffe547af5a74415f15499b798f32a
On 19. 5. 3. 오전 2:58, Gaël PORTAY wrote:
> From: Enric Balletbo i Serra
>
> Trusted Fi
On 03/05/2019 00:03, Stephen Rothwell wrote:
> Hi Daniel,
>
> On Thu, 2 May 2019 22:09:49 +0200 Daniel Lezcano
> wrote:
>>
>> Yes, I picked the patch and it was merged it via the tip tree [1] as
>> requested by Marc Zyngier [2] and notified [3].
>>
>> In any case, this patch should have go throu
03.05.2019 3:31, Chanwoo Choi пишет:
> Hi Dmitry,
>
> On 19. 5. 2. 오전 8:37, Dmitry Osipenko wrote:
>> Changelog:
>>
>> v4: Addressed all review comments that were made by Chanwoo Choi to v3:
>>
>> - changed the driver removal order to match the probe exactly
>> - added clarifying comment f
On Thu, May 2, 2019 at 9:48 PM Yingjoe Chen wrote:
>
> On Mon, 2019-04-29 at 11:25 +0800, Nicolas Boichat wrote:
> > pinctrl variants that include pinctrl-mtk-common-v2.h (and not
> > pinctrl-mtk-common.h) also need to use mtk_eint_pm_ops to setup
> > wake mask properly, so copy over the pm_ops to
On 2019/05/03 1:28, Casey Schaufler wrote:
> On 5/2/2019 8:48 AM, Mimi Zohar wrote:
>> [Cc'ing Paul, John, Casey]
>>
>> On Mon, 2019-04-22 at 20:18 -0400, Mimi Zohar wrote:
>>> [Cc'ing LSM mailing list]
>>>
>>> On Fri, 2019-04-19 at 17:30 -0700, prakhar srivastava wrote:
>>>
2) Adding a LSM ho
Hello,
syzbot found the following crash on:
HEAD commit:9520b532 Merge tag 'for-linus' of git://git.armlinux.org.u..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1104bb90a0
kernel config: https://syzkaller.appspot.com/x/.config?x=a42d110b47dd6b36
da
Hi all,
Today's linux-next merge of the vfs tree got a conflict in:
fs/ext4/super.c
fs/f2fs/super.c
between commit:
2c58d548f570 ("fscrypt: cache decrypted symlink target in ->i_link")
from the fscrypt tree and commits:
94053139d482 ("ext4: make use of ->free_inode()")
d01718a050d0
Hi all,
Today's linux-next merge of the vfs tree got a conflict in:
fs/orangefs/super.c
between commit:
77becb76042a ("orangefs: implement xattr cache")
from the orangefs tree and commit:
f276ae0dd6d0 ("orangefs: make use of ->free_inode()")
from the vfs tree.
I fixed it up (see below
On Thu, May 02, 2019 at 10:34:12AM +0200, Petr Mladek wrote:
> On Wed 2019-05-01 09:38:03, Tobin C. Harding wrote:
> > Hi,
> >
> > Looks like I've created a bit of confusion trying to fix memleaks in
> > calls to kobject_init_and_add(). Its spread over various patches and
> > mailing lists so I'm
Hi all,
Today's linux-next merge of the vfs tree got a conflict in:
samples/Makefile
between commit:
a757ed09d672 ("samples: guard sub-directories with CONFIG options")
from the kbuild tree and commit:
f1b5618e013a ("vfs: Add a sample program for the new mount API")
from the vfs tree.
problem may be somewhere else. *
* Hope this helps! *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
next/master boot bisection: next-20190502 on beagle-xm
Summary:
Start: e8b243ea3b19 Add linux-next specific files for 20190502
Hi,
On Thu, May 02, 2019 at 11:27:00AM -0600, Ross Zwisler wrote:
> Several sound related entries in MAINTAINERS refer to the old git tree
> at "git://git.alsa-project.org/alsa-kernel.git". This is no longer used
> for development, and Takashi Iwai's kernel.org tree is used instead.
>
> Signed-o
On Thu, May 02, 2019 at 12:22:24PM +0200, Greg Kroah-Hartman wrote:
> Commit 1fd7c3b438a2 ("kobject: Improve doc clarity kobject_init_and_add()")
> tried to provide more clarity, but the reference to kobject_del() was
> incorrect. Fix that up by removing that line, and hopefully be more explicit
>
On Thu, May 02, 2019 at 10:39:22AM +0200, Johan Hovold wrote:
> On Thu, May 02, 2019 at 06:25:39PM +1000, Tobin C. Harding wrote: > Adding
> Jon to CC
> >
> > On Thu, May 02, 2019 at 09:38:23AM +0200, Johan Hovold wrote:
> > > On Thu, May 02, 2019 at 12:31:40PM +1000, Tobin C. Harding wrote:
> >
The Hygon Dhyana CPU has the SMBus device with PCI device ID 0x790b,
which is the same as AMD CZ SMBus device. So add Hygon Dhyana support
to the i2c-piix4 driver by using the code path of AMD.
Signed-off-by: Pu Wen
Reviewed-by: Jean Delvare
---
v2 RESEND:
- Add 'Reviewed-by' tag from Jean Del
On 5/2/19 6:40 PM, Tobin C. Harding wrote:
> On Thu, May 02, 2019 at 10:39:22AM +0200, Johan Hovold wrote:
>> On Thu, May 02, 2019 at 06:25:39PM +1000, Tobin C. Harding wrote: > Adding
>> Jon to CC
>>>
>>> On Thu, May 02, 2019 at 09:38:23AM +0200, Johan Hovold wrote:
On Thu, May 02, 2019 at 1
On Thu, May 02, 2019 at 03:23:12PM -0700, Yury Norov wrote:
> чт, 2 мая 2019 г. в 13:52, Joel Savitz :
> >
> > Add a short explanation of the new PR_GET_TASK_SIZE option for the benefit
> > of future generations.
> >
> > Signed-off-by: Joel Savitz
> > ---
> > man2/prctl.2 | 9 +
> > 1 fil
On 5/1/19 5:01 PM, Brendan Higgins wrote:
A lot of the expectation and assertion infrastructure prints out fairly
complicated test failure messages, so add a C++ style log library for
for logging test results.
Signed-off-by: Brendan Higgins
---
include/kunit/kunit-stream.h | 85 +
[ This version of the patch passed all my tests! ]
From: Peter Zijlstra
In order to allow breakpoints to emulate call functions, they need to push
the return address onto the stack. But because the breakpoint exception
frame is added to the stack when the breakpoint is hit, there's no room to
drivers/staging/kpc2000/kpc_spi/spi_driver.c:158:11: error: implicit
declaration of function 'readq' [-Werror,-Wimplicit-function-declaration]
drivers/staging/kpc2000/kpc_spi/spi_driver.c:167:5: error: implicit
declaration of function 'writeq' [-Werror,-Wimplicit-function-declaration]
Same as comm
After thread is added to machine->threads[i].dead in
__machine__remove_thread, the machine->threads[i].dead is freed
when calling free(session) in perf_session__delete(). So it get a
Segmentation fault when accessing it in thread__put().
In this patch, we delay the perf_session__delete until all t
Deepa Dinamani wrote:
> Eric,
> Can you please help test this?
Nope, that was _really_ badly whitespace-damaged.
(C'mon, it's not like you're new to this)
Hi Eddie,
On Wed, 1 May 2019 at 14:43, Eddie James wrote:
>
> The DPS310 supports measurement of pressure, so support that in the
> driver. Use background measurement like the temperature sensing and
> default to lowest precision and lowest measurement rate.
Upstream didn't accept my patch as th
> From: Stephen Boyd [mailto:sb...@kernel.org]
> Sent: Thursday, May 2, 2019 5:01 AM
>
> The Content-transfer-encoding header is still base64. I guess it can't be
> fixed.
>
How can we know it's base64?
As I saw from the 'Headers' in patchwork, it's:
"Content-Type: text/plain; charset="us-ascii
On 02-05-19, 08:00, Bjorn Andersson wrote:
> On Thu 02 May 04:53 PDT 2019, Vinod Koul wrote:
> > On 01-05-19, 17:19, Bjorn Andersson wrote:
> [..]
> > > diff --git a/drivers/pci/controller/dwc/pcie-qcom.c
> > > b/drivers/pci/controller/dwc/pcie-qcom.c
> > > index 0ed235d560e3..d740cbe0e56d 100644
Hi all,
When building with -Wuninitialized, Clang warns:
drivers/misc/sgi-xp/xpc_partition.c:73:14: warning: variable 'buf' is
uninitialized when used within its own initialization [-Wuninitialized]
void *buf = buf;
~~~ ^~~
1 warning generated.
I am not really sure how t
On Thu, 02 May 2019, Deepa Dinamani wrote:
Reported-by: Omar Kilani
Do we actually know if this was the issue Omar was hitting?
Thanks,
Davidlohr
701 - 800 of 895 matches
Mail list logo
