As described in the patch ("mmc: core: Add sdio_trigger_replug()
API"), the current mwifiex_sdio_card_reset() is broken in the cases
where we're running Bluetooth on a second SDIO func on the same card
as WiFi. The problem goes away if we just use the
sdio_trigger_replug() API call.
NOTE: Even th
When using Marvell WiFi SDIO cards, it is not uncommon for Linux WiFi
driver to fully lose the communication channel to the firmware running
on the card. Presumably the firmware on the card has a bug or two in
it and occasionally crashes.
The Marvell WiFi driver attempts to recover from this prob
Quoting Paul Cercueil (2019-07-14 14:57:15)
> Remove the OF_POPULATED flag, in order to probe children when the
> device node is compatible with "simple-mfd".
We have CLK_OF_DECLARE_DRIVER for this. Can you use that?
>
> Signed-off-by: Paul Cercueil
> ---
> drivers/clk/ingenic/cgu.c | 6 ++
On 7/16/19 8:00 AM, Dmitry Osipenko wrote:
16.07.2019 11:06, Peter De Schrijver пишет:
On Tue, Jul 16, 2019 at 03:24:26PM +0800, Joseph Lo wrote:
OK, Will add to CPUFreq driver...
The other thing that also need attention is that T124 CPUFreq driver
implicitly relies on DFLL driver to be prob
On Tue, Jul 16, 2019 at 11:43:05AM -0400, Qian Cai wrote:
> The commit 6413139dfc64 ("skbuff: increase verbosity when dumping skb
> data") introduced a few compilation warnings.
>
> net/core/skbuff.c:766:32: warning: format specifies type 'unsigned
> short' but the argument has type 'unsigned int'
On 7/16/19 12:04 PM, Jan Stancek wrote:
> LTP mtest06 has been observed to rarely hit "still mapped when deleted"
> and following BUG_ON on arm64:
> page:7e02fa37e480 refcount:3 mapcount:1 mapping:80be3d678ab0
> index:0x0
> xfs_address_space_operations [xfs]
> flags: 0xbfffe00037
On Tue, Jul 16, 2019 at 9:08 AM Michael S. Tsirkin wrote:
>
> On Tue, Jul 16, 2019 at 08:37:06AM -0700, Alexander Duyck wrote:
> > On Tue, Jul 16, 2019 at 2:55 AM Michael S. Tsirkin wrote:
> > >
> > > On Wed, Jun 19, 2019 at 03:33:38PM -0700, Alexander Duyck wrote:
> > > > From: Alexander Duyck
Le mar. 16 juil. 2019 à 12:48, Stephen Boyd a
écrit :
Quoting Paul Cercueil (2019-07-14 14:57:15)
Remove the OF_POPULATED flag, in order to probe children when the
device node is compatible with "simple-mfd".
We have CLK_OF_DECLARE_DRIVER for this. Can you use that?
Didn't see it. I'l
I could add another patch to the series for that. Any suggestion for what
capability to check for here?
(There is always an alternative to not check for anything and let the kernel
refuse to perform actions that the user does not have permissions to perform.)
- Igor
-Original Message-
On Tue, Jul 16, 2019 at 02:47:56PM +0200, Thomas Gleixner wrote:
> The gold linker has known issues of failing the build in random and
> predictible ways. H.J. stated:
>
> "Since building a workable kernel for different kernel configurations
>isn't a requirement for gold, I don't recommend g
By using CLK_OF_DECLARE_DRIVER instead of the CLK_OF_DECLARE macro, we
allow the driver to probe also as a platform driver.
While this driver does not have code to probe as a platform driver, this
is still useful for probing children devices in the case where the
device node is compatible with "si
Hi David,
On 7/10/19 12:08 PM, David Lechner wrote:
>
+- interrupts : all the interrupts generated towards the
main host
+ processor in the SoC. The format depends
on the
+ interrupt specifier for the particular
>>
On Fri, Mar 22, 2019 at 04:03:07PM +, Chris Down wrote:
> This patch is an incremental improvement on the existing
> memory.{low,min} relative reclaim work to base its scan pressure
> calculations on how much protection is available compared to the current
> usage, rather than how much the curr
вт, 9 июл. 2019 г. в 13:40, Andrii Nakryiko :
>
> On Mon, Jul 8, 2019 at 1:37 PM Anton Protopopov
> wrote:
> >
> > пн, 8 июл. 2019 г. в 13:54, Andrii Nakryiko :
> > >
> > > On Fri, Jul 5, 2019 at 2:53 PM Daniel Borkmann
> > > wrote:
> > > >
> > > > On 07/05/2019 10:44 PM, Anton Protopopov wrote:
The following changes since commit 3ff46efbcd90d3d469de8eddaf03d12293aaa50c:
clk: meson: meson8b: fix a typo in the VPU parent names array variable
(2019-05-20 12:11:08 +0200)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
tags/clk-for
During enabling of the RPi 4, we found out that the driver doesn't provide
a helpful error message in case setting DMA mask fails. So add one.
Signed-off-by: Stefan Wahren
---
drivers/dma/bcm2835-dma.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/dma/bcm2835-dma
Hey Saravana,
Thanks for taking time to post out this series.
On 6/26/19 3:03 AM, Saravana Kannan wrote:
A Device-A can have a (minimum) performance requirement on another
Device-B to be able to function correctly. This performance requirement
on Device-B can also change based on the current per
On 7/16/19 1:12 AM, Vlastimil Babka wrote:
On 6/22/19 2:20 AM, Yang Shi wrote:
When both MPOL_MF_MOVE* and MPOL_MF_STRICT was specified, mbind() should
try best to migrate misplaced pages, if some of the pages could not be
migrated, then return -EIO.
There are three different sub-cases:
1. v
On 7/16/19 1:47 AM, Vlastimil Babka wrote:
On 7/16/19 10:12 AM, Vlastimil Babka wrote:
--- a/mm/mempolicy.c
+++ b/mm/mempolicy.c
@@ -429,11 +429,14 @@ static inline bool queue_pages_required(struct page *page,
}
/*
- * queue_pages_pmd() has three possible return values:
+ * queue_page
Hi, Peter.
Thanks for the review and all the suggestions!
A couple of comments are inlined below.
> On Jul 16, 2019, at 11:50 AM, Peter Zijlstra wrote:
>
> On Mon, Jul 15, 2019 at 03:25:34PM -0400, Alex Kogan wrote:
>> +static struct cna_node *find_successor(struct mcs_spinlock *me)
>> +{
>> +
Hi David,
On 7/11/19 11:45 AM, David Lechner wrote:
> On 7/7/19 10:52 PM, Suman Anna wrote:
>> From: "Andrew F. Davis"
>>
>> The Programmable Real-Time Unit Subsystem (PRUSS) contains a local
>> interrupt controller (INTC) that can handle various system input events
>> and post interrupts back to
On Mon, Jul 15, 2019 at 03:35:27PM -0700, Andrew Morton wrote:
> On Mon, 28 Jan 2019 21:52:40 + Roman Gushchin wrote:
>
> > > Hmm, this isn't really a common situation that I'd thought about, but it
> > > seems reasonable to make the boundaries when in low reclaim to be between
> > > min and
Hey Saravana,
https://patchwork.kernel.org/patch/10850815/
There was already a discussion ^^ on how bandwidth bindings were to be
named.
On 7/3/19 6:40 AM, Saravana Kannan wrote:
Interconnects often quantify their performance points in terms of
bandwidth. So, add opp-peak-KBps (required) and op
On Thu, Jul 11, 2019 at 7:15 PM Joe Perches wrote:
>
> On Thu, 2019-07-11 at 17:17 -0700, Nick Desaulniers wrote:
> > Commit r353569 in prerelease Clang-9 is producing a linkage failure:
> >
> > ld: drivers/net/wireless/intel/iwlwifi/fw/dbg.o:
> > in function `_iwl_fw_dbg_apply_point':
> > dbg.c:(
fix below issue reported by coccicheck
drivers/infiniband/hw/qib/qib_file_ops.c:1792:5-8: Unneeded variable:
"ret". Return "0" on line 1876
Signed-off-by: Hariprasad Kelam
---
drivers/infiniband/hw/qib/qib_file_ops.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/i
On 7/16/19 5:07 AM, Vlastimil Babka wrote:
On 6/22/19 2:20 AM, Yang Shi wrote:
@@ -969,10 +975,21 @@ static long do_get_mempolicy(int *policy, nodemask_t
*nmask,
/*
* page migration, thp tail pages can be passed.
*/
-static void migrate_page_add(struct page *page, struct list_head *p
Hey Saravana,
On 7/3/19 6:40 AM, Saravana Kannan wrote:
Not all devices quantify their performance points in terms of frequency.
Devices like interconnects quantify their performance points in terms of
bandwidth. We need a way to represent these bandwidth levels in OPP. So,
add support for parsi
The pull request you sent on Mon, 15 Jul 2019 09:00:09 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git
> backlight-next-5.3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/50950626414a982c8ed539128c7f69a3d328a970
Thank you!
--
Deet-doot-dot,
Hey Saravana,
On 6/26/19 3:03 AM, Saravana Kannan wrote:
The OPP table can be used often in devfreq. Trying to get it each time can
be expensive, so cache it in the devfreq struct.
Signed-off-by: Saravana Kannan
---
drivers/devfreq/devfreq.c | 6 ++
include/linux/devfreq.h | 1 +
2 f
fix below issue reported by coccicheck
drivers/infiniband/hw/qedr/verbs.c:2454:5-7: Unneeded variable: "rc".
Return "0" on line 2499
Signed-off-by: Hariprasad Kelam
---
drivers/infiniband/hw/qedr/verbs.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/infiniband/hw/
On 7/15/19 8:01 AM, Catalin Marinas wrote:
On 15 Jul 2019, at 08:17, Michal Hocko wrote:
On Sat 13-07-19 04:49:04, Yang Shi wrote:
When running ltp's oom test with kmemleak enabled, the below warning was
triggerred since kernel detects __GFP_NOFAIL & ~__GFP_DIRECT_RECLAIM is
passed in:
kme
On Tue, Jul 16, 2019 at 09:54:37AM -0700, Alexander Duyck wrote:
> On Tue, Jul 16, 2019 at 9:08 AM Michael S. Tsirkin wrote:
> >
> > On Tue, Jul 16, 2019 at 08:37:06AM -0700, Alexander Duyck wrote:
> > > On Tue, Jul 16, 2019 at 2:55 AM Michael S. Tsirkin
> > > wrote:
> > > >
> > > > On Wed, Jun
When running ltp's oom test with kmemleak enabled, the below warning was
triggerred since kernel detects __GFP_NOFAIL & ~__GFP_DIRECT_RECLAIM is
passed in:
WARNING: CPU: 105 PID: 2138 at mm/page_alloc.c:4608
__alloc_pages_nodemask+0x1c31/0x1d50
Modules linked in: loop dax_pmem dax_pmem_core ip_ta
On Fri, 12 Jul 2019 00:13:57 +0300
Jarkko Sakkinen wrote:
> On Thu, Jul 11, 2019 at 11:28:24PM +0300, Jarkko Sakkinen wrote:
> > On Thu, Jul 11, 2019 at 12:13:35PM -0400, Nayna Jain wrote:
> > > The nr_allocated_banks and allocated banks are initialized as part of
> > > tpm_chip_register. Curre
On 16-Jul 17:29, Michal Koutný wrote:
> On Tue, Jul 16, 2019 at 03:07:06PM +0100, Patrick Bellasi
> wrote:
> > That note comes from the previous review cycle and it's based on a
> > request from Tejun to align uclamp behaviors with the way the
> > delegation model is supposed to work.
> I saw and
On 16-Jul 17:36, Michal Koutný wrote:
> On Tue, Jul 16, 2019 at 03:34:17PM +0100, Patrick Bellasi
> wrote:
> > > cpu_util_update_eff internally calls css_for_each_descendant_pre() so
> > > this should be protected with rcu_read_lock().
> >
> > Right, good catch! Will add in v12.
> When I respond
On 7/16/19 1:36 AM, Greg Kroah-Hartman wrote:
> On Mon, Jul 15, 2019 at 02:21:23PM -0700, john.hubb...@gmail.com wrote:
>> From: John Hubbard
...
>> drivers/staging/kpc2000/kpc2000_i2c.c | 189 +++--
>> drivers/staging/kpc2000/kpc2000_spi.c | 116 +-
>> drivers
Axel
On 7/7/19 9:02 PM, Axel Lin wrote:
Axel Lin 於 2019年6月26日 週三 下午11:12寫道：
Dan Murphy 於 2019年6月26日 週三 下午11:07寫道：
Hello
On 6/26/19 8:26 AM, Axel Lin wrote:
According to the datasheet https://www.ti.com/lit/ds/symlink/lm3632a.pdf
Table 20. VPOS Bias Register Field Descriptions VPOS[5:0]
Set
Hey Saravana,
On 6/18/19 2:48 AM, Saravana Kannan wrote:
On Mon, Jun 17, 2019 at 8:44 AM Georgi Djakov wrote:
Hi Saravana,
On 6/14/19 07:17, Saravana Kannan wrote:
Add a icc_create_devfreq() and icc_remove_devfreq() to create and remove
devfreq devices for interconnect paths. A driver can c
* Thomas Gleixner wrote:
> On Tue, 16 Jul 2019, Ingo Molnar wrote:
>
> >
> > * Thomas Gleixner wrote:
> >
> > > The gold linker has known issues of failing the build in random and
> > > predictible ways. H.J. stated:
> >
> > s/predictable/unpredictable?
>
> No. It fails randomly, but also
On Sun, Jul 14, 2019 at 5:37 PM Josh Poimboeuf wrote:
>
> On x86-64, with CONFIG_RETPOLINE=n, GCC's "global common subexpression
> elimination" optimization results in ___bpf_prog_run()'s jumptable code
> changing from this:
>
> select_insn:
> jmp *jumptable(, %rax, 8)
>
On Sun, Jul 14, 2019 at 5:37 PM Josh Poimboeuf wrote:
>
> After an objtool improvement, it's complaining about the CLAC in
> copy_user_handle_tail():
>
> arch/x86/lib/copy_user_64.o: warning: objtool: .altinstr_replacement+0x12:
> redundant UACCESS disable
> arch/x86/lib/copy_user_64.o: warni
On Tue, Jul 16, 2019 at 04:54:23PM +0800, Mao Wenan wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/input/keyboard/applespi.c: In function applespi_set_bl_level:
> drivers/input/keyboard/applespi.c:902:6: warning: variable sts set but not
> used [-Wunused-but-set-variable]
>
The patch
ASoC: samsung: odroid: fix an use-after-free issue for codec
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
On Tue, Jul 16, 2019 at 2:15 PM KyleMahlkuch
wrote:
>
> During kexec some adapters hit an EEH since they are not properly
> shut down in the radeon_pci_shutdown() function. Adding
> radeon_suspend_kms() fixes this issue.
>
> Since radeon.h is now included in radeon_drv.c radeon_init() needs
> a ne
The patch
ASoC: samsung: odroid: fix a double-free issue for cpu_dai
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 2
The patch
regulator: axp20x: fix DCDC5 and DCDC6 for AXP803
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 2
The patch
regulator: axp20x: fix DCDCA and DCDCD for AXP806
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 2
Hi,
On 7/16/19 9:21 AM, Dmitry Torokhov wrote:
When you are saying that Pro 4 and later models use different
notifications, does this mean that Pro 4 does not define any GPIOs?
Unfortunately, at least the Surface Book (first generation, buttons are
handled the same way as on the Pro 4) has G
On Tue, Jul 16, 2019 at 02:54:11PM +0800, YueHaibing wrote:
> trackpoint_detect() should be static inline while
> CONFIG_MOUSE_PS2_TRACKPOINT is not set. otherwire,we
> got building fails:
>
> drivers/input/mouse/alps.o: In function `trackpoint_detect':
> alps.c:(.text+0x8e00): multiple definition
On 7/16/19 9:50 AM, Sowjanya Komatineni wrote:
On 7/16/19 8:00 AM, Dmitry Osipenko wrote:
16.07.2019 11:06, Peter De Schrijver пишет:
On Tue, Jul 16, 2019 at 03:24:26PM +0800, Joseph Lo wrote:
OK, Will add to CPUFreq driver...
The other thing that also need attention is that T124 CPUFreq d
On Mon, Jul 15, 2019 at 05:04:03PM +0200, Thomas Gleixner wrote:
> Add a new entry to the preemption menu which enables the real-time support
> for the kernel. The choice is only enabled when an architecture supports
> it.
>
> It selects PREEMPT as the RT features depend on it. To achieve that the
Hello
On 5/15/19 3:54 PM, Dan Murphy wrote:
Marc
On 5/9/19 11:11 AM, Dan Murphy wrote:
Create a m_can platform framework that peripheral
devices can register to and use common code and register sets.
The peripheral devices may provide read/write and configuration
support of the IP.
Acked-by:
On Wed, 2019-07-17 at 01:50 +0800, Yang Shi wrote:
> When running ltp's oom test with kmemleak enabled, the below warning was
> triggerred since kernel detects __GFP_NOFAIL & ~__GFP_DIRECT_RECLAIM is
> passed in:
>
> WARNING: CPU: 105 PID: 2138 at mm/page_alloc.c:4608
> __alloc_pages_nodemask+0x1c
On 15.07.19 16:38, Florian Eckert wrote:
> I plugged in a mpcie usb modem.
> In my test case it was a EC25 from Quectel in mpcie2 port.
> After that I did a reboot and exported the gpio via "/sys/class/gpio"
> Then I executed the command "echo 0 > /sys/class/gpio//value" and
> "echo 1 > /sys/clas
16.07.2019 21:19, Sowjanya Komatineni пишет:
>
> On 7/16/19 9:50 AM, Sowjanya Komatineni wrote:
>>
>> On 7/16/19 8:00 AM, Dmitry Osipenko wrote:
>>> 16.07.2019 11:06, Peter De Schrijver пишет:
On Tue, Jul 16, 2019 at 03:24:26PM +0800, Joseph Lo wrote:
>> OK, Will add to CPUFreq driver...
On Wed, Jul 10, 2019 at 10:44 AM Jeffrin Thalakkottoor
wrote:
>
> hello all ,
>
> i encountered a KASAN bug related .here are some related information...
>
>
> ---x-x--
> [ 30.037312] BUG: KASAN: global-out-of-bounds in
> ata_exec_i
On 7/16/19 11:25 AM, Dmitry Osipenko wrote:
16.07.2019 21:19, Sowjanya Komatineni пишет:
On 7/16/19 9:50 AM, Sowjanya Komatineni wrote:
On 7/16/19 8:00 AM, Dmitry Osipenko wrote:
16.07.2019 11:06, Peter De Schrijver пишет:
On Tue, Jul 16, 2019 at 03:24:26PM +0800, Joseph Lo wrote:
OK, Will
Hi Vishal,
On Thu, Jul 11, 2019 at 09:09:37AM +, Vishal Sagar wrote:
...
> > > +static int xcsi2rxss_subscribe_event(struct v4l2_subdev *sd,
> > > + struct v4l2_fh *fh,
> > > + struct v4l2_event_subscription *sub)
> > > +{
> > >
- Original Message -
> On 7/16/19 12:04 PM, Jan Stancek wrote:
> > LTP mtest06 has been observed to rarely hit "still mapped when deleted"
> > and following BUG_ON on arm64:
> > page:7e02fa37e480 refcount:3 mapcount:1 mapping:80be3d678ab0
> > index:0x0
> > xfs_address_space
16.07.2019 21:30, Sowjanya Komatineni пишет:
>
> On 7/16/19 11:25 AM, Dmitry Osipenko wrote:
>> 16.07.2019 21:19, Sowjanya Komatineni пишет:
>>> On 7/16/19 9:50 AM, Sowjanya Komatineni wrote:
On 7/16/19 8:00 AM, Dmitry Osipenko wrote:
> 16.07.2019 11:06, Peter De Schrijver пишет:
>> O
Em Thu, Jul 11, 2019 at 11:19:20AM -0700, Andi Kleen escreveu:
> From: Andi Kleen
>
> The --max-blocks description was using the old name brstackasm.
> Use brstackinsn instead.
Thanks, applied.
- Arnaldo
Em Thu, Jul 11, 2019 at 11:19:21AM -0700, Andi Kleen escreveu:
> From: Andi Kleen
>
> When we hit the end of a program block, need to count the last instruction
> too for the IPC computation. This caused large errors for small blocks.
>
> % perf script -b ls / > /dev/null
>
> Before:
Thanks, a
On Mon, Jul 15, 2019 at 10:37:04AM -0400, Joel Fernandes (Google) wrote:
> list_for_each_entry_rcu has built-in RCU and lock checking. Make use of
> it for acpi_ioremaps list traversal.
>
> Signed-off-by: Joel Fernandes (Google)
Given that Rafael acked it, this one looks ready.
Em Thu, Jul 11, 2019 at 11:19:22AM -0700, Andi Kleen escreveu:
> From: Andi Kleen
>
> Clarify that a metric is based on events, not referring
> to itself. Also some improvements with the sentences.
Thanks, applied.
On Wed, Jul 10, 2019 at 12:59:18PM +0200, Miroslav Benes wrote:
> The livepatch consistency model requires reliable stack tracing
> architecture support in order to work properly. In order to achieve
> this, two main issues have to be solved. First, reliable and consistent
> call chain backtracing
On Tue, Jul 16, 2019 at 11:13 AM Ingo Molnar wrote:
>
> Then please make this a bit more apparent, such as:
>
> "The gold linker has known issues of failing the build in random
> but also in more predictible ways."
Maybe even mention a couple of particular known failure cases.
Just in case so
Em Mon, Jul 15, 2019 at 04:04:26PM +0200, Jiri Olsa escreveu:
> After Song Liu's segfault fix for pipe mode, Arnaldo reported
> following error:
>
> # perf record -o - | perf script
> 0x514 [0x1ac]: failed to process type: 80
Thanks, tested and applied.
- Arnaldo
On Tue, Jul 16, 2019 at 01:19:16PM -0400, Alex Kogan wrote:
> > On Jul 16, 2019, at 11:50 AM, Peter Zijlstra wrote:
> > static void cna_move(struct cna_node *cn, struct cna_node *cni)
> > {
> > struct cna_node *head, *tail;
> >
> > /* remove @cni */
> > WRITE_ONCE(cn->mcs.next, cni->
Em Mon, Jul 15, 2019 at 04:21:21PM +0200, Jiri Olsa escreveu:
> Numfor Mbiziwo-Tiapo reported segfault on stat of event
> group in repeat mode:
>
> # perf stat -e '{cycles,instructions}' -r 10 ls
>
> It's caused by memory corruption due to not cleaned
> evsel's id array and index, which needs t
On Tue, Jul 16, 2019 at 8:21 AM Rafael J. Wysocki wrote:
>
> From: Rafael J. Wysocki
> Subject: [PATCH] driver core: Remove device link creation limitation
>
> If device_link_add() is called for a consumer/supplier pair with an
> existing device link between them and the existing link's type is
>
Em Mon, Jul 15, 2019 at 03:30:24PM +0300, Alexey Budankov escreveu:
> On 14.07.2019 18:49, Jiri Olsa wrote:
> > On Tue, Jul 09, 2019 at 05:48:14PM +0300, Alexey Budankov wrote:
> >
> > SNIP
> >
> >>decomp->file_pos = file_offset;
> >> + decomp->mmap_len = mmap_len;
> >>decomp->head = 0;
On Tue, Jul 16, 2019 at 11:16:48AM -0700, Nick Desaulniers wrote:
> On Sun, Jul 14, 2019 at 5:37 PM Josh Poimboeuf wrote:
> >
> > After an objtool improvement, it's complaining about the CLAC in
> > copy_user_handle_tail():
> >
> > arch/x86/lib/copy_user_64.o: warning: objtool:
> > .altinstr_re
On Tue, Jul 16, 2019 at 08:13:24PM +0200, Ingo Molnar wrote:
>
> * Thomas Gleixner wrote:
>
> > On Tue, 16 Jul 2019, Ingo Molnar wrote:
> >
> > >
> > > * Thomas Gleixner wrote:
> > >
> > > > The gold linker has known issues of failing the build in random and
> > > > predictible ways. H.J. st
On Tue, Jul 16, 2019 at 10:18 AM Sibi Sankar wrote:
>
> Hey Saravana,
> Thanks for taking time to post out this series.
>
> On 6/26/19 3:03 AM, Saravana Kannan wrote:
> > A Device-A can have a (minimum) performance requirement on another
> > Device-B to be able to function correctly. This performa
On Thu 2019-07-11 19:51:25, Amit Kucheria wrote:
> The network_latency and network_throughput flags for PM-QoS have not
> found much use in drivers or in userspace since they were introduced.
>
> Commit 4a733ef1bea7 ("mac80211: remove PM-QoS listener") removed the
> only user PM_QOS_NETWORK_LATENC
On Tue, 16 Jul 2019 11:28:29 -0700
Nick Desaulniers wrote:
> The cited code looks like a check comparing that the pointer distance
> is greater than the size of bytes being passed in. I'd wager
> someone's calling memmove with overlapping memory regions when they
> really wanted memcpy. Maybe a
On Tue, Jul 16, 2019 at 10:25 AM Sibi Sankar wrote:
>
> Hey Saravana,
>
> https://patchwork.kernel.org/patch/10850815/
> There was already a discussion ^^ on how bandwidth bindings were to be
> named.
Yes, I'm aware of that series. That series is trying to define a BW
mapping for an existing freq
On Tue, Jul 16, 2019 at 12:53:14PM -0400, Waiman Long wrote:
> On 7/16/19 12:04 PM, Jan Stancek wrote:
> > Suspected problem here is that last *_acquire on down_read() side
> > happens before write side issues *_release:
> > 1. writer: has the lock
> > 2. reader: down_read() issues *read_acqui
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the Git repository at:
git://github.com/andersson/remoteproc tags/rpmsg-v5.3
for you to fetch changes up to 54119bc1110dab2fa389f45c73a0787b8e037e8b:
rp
On Tue, 16 Jul 2019, Nathan Chancellor wrote:
> On Tue, Jul 16, 2019 at 02:47:56PM +0200, Thomas Gleixner wrote:
> > The gold linker has known issues of failing the build in random and
> > predictible ways. H.J. stated:
> >
> > "Since building a workable kernel for different kernel configuration
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the Git repository at:
git://github.com/andersson/remoteproc tags/rproc-v5.3
for you to fetch changes up to 93f1d3e4b59cf2e7ef31eaf1131480897b040e97:
re
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the Git repository at:
git://github.com/andersson/remoteproc tags/hwlock-v5.3
for you to fetch changes up to 360aa640a59f269b784848c0b2d6d462952750d9:
h
On Tue, Jul 16, 2019 at 12:22:25PM +0100, Lorenzo Pieralisi wrote:
> On Sat, Jul 13, 2019 at 12:34:34PM +0530, Vidya Sagar wrote:
> > > > > So if the link is not up we still go ahead and make probe
> > > > > succeed. What for ?
> > > > We may need root port to be available to support hot-plugging
Bah, I had this tested last week before going on PTO and forgot to push
it to my for-next branch. But it's for this merge window.
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: f86a1152e15c6b5913f9ec03a2bd97ca70c1ed82
Cong Wang (3):
tracing: Pa
From: "Steven Rostedt (VMware)"
While testing on a very old kernel (3.5), the tests failed because the write
to set_event_pid in the setup code, did not exist. The tests themselves
could pass, but the setup failed causing an error.
Other files test for existance before writing to them. Do the sa
From: "Steven Rostedt (VMware)"
If the kernel is not configured with ftrace enabled, the ftracetest
selftests should return the error code of "4" as that is the kselftests
"skip" code, and not "1" which means an error.
To determine if ftrace is enabled, first the newer "tracefs" is searched for
From: Cong Wang
All callers of tracing_generic_entry_update() have to initialize
entry->type, so let's just simply move it inside.
Link: http://lkml.kernel.org/r/20190525165802.25944-2-xiyou.wangc...@gmail.com
Cc: Ingo Molnar
Signed-off-by: Cong Wang
Signed-off-by: Steven Rostedt (VMware)
---
On 7/16/19 11:23 AM, Qian Cai wrote:
On Wed, 2019-07-17 at 01:50 +0800, Yang Shi wrote:
When running ltp's oom test with kmemleak enabled, the below warning was
triggerred since kernel detects __GFP_NOFAIL & ~__GFP_DIRECT_RECLAIM is
passed in:
WARNING: CPU: 105 PID: 2138 at mm/page_alloc.c:4
From: Cong Wang
filter_assign_type() could detect dynamic string and static
string, but not string pointers. Teach filter_assign_type()
to detect string pointers, and this will be needed by trace
event injection code.
BTW, trace event hist uses FILTER_PTR_STRING too.
Link: http://lkml.kernel.org
From: Cong Wang
trace_get_fields() is the only way to read tracepoint fields at
run time, as their fields are defined at compile-time with macros.
Make this function visible to all users and it will be used by
trace event injection code to calculate the size of a tracepoint
entry.
Link: http://lk
On Tue, Jul 16, 2019 at 6:53 PM Nathan Chancellor
wrote:
>
> On Tue, Jul 16, 2019 at 11:43:05AM -0400, Qian Cai wrote:
> > The commit 6413139dfc64 ("skbuff: increase verbosity when dumping skb
> > data") introduced a few compilation warnings.
> >
> > net/core/skbuff.c:766:32: warning: format speci
Neil,
On Tue, 16 Jul 2019, Neil Horman wrote:
> On Tue, Jul 16, 2019 at 05:57:31PM +0200, Thomas Gleixner wrote:
> > On Tue, 16 Jul 2019, Neil Horman wrote:
> > > If a cpu has more than this number of interrupts affined to it, they
> > > will spill over to other cpus, which potentially may be outs
On Mon, Jul 15, 2019 at 9:05 AM Micah Morton wrote:
>
> I'm maintaining the new SafeSetID LSM and was told to set up my own
> tree for sending pull requests rather than sending my changes through
> James Morris and the security subsystem tree.
Yes. It would be good if you also added yourself to t
On 7/16/19 2:58 PM, Peter Zijlstra wrote:
> On Tue, Jul 16, 2019 at 12:53:14PM -0400, Waiman Long wrote:
>> On 7/16/19 12:04 PM, Jan Stancek wrote:
> Fixes: 4b486b535c33 ("locking/rwsem: Exit read lock slowpath if queue empty &
> no writer")
> Signed-off-by: Jan Stancek
> Cc: Waiman Long
> Cc: D
On Tue, Jul 16, 2019 at 10:33 AM Sibi Sankar wrote:
>
> Hey Saravana,
>
> On 7/3/19 6:40 AM, Saravana Kannan wrote:
> > Not all devices quantify their performance points in terms of frequency.
> > Devices like interconnects quantify their performance points in terms of
> > bandwidth. We need a way
On Tue, Jul 16, 2019 at 10:36 AM Sibi Sankar wrote:
>
> Hey Saravana,
>
> On 6/26/19 3:03 AM, Saravana Kannan wrote:
> > The OPP table can be used often in devfreq. Trying to get it each time can
> > be expensive, so cache it in the devfreq struct.
> >
> > Signed-off-by: Saravana Kannan
> > ---
>
On 7/16/19 12:20 AM, Felipe Balbi wrote:
Add a driver supporting Intel Timed GPIO controller available as part
of some Intel PMCs.
Signed-off-by: Felipe Balbi
Hi Felipe, just a couple of quick comments:
There are several places where a line is continued on the next line, but
should be inden
On Tue, Jul 16, 2019 at 12:06 PM Linus Torvalds
wrote:
>
> - Please use the "git pull-request" format and then add any extra
> notes you feel are necessary
>
>Yes, your pull request is *almost* git pull-request, but you seem
> to have actively removed whitespace making it almost illegible. It
On Tue, Jul 16, 2019 at 11:13 AM Sibi Sankar wrote:
>
> Hey Saravana,
>
> On 6/18/19 2:48 AM, Saravana Kannan wrote:
> > On Mon, Jun 17, 2019 at 8:44 AM Georgi Djakov
> > wrote:
> >>
> >> Hi Saravana,
> >>
> >> On 6/14/19 07:17, Saravana Kannan wrote:
> >>> Add a icc_create_devfreq() and icc_rem
301 - 400 of 667 matches
Mail list logo
