On Thu, 25 Jul 2019, H. Peter Anvin wrote:
> On 7/25/19 3:03 PM, Thomas Gleixner wrote:
> > On Thu, 25 Jul 2019, h...@zytor.com wrote:
> >> On July 25, 2019 2:48:30 PM PDT, Thomas Gleixner
> >> wrote:
> >>>
> >>> But seriously I think it's not completely insane what they are doing
> >>> and the
Align the RV64 defconfig to the output of "make savedefconfig" to
avoid unnecessary deltas for future defconfig patches. This patch
should have no runtime functional impact.
Signed-off-by: Paul Walmsley
---
arch/riscv/configs/defconfig | 10 +-
1 file changed, 5 insertions(+), 5
On Thu, Jul 25, 2019 at 06:24:01PM -0400, George G. Davis wrote:
> Hello Russell,
>
> On Thu, Jul 25, 2019 at 10:55:40PM +0100, Russell King - ARM Linux admin
> wrote:
> > On Thu, Jul 25, 2019 at 05:37:54PM -0400, George G. Davis wrote:
> > > Hello Russell,
> > >
> > > Thanks for your prompt
On 7/25/19 3:03 PM, Thomas Gleixner wrote:
> On Thu, 25 Jul 2019, h...@zytor.com wrote:
>> On July 25, 2019 2:48:30 PM PDT, Thomas Gleixner wrote:
>>>
>>> But seriously I think it's not completely insane what they are doing
>>> and the table based approach is definitely more readable and
On Wed, Jul 24, 2019 at 1:42 PM Suman Anna wrote:
>
> On 7/24/19 11:34 AM, Rob Herring wrote:
> > On Sun, 7 Jul 2019 22:52:38 -0500, Suman Anna wrote:
> >> The Programmable Real-Time Unit Subsystem (PRUSS) contains an interrupt
> >> controller (INTC) that can handle various system input events
Hello Russell,
On Thu, Jul 25, 2019 at 10:55:40PM +0100, Russell King - ARM Linux admin wrote:
> On Thu, Jul 25, 2019 at 05:37:54PM -0400, George G. Davis wrote:
> > Hello Russell,
> >
> > Thanks for your prompt reply!
> >
> > On Sat, Jul 20, 2019 at 01:30:23PM +0100, Russell King - ARM Linux
Add interrupt support to TSENS. The first 6 patches are general fixes and
cleanups to the driver before interrupt support is introduced.
This series has been developed against qcs404 and sdm845 and then tested on
msm8916. Testing on msm8998 and msm8974 would be appreciated since I don't
have
There are two fields - id and hw_id - to track what sensor an action was
to performed on. This was because the sensors connected to a TSENS IP
might not be contiguous i.e. 1, 2, 4, 5 with 3 being skipped.
This causes confusion in the code which uses hw_id sometimes and id
other times
msm8916 uses sensors 0, 1, 2, 4 and 5. Sensor 3 is NOT used. Fixup the
device tree so that the correct sensor ID is used and as a result we can
actually check the temperature for the cpu2_3 sensor.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/msm8916.dtsi | 4 ++--
1 file changed,
Dump some basic version info and sensor details into debugfs
Signed-off-by: Amit Kucheria
---
drivers/thermal/qcom/tsens-common.c | 85 +
drivers/thermal/qcom/tsens.c| 2 +
drivers/thermal/qcom/tsens.h| 6 ++
3 files changed, 93 insertions(+)
diff
Register upper-lower interrupt for the tsens controller.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/msm8916.dtsi | 22 --
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/msm8916.dtsi
Hi Justin,
Am Sonntag, 16. Juni 2019, 22:47:45 CEST schrieb Justin Swartz:
> The Mecer Xtreme Mini S6 features a Rockchip RK3229 SoC,
> 1GB DDR3 RAM, 8GB eMMC, MicroSD port, 10/100Mbps Ethernet,
> Realtek 8723BS WLAN module, 2 x USB 2.0 ports, HDMI output,
> and S/PDIF output.
>
> Signed-off-by:
Register upper-lower interrupts for each of the two tsens controllers.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 88 +++-
1 file changed, 46 insertions(+), 42 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
Hide the details of how to convert values read from TSENS HW to mCelsius
behind a function. All versions of the IP can be supported as a result.
Signed-off-by: Amit Kucheria
---
drivers/thermal/qcom/tsens-common.c | 34 -
1 file changed, 24 insertions(+), 10
Register upper-lower interrupt for the tsens controller.
Signed-off-by: Amit Kucheria
---
Cc: masn...@onstation.org
arch/arm/boot/dts/qcom-msm8974.dtsi | 36 +++--
1 file changed, 19 insertions(+), 17 deletions(-)
diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi
msm8974 has 11 sensors connected to a single TSENS IP. Define a thermal
zone for each of those sensors to expose the temperature of each zone.
Signed-off-by: Amit Kucheria
---
Cc: masn...@onstation.org
arch/arm/boot/dts/qcom-msm8974.dtsi | 90 +
1 file changed, 90
Register upper-lower interrupts for each of the two tsens controllers.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 60 ++-
1 file changed, 32 insertions(+), 28 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi
Register upper-lower interrupts for each of the two tsens controllers.
Signed-off-by: Amit Kucheria
---
Cc: marc.w.gonza...@free.fr
arch/arm64/boot/dts/qcom/msm8998.dtsi | 82 ++-
1 file changed, 42 insertions(+), 40 deletions(-)
diff --git
Register upper-lower interrupt for the tsens controller.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/qcs404.dtsi | 42 +++-
1 file changed, 22 insertions(+), 20 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/qcs404.dtsi
Define two new required properties to define interrupts and
interrupt-names for tsens.
Signed-off-by: Amit Kucheria
---
Documentation/devicetree/bindings/thermal/qcom-tsens.txt | 5 +
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/thermal/qcom-tsens.txt
Depending on the IP version, TSENS supports upper, lower, max, min and
critical threshold interrupts. We only add support for upper and lower
threshold interrupts for now.
TSENSv2 has an irq [status|clear|mask] bit tuple for each sensor while
earlier versions only have a single bit per sensor to
On Wed, Jul 24, 2019 at 09:15:52PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.1.20 release.
> There are 371 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
Move platform_set_drvdata up to avoid an extra 'if (ret)' check after
the call to tsens_register.
Signed-off-by: Amit Kucheria
---
drivers/thermal/qcom/tsens.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/thermal/qcom/tsens.c b/drivers/thermal/qcom/tsens.c
Printing the function name when enabling debugging makes logs easier to
read.
Signed-off-by: Amit Kucheria
---
drivers/thermal/qcom/tsens-common.c | 8
drivers/thermal/qcom/tsens.c| 6 +++---
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git
On Thu, 25 Jul 2019, Peter Zijlstra wrote:
> On Thu, Jul 25, 2019 at 09:37:15AM -0700, Andy Lutomirski wrote:
> > A data breakpoint near the top of an IST stack will cause unresoverable
unresoverable?
> > recursion. A data breakpoint on the GDT, IDT, or TSS is terrifying.
> > Prevent either of
On 25/07/19 22:57, Sean Christopherson wrote:
> On Thu, Jul 25, 2019 at 03:19:33PM -0500, Dan Rue wrote:
>> I would still prefer to run the latest tests against all kernel versions
>> (but better control when we upgrade it). Like I said, we can handle
>> expected failures, and it would even help
On Thu, 25 Jul 2019, h...@zytor.com wrote:
> On July 25, 2019 2:48:30 PM PDT, Thomas Gleixner wrote:
> >
> > But seriously I think it's not completely insane what they are doing
> > and the table based approach is definitely more readable and maintainable
> > than the existing stuff.
>
> Doing
On 7/24/19 9:40 PM, a...@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2019-07-24-21-39 has been uploaded to
>
>http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my
add_to_kill() expects the first 'tk' to be pre-allocated, it makes
subsequent allocations on need basis, this makes the code a bit
difficult to read. Move all the allocation internal to add_to_kill()
and drop the **tk argument.
Signed-off-by: Jane Chu
---
mm/memory-failure.c | 40
Changes in v3:
- move **tk cleanup to its own patch
Changes in v2:
- move 'tk' allocations internal to add_to_kill(), suggested by Dan;
- ran checkpatch.pl check, pointed out by Matthew;
- Noaya pointed out that v1 would have missed the SIGKILL
if "tk->addr == -EFAULT", since the code
Mmap /dev/dax more than once, then read the poison location using address
from one of the mappings. The other mappings due to not having the page
mapped in will cause SIGKILLs delivered to the process. SIGKILL succeeds
over SIGBUS, so user process looses the opportunity to handle the UE.
Although
On Thu, 2019-07-25 at 20:28 +0800, liuyonglong wrote:
>
> On 2019/7/25 3:12, Saeed Mahameed wrote:
> > On Wed, 2019-07-24 at 11:18 +0800, Huazhong Tan wrote:
> > > From: Yonglong Liu
> > >
> > > Some times just see the eth interface have been down/up via
> > > dmesg, but can not know why the
On Thu, Jul 25, 2019 at 02:42:22PM -0700, Matthew Wilcox wrote:
> On Thu, Jul 25, 2019 at 10:38:58PM +0100, Russell King - ARM Linux admin
> wrote:
> > On Thu, Jul 25, 2019 at 07:39:21AM -0700, Matthew Wilcox wrote:
> > > But 'page' isn't necessarily PMD-aligned. I don't think we can rely on
> >
On July 25, 2019 2:48:30 PM PDT, Thomas Gleixner wrote:
>On Thu, 25 Jul 2019, John Hubbard wrote:
>> On 7/25/19 12:22 AM, Thomas Gleixner wrote:
>> > It removes the clearing of the range between kbd_status and hdr
>without any
>> > replacement. It neither clears edid_info.
>>
>>
>> Yes. Somehow
On Thu, Jul 25, 2019 at 05:37:54PM -0400, George G. Davis wrote:
> Hello Russell,
>
> Thanks for your prompt reply!
>
> On Sat, Jul 20, 2019 at 01:30:23PM +0100, Russell King - ARM Linux admin
> wrote:
> > On Fri, Jul 19, 2019 at 10:32:55PM -0400, George G. Davis wrote:
> > > When an unhandled
On Thu, Jul 25, 2019 at 12:25:23PM +0530, Anshuman Khandual wrote:
> This adds a test module which will validate architecture page table helpers
> and accessors regarding compliance with generic MM semantics expectations.
> This will help various architectures in validating changes to the existing
On Thu, 25 Jul 2019, John Hubbard wrote:
> On 7/25/19 12:22 AM, Thomas Gleixner wrote:
> > It removes the clearing of the range between kbd_status and hdr without any
> > replacement. It neither clears edid_info.
>
>
> Yes. Somehow I left that chunk out. Not my finest hour.
S*** happens
> > +
On 7/24/19 2:13 PM, Qian Cai wrote:
On Wed, 2019-07-10 at 17:43 -0400, Qian Cai wrote:
Running LTP oom01 test case with swap triggers a crash below. Revert the
series
"Make deferred split shrinker memcg aware" [1] seems fix the issue.
You might want to look harder on this commit, as
On 2019/7/25 22:30, Aaron Lu wrote:
> On Mon, Jul 22, 2019 at 06:26:46PM +0800, Aubrey Li wrote:
>> The granularity period of util_avg seems too large to decide task priority
>> during pick_task(), at least it is in my case, cfs_prio_less() always picked
>> core max task, so pick_task() eventually
On Thu, Jul 25, 2019 at 10:38:58PM +0100, Russell King - ARM Linux admin wrote:
> On Thu, Jul 25, 2019 at 07:39:21AM -0700, Matthew Wilcox wrote:
> > But 'page' isn't necessarily PMD-aligned. I don't think we can rely on
> > architectures doing the right thing if asked to make a PMD for a
On 2019-07-23 23:51, Marc Zyngier wrote:
On Tue, 23 Jul 2019 14:52:34 -0700
pher...@codeaurora.org wrote:
Hi Prakruthi,
Hi,
I have been working on a interrupt controller driver that uses tree
based mapping for its domain (irq_domain_add_tree(..)).
If I understand correctly, the clients get a
Zdravstvujte! Vas interesuyut klientskie bazy dannyh?
On Thu, Jul 25, 2019 at 07:39:21AM -0700, Matthew Wilcox wrote:
> On Thu, Jul 25, 2019 at 12:25:23PM +0530, Anshuman Khandual wrote:
> > This adds a test module which will validate architecture page table helpers
> > and accessors regarding compliance with generic MM semantics expectations.
> >
On Wed, 24 Jul 2019 22:32:07 -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:9e6dfe80 Add linux-next specific files for 20190724
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1046971fa0
> kernel config:
Hello Russell,
Thanks for your prompt reply!
On Sat, Jul 20, 2019 at 01:30:23PM +0100, Russell King - ARM Linux admin wrote:
> On Fri, Jul 19, 2019 at 10:32:55PM -0400, George G. Davis wrote:
> > When an unhandled data or prefetch abort occurs, the die() string
> > is empty resulting in
On Thu, Jul 25, 2019 at 3:06 PM Stephen Boyd wrote:
>
> Quoting anson.hu...@nxp.com (2019-07-24 19:05:51)
> > From: Anson Huang
> >
> > YAML file can NOT contain tab as indentation, fix it.
> >
>
> Would be nice if checkpatch could check for this.
Would be nice if folks just ran 'make
That's an even better solution and it gets my HS400 mode working.
Will you add this change or should I?
Thanks
Al
On Thu, Jul 25, 2019 at 3:33 AM Adrian Hunter wrote:
>
> On 23/07/19 3:34 PM, Alan Cooper wrote:
> > On Tue, Jul 23, 2019 at 1:21 AM Adrian Hunter
> > wrote:
> >>
> >> On 23/07/19
hello Jens Axboe,
Please can you take a look at related code and also patch from Kees ?
On Tue, Jul 16, 2019 at 11:58 PM Nick Desaulniers
wrote:
>
> On Wed, Jul 10, 2019 at 10:44 AM Jeffrin Thalakkottoor
> wrote:
> >
> > hello all ,
> >
> > i encountered a KASAN bug related .here are some
Hi Alexey
On Thu, Jul 25, 2019 at 10:56:33PM +0300, Alexey Dobriyan wrote:
> What are these files for?
>
> $ cat ../obj/include/linux/kernel.h.s
> .file "null"
> .text
> .ident "GCC: (Gentoo 9.1.0-r1 p1.1) 9.1.0"
> .section
Am Mittwoch, 3. Juli 2019, 06:54:58 CEST schrieb Doug Anderson:
> Hi,
>
> On Thu, Jun 20, 2019 at 1:31 PM Doug Anderson wrote:
> >
> > Hi,
> >
> > On Thu, Jun 20, 2019 at 11:21 AM Douglas Anderson
> > wrote:
> > >
> > > This reverts commit 1f45e8c6d0161f044d679f242fe7514e2625af4a.
> > >
> > >
On Thu, 2019-07-25 at 10:34 +0800, tanhuazhong wrote:
>
> On 2019/7/25 2:34, Saeed Mahameed wrote:
> > On Wed, 2019-07-24 at 11:18 +0800, Huazhong Tan wrote:
> > > From: Yufeng Mo
> > >
> > > This patch modifies firmware version display format in
> > > hclge(vf)_cmd_init() and
On FU540-based systems, the "timebase-frequency" (RTCCLK) is sourced
from an external crystal located on the PCB. Thus the
timebase-frequency DT property should be defined by the board that
uses the SoC, not the SoC itself. Drop the superfluous
timebase-frequency property from the SoC DT data.
On Mon, Jul 22, 2019 at 10:58 AM Segher Boessenkool
wrote:
>
> On Mon, Jul 22, 2019 at 10:21:07AM -0700, Nick Desaulniers wrote:
> > On Sun, Jul 21, 2019 at 11:19 PM Segher Boessenkool
> > wrote:
> > > On Sun, Jul 21, 2019 at 07:41:40PM -0700, Nathan Chancellor wrote:
> > > > On Sun, Jul 21,
Hi all,
In commit
9fcf9139a2fd ("ASoC: ti: davinci-mcasp: Fix clk PDIR handling for i2s master
mode")
Fixes tag
Fixes: 2302be4126f52 ("ASoC: davinci-mcasp: Update PDIR (pin direction)
register handling")
has these problem(s):
- Target SHA1 does not exist
Did you mean
Fixes:
From: Wesley Terpstra
This is part of adding support for RISC-V systems with PCIe host
controllers that support message-signaled interrupts.
Signed-off-by: Wesley Terpstra
[paul.walms...@sifive.com: wrote patch description; split this
patch from the arch/riscv patch]
Signed-off-by: Paul
On Thu, 25 Jul 2019, Paul Walmsley wrote:
> This is part of adding support for RISC-V systems with PCIe host
> controllers that support message-signaled interrupts.
>
> Signed-off-by: Wesley Terpstra
> [paul.walms...@sifive.com: wrote patch description; split this
> patch from the arch/riscv
This is part of adding support for RISC-V systems with PCIe host
controllers that support message-signaled interrupts.
Signed-off-by: Wesley Terpstra
[paul.walms...@sifive.com: wrote patch description; split this
patch from the arch/riscv patch]
Signed-off-by: Paul Walmsley
---
On Thu, Jul 25, 2019 at 10:49 PM David Hildenbrand wrote:
>
> On 25.07.19 21:19, Michal Hocko wrote:
> > On Thu 25-07-19 16:35:07, David Hildenbrand wrote:
> >> On 25.07.19 15:57, Michal Hocko wrote:
> >>> On Thu 25-07-19 15:05:02, David Hildenbrand wrote:
> On 25.07.19 14:56, Michal Hocko
On 7/22/19 4:24 PM, Brandon Darbro wrote:
> Ubuntu bug tracking the same issue.
>
> https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836986
>
Hello Luca,
Any updated information on this iwlwifi-9260 firmware 46 issue? Is
there bug tracker or repo I should be looking to for
On Thu, Jul 25, 2019 at 6:06 AM David Laight wrote:
>
> From: Numfor Mbiziwo-Tiapo
> > Sent: 24 July 2019 19:45
> >
> > The ubsan (undefined behavior sanitizer) version of perf throws an
> > error on the 'x86 instruction decoder - new instructions' function
> > of perf test.
> >
> > To reproduce
On Jul 23, 2019, at 10:01 PM, Sultan Alsawaf wrote:
>
> On Tue, Jul 23, 2019 at 10:56:05AM -0600, Andreas Dilger wrote:
>> Do you have any kind of performance metrics that show this is an actual
>> improvement in performance? This would be either macro-level benchmarks
>> (e.g. fio, but this
On 7/25/19 1:13 AM, Mel Gorman wrote:
> On Wed, Jul 24, 2019 at 10:50:14AM -0700, Mike Kravetz wrote:
>> When allocating hugetlbfs pool pages via /proc/sys/vm/nr_hugepages,
>> the pages will be interleaved between all nodes of the system. If
>> nodes are not equal, it is quite possible for one
On Thu, 11 Jul 2019, Mao Han wrote:
> This patch fix following perf record error by linking vdso.so with
> build id.
>
> perf.data perf.data.old
> [ perf record: Woken up 1 times to write data ]
> free(): double free detected in tcache 2
> Aborted
>
> perf record use
Quoting anson.hu...@nxp.com (2019-07-24 19:05:51)
> From: Anson Huang
>
> YAML file can NOT contain tab as indentation, fix it.
>
Would be nice if checkpatch could check for this.
> Fixes: 6d6062553e3d ("dt-bindings: imx: Add clock binding doc for i.MX8MN")
> Signed-off-by: Anson Huang
On 7/25/19 6:42 AM, Greg Kroah-Hartman wrote:
> On Tue, Jul 23, 2019 at 05:10:53PM -0700, Saravana Kannan wrote:
>> Add device-links to track functional dependencies between devices
>> after they are created (but before they are probed) by looking at
>> their common DT bindings like clocks,
Am Donnerstag, 25. Juli 2019, 18:26:42 CEST schrieb Matthias Kaehlcke:
> Also known as the AOpen Chromebase Mini.
>
> tiger and fievel are share the same board, tiger has a display and
> touchscreen, fievel not. Use the fievel .dts as base and add the
> extra bits.
>
> Signed-off-by: Matthias
On Thu, Jul 25, 2019 at 03:19:33PM -0500, Dan Rue wrote:
> I would still prefer to run the latest tests against all kernel versions
> (but better control when we upgrade it). Like I said, we can handle
> expected failures, and it would even help to validate backports for
> fixes that do get
Am Donnerstag, 25. Juli 2019, 18:26:41 CEST schrieb Matthias Kaehlcke:
> Also known as AOpen Chromebox Mini.
>
> Signed-off-by: Matthias Kaehlcke
> ---
> Changes in v3:
> - patch added to the series
> ---
> arch/arm/boot/dts/Makefile | 1 +
>
Am Donnerstag, 25. Juli 2019, 18:26:40 CEST schrieb Matthias Kaehlcke:
> Fievel is a Chromebox and Tiger a Chromebase with a 10" display and
> touchscreen. Tiger and Fievel are based on the same board.
>
> Signed-off-by: Matthias Kaehlcke
applied for 5.4
On 25.07.19 21:19, Michal Hocko wrote:
> On Thu 25-07-19 16:35:07, David Hildenbrand wrote:
>> On 25.07.19 15:57, Michal Hocko wrote:
>>> On Thu 25-07-19 15:05:02, David Hildenbrand wrote:
On 25.07.19 14:56, Michal Hocko wrote:
> On Wed 24-07-19 16:30:17, David Hildenbrand wrote:
>>
Am Donnerstag, 25. Juli 2019, 18:26:39 CEST schrieb Matthias Kaehlcke:
> veyron jaq, jerry, minnie and speedy have mostly redundant regulator
> and pinctrl configurations for the panel/backlight. Consolidate these
> pieces in the eDP .dtsi.
>
> Also change the default power supply for the panel
Am Donnerstag, 25. Juli 2019, 18:26:38 CEST schrieb Matthias Kaehlcke:
> The chromebook .dtsi file contains common settings for veyron
> Chromebooks with eDP displays. Some veyron devices with a display
> aren't Chromebooks (e.g. 'tiger' aka 'AOpen Chromebase Mini'), move
> display related bits
On 25.07.19 22:37, Alexander Duyck wrote:
> On Thu, 2019-07-25 at 20:32 +0200, David Hildenbrand wrote:
>> On 25.07.19 19:38, Alexander Duyck wrote:
>>> On Thu, 2019-07-25 at 18:48 +0200, David Hildenbrand wrote:
On 25.07.19 17:59, Alexander Duyck wrote:
> On Thu, Jul 25, 2019 at 1:53 AM
On 7/25/19 1:38 PM, H. Peter Anvin wrote:
> On 7/25/19 12:22 AM, Thomas Gleixner wrote:
> The easy way would be to put in a suitable cast to clear the warning -- I
> would not be surprised if an explicit cast to something like (void *) would
> quiet the warning, or else (yuck) put in an explicit
We want to be able to keep more spaces available in our queue for
processing incoming IPv6 multicast traffic (adding (S,G) entries) - this
lets us learn more groups faster, rather than dropping them at this stage.
Signed-off-by: Brodie Greenfield
---
Documentation/networking/ip-sysctl.txt | 8
We want to have some more space in our queue for processing incoming
multicast packets, so we can process more of them without dropping
them prematurely. It is useful to be able to increase this limit on
higher-spec platforms that can handle more items.
For the particular use case here at Allied
Le jeu. 25 juil. 2019 à 12:59, Paul Burton a
écrit :
Hi Paul,
On Wed, Jul 24, 2019 at 07:46:54PM -0400, Paul Cercueil wrote:
Support partial kernel mode of Xburst CPUs found in Ingenic SoCs.
Partial kernel mode means the userspace applications have access to
the TCSM0 banks of the VPU,
We want to be able to keep more spaces available in our queue for
processing incoming multicast traffic (adding (S,G) entries) - this lets
us learn more groups faster, rather than dropping them at this stage.
Signed-off-by: Brodie Greenfield
---
Documentation/networking/ip-sysctl.txt | 8
On 7/25/19 12:22 AM, Thomas Gleixner wrote:
>>
>> The problem with this is that it will break silently when changes are
>> made to this structure.
>
> That's not really the worst problem. Changes to that struct which touch any
> of the to be cleared ranges will break anyway if not handled
On Thu, 2019-07-25 at 20:32 +0200, David Hildenbrand wrote:
> On 25.07.19 19:38, Alexander Duyck wrote:
> > On Thu, 2019-07-25 at 18:48 +0200, David Hildenbrand wrote:
> > > On 25.07.19 17:59, Alexander Duyck wrote:
> > > > On Thu, Jul 25, 2019 at 1:53 AM David Hildenbrand
> > > > wrote:
> > > >
It seems from the very beginning the error check has been missed
in axp288_extcon_log_rsi(). Add it here.
Cc: Ramakrishna Pallala
Signed-off-by: Andy Shevchenko
---
drivers/extcon/extcon-axp288.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/extcon/extcon-axp288.c
This simplifies and standardizes axp288_extcon_log_rsi()
by using for_each_set_bit() library function.
Signed-off-by: Andy Shevchenko
---
drivers/extcon/extcon-axp288.c | 13 +
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/drivers/extcon/extcon-axp288.c
On Thu, Jul 25, 2019 at 02:28:28PM -0600, Logan Gunthorpe wrote:
>
>
> On 2019-07-25 1:58 p.m., Keith Busch wrote:
> > On Thu, Jul 25, 2019 at 11:54:18AM -0600, Logan Gunthorpe wrote:
> >>
> >>
> >> On 2019-07-25 11:50 a.m., Matthew Wilcox wrote:
> >>> On Thu, Jul 25, 2019 at 11:23:23AM -0600,
On 7/25/19 12:22 AM, Thomas Gleixner wrote:
> On Wed, 24 Jul 2019, h...@zytor.com wrote:
>> On July 24, 2019 4:15:28 PM PDT, john.hubb...@gmail.com wrote:
>>> From: John Hubbard
>>>
>>> Recent gcc compilers (gcc 9.1) generate warnings about an
>>> out of bounds memset, if you trying memset across
Am Mittwoch, 24. Juli 2019, 00:52:58 CEST schrieb Matthias Kaehlcke:
> The downstream Chrome OS 3.14 kernel for jerry limits WiFi TX power
> through calibration data in the device tree [1]. Add a DT node for
> the WiFi chip and use the downstream calibration data.
>
> Not all calibration data
On Thu, Jul 25, 2019 at 08:10:49AM +0200, Sedat Dilek wrote:
> On Thu, Jul 25, 2019 at 12:48 AM Josh Poimboeuf wrote:
> >
> > Objtool reports:
> >
> > drivers/gpu/drm/i915/gem/i915_gem_execbuffer.o: warning: objtool:
> > .altinstr_replacement+0x36: redundant UACCESS disable
> >
> >
On Thu, Jul 25, 2019 at 07:06:19PM +0200, Paolo Bonzini wrote:
> On 25/07/19 18:39, Dan Rue wrote:
> > To your point Paolo - reporting 'fail' because of a missing kernel
> > feature is a generic problem we see across test suites, and causes tons
> > of pain and misery for CI people. As a general
On 7/25/19 4:00 PM, Alexander Duyck wrote:
> On Thu, 2019-07-25 at 14:25 -0400, Nitesh Narayan Lal wrote:
>> On 7/25/19 12:16 PM, Alexander Duyck wrote:
>>> On Thu, 2019-07-25 at 11:16 -0400, Michael S. Tsirkin wrote:
On Thu, Jul 25, 2019 at 08:05:30AM -0700, Alexander Duyck wrote:
> On
Add the of_device_id struct and the respective
of_match_device entry to complete device tree support.
Signed-off-by: Kartik Kulkarni
Reviewed-by: Matheus Tavares
---
drivers/staging/iio/adc/ad7280a.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git
On 19/07/25 08:33PM, Andy Shevchenko wrote:
> On Sun, Jun 30, 2019 at 8:41 AM Ayman Bagabas wrote:
> >
> > This patch series introduce changes to huawei-wmi driver that includes:
> > * Move to platform driver
> > * Implement WMI management interface
> > * Add micmute LED support through WMI
> > *
KBUILD_CFLAGS is very carefully built up in the top level Makefile,
particularly when cross compiling or using different build tools.
Resetting KBUILD_CFLAGS via := assignment is an antipattern.
The comment above the reset mentions that -pg is problematic. Other
Makefiles use
Add the of_device_id struct and the respective
of_match_device entry to complete device tree support.
Signed-off-by: Kartik Kulkarni
Reviewed-by: Matheus Tavares
---
drivers/staging/iio/adc/ad7280a.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/staging/iio/adc/ad7280a.c
1. Reuse the implementation of memcpy and memset instead of relying on
__builtin_memcpy and __builtin_memset as it causes infinite recursion
in Clang (at any opt level) or GCC at -O2.
2. Don't reset KBUILD_CFLAGS, rather filter CONFIG_FUNCTION_TRACER,
CONFIG_STACKPROTECTOR, and
Implementing memcpy and memset in terms of __builtin_memcpy and
__builtin_memset is problematic.
GCC at -O2 will replace calls to the builtins with calls to memcpy and
memset (but will generate an inline implementation at -Os). Clang will
replace the builtins with these calls regardless of
On Wed, Jul 24, 2019 at 10:08:57AM -0700, Linus Torvalds wrote:
> On Wed, Jul 24, 2019 at 6:09 AM Rasmus Villemoes
> wrote:
> >
> > The kernel's snprintf() does not behave in a non-standard way, at least
> > not with respect to its return value.
>
> Note that the kernels snprintf() *does* very
Awesome, thanks for the update! I will wait for the next upstrem...
Besides this minor problem everything is wonderful!
Even retroarch works now!
With 4.18.x 5.1.x and 5.2.x freeze the entire system when access amdgpu...
Thanks a lot!
---
Gilberto Nunes Ferreira
(47) 3025-5907
(47) 99676-7530 -
On Thursday, July 25, 2019 9:52:59 PM CEST Keith Busch wrote:
> On Thu, Jul 25, 2019 at 09:48:57PM +0200, Rafael J. Wysocki wrote:
> > NVME Identify Controller:
> > vid : 0x1c5c
> > ssvid : 0x1c5c
> > sn : MS92N171312902J0N
> > mn : PC401 NVMe SK hynix 256GB
> >
Hi Luis,
On Wed, Jul 10, 2019 at 10:20:55AM +, Luis de Oliveira wrote:
> Hi Sakari,
>
> From: Sakari Ailus
> Date: Tue, Jul 09, 2019 at 19:25:00
>
> > Hi Luis,
> >
> > On Mon, Jul 08, 2019 at 03:21:50PM +, Luis de Oliveira wrote:
> > > Hi Sakari,
> > >
> > > Thank you for your
On Thu, 2019-07-25 at 14:25 -0400, Nitesh Narayan Lal wrote:
> On 7/25/19 12:16 PM, Alexander Duyck wrote:
> > On Thu, 2019-07-25 at 11:16 -0400, Michael S. Tsirkin wrote:
> > > On Thu, Jul 25, 2019 at 08:05:30AM -0700, Alexander Duyck wrote:
> > > > On Thu, 2019-07-25 at 07:35 -0400, Nitesh
On Thu, Jul 25, 2019 at 08:22:06AM +0200, Alexandre Ghiti wrote:
> On 7/24/19 7:58 AM, Alexandre Ghiti wrote:
> > This commit simply bumps up to 32MB and 1GB the random offset
> > of brk, compared to 8MB and 256MB, for 32bit and 64bit respectively.
> >
> > Suggested-by: Kees Cook
> >
201 - 300 of 1107 matches
Mail list logo