Most of the TI drivers build just fine with COMPILE_TEST, cpmac (AR7) is
the exception because it uses a header file from
arch/mips/include/asm/mach-ar7/ar7.h and keystone netcp which requires
help from drivers/soc/ti/ for queue management helpers.
Signed-off-by: Florian Fainelli
---
drivers/net
Those drivers build just fine with COMPILE_TEST, so make that possible.
Signed-off-by: Florian Fainelli
---
drivers/net/phy/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/phy/Kconfig b/drivers/net/phy/Kconfig
index 0e2305ccc91f..343989f9f9d9 100644
--
From: Zhu Yi
Add Rohm BU21029 resistive touch panel controller support with I2C
interface.
Signed-off-by: Zhu Yi
Signed-off-by: Mark Jonas
Reviewed-by: Heiko Schocher
Reviewed-by: Rob Herring
---
Changes in v5:
- use usleep_range() and msleep() instead of atomic delays
- drop #ifdef CONFIG
Em Thu, May 17, 2018 at 10:58:38PM +0800, Jin Yao escreveu:
> In perf annotate view, a new hotkey 'c' is created for
> showing the max/min cycles.
I just changed everything from "max/min" to "min/max", as it looked
strange print the max first, thanks, applying.
- Arnaldo
> For example, when pre
On 5/17/2018 3:46 PM, Matthew Wilcox wrote:
>> Remember that the CPU core that is running this driver is most probably on
>> the same NUMA node as the device itself.
> Umm ... says who? If my process is running on NUMA node 5 and I submit
> an I/O, it should be allocating from a pool on node 5, no
Em Thu, May 17, 2018 at 12:03:25PM +0530, Sandipan Das escreveu:
> When perf data is recorded with the call-graph option enabled,
> the callchain shown by perf script shows the binary offsets of
> the symbols as the ip. This is incorrect for kernel symbols as
> the ip values are always off by a fix
Hi Neil,
I love your patch! Yet something to improve:
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.17-rc5 next-20180517]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On 05/17/2018 12:31 PM, Vince Weaver wrote:
> On Thu, 17 May 2018, Vince Weaver wrote:
>
>> On Thu, 17 May 2018, Peter Zijlstra wrote:
>> with cortex-a7 now, would it be possible to later drop that if proper
>> cortex-a53 support is added to the armv7 pmu driver? Or would that lead
>> to all ki
From: Hemanth Puranik
Date: Thu, 17 May 2018 13:58:00 +0530
> Currently we use non-NUMA aware allocation for TPD and RRD buffers,
> this patch modifies to use NUMA friendly allocation.
>
> Signed-off-by: Hemanth Puranik
> ---
> drivers/net/ethernet/qualcomm/emac/emac-mac.c | 6 --
> 1 file
From: YueHaibing
Date: Thu, 17 May 2018 11:46:41 +0800
> As documented in Documentation/timers/timers-howto.txt,
> replace msleep(1) with usleep_range().
>
> Signed-off-by: YueHaibing
Applied, thank you.
On Thu, May 17, 2018 at 03:46:58PM -0300, Eduardo Habkost wrote:
> On Thu, May 17, 2018 at 05:54:24PM +0300, Michael S. Tsirkin wrote:
> > HINTS_DEDICATED seems to be somewhat confusing:
> >
> > Guest doesn't really care whether it's the only task running on a host
> > CPU as long as it's not pree
On Thu, May 17, 2018 at 08:13:35PM +0300, Ville Syrjälä wrote:
> On Thu, May 17, 2018 at 06:49:47PM +0200, Michal Hocko wrote:
> > On Thu 17-05-18 16:58:32, Ville Syrjälä wrote:
> > > On Thu, May 17, 2018 at 04:36:29PM +0300, Ville Syrjälä wrote:
> > > > On Thu, May 17, 2018 at 03:21:09PM +0200, Mi
Hi Robin,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.17-rc5 next-20180517]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
* Linus Walleij [180514 08:08]:
> As we augmented the regulator core to accept a GPIO descriptor instead
> of a GPIO number, we can augment the fixed GPIO regulator to look up
> and pass that descriptor directly from device tree or board GPIO
> descriptor look up tables.
...
> arch/arm/mach-omap1
On 5/17/2018 4:24 AM, Rafael J. Wysocki wrote:
> On Thu, May 17, 2018 at 12:01 AM, Al Stone wrote:
>> There have been multiple reports of the following error message:
>>
>> [0.068293] Error parsing PCC subspaces from PCCT
>>
>> This error message is not correct. In multiple cases examined, t
* Andy Shevchenko [180517 16:38]:
> On Thu, May 17, 2018 at 4:48 PM, Tony Lindgren wrote:
> > * Sebastian Andrzej Siewior [180516 10:49]:
> >> On 2018-05-16 13:17:36 [+0300], Andy Shevchenko wrote:
> >> > > The output is usually short so there
> >> > > shouldn't be much benefit from using it.
>
On Thu, May 17, 2018 at 03:37:21PM -0400, Sinan Kaya wrote:
> On 5/17/2018 2:18 PM, Matthew Wilcox wrote:
> > On Thu, May 17, 2018 at 01:36:19PM -0400, Sinan Kaya wrote:
> >> Try to keep the pool closer to the device's NUMA node by changing kmalloc()
> >> to kmalloc_node() and devres_alloc() to dev
On 17/05/2018 12:28:59-0700, Joe Perches wrote:
> On Thu, 2018-05-17 at 21:23 +0200, Alexandre Belloni wrote:
> > ocelot_qsys.h is missing the SPDX identfier, fix that.
> >
> > Signed-off-by: Alexandre Belloni
>
> Only the copyright holders should ideally be modifying
> these and also removing o
On 5/17/2018 2:18 PM, Matthew Wilcox wrote:
> On Thu, May 17, 2018 at 01:36:19PM -0400, Sinan Kaya wrote:
>> Try to keep the pool closer to the device's NUMA node by changing kmalloc()
>> to kmalloc_node() and devres_alloc() to devres_alloc_node().
> Have you measured any performance gains by doing
> -Original Message-
> From: Vitaly Kuznetsov
> Sent: Thursday, May 17, 2018 12:06 AM
> To: KY Srinivasan
> Cc: k...@vger.kernel.org; x...@kernel.org; Paolo Bonzini
> ; Radim Krčmář ; Roman
> Kagan ; Haiyang Zhang ;
> Stephen Hemminger ; Michael Kelley (EOSG)
> ; Mohammed Gamal
> ; Cath
When run raidconfig from Dom0 we found that the Xen DMA heap is reduced,
but Dom Heap is increased by the same size. Tracing raidconfig we found
that the related ioctl() in megaraid_sas will call dma_alloc_coherent()
to apply memory. If the memory allocated by Dom0 is not in the DMA area,
it will e
On Thu, May 17, 2018 at 09:29:23PM +0200, Johannes Hirte wrote:
> Works as expected on my Carrizo.
Thanks, I'll add your Tested-by.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284
(AG Nürnberg)
--
On 5/17/18 12:10 PM, Greg KH wrote:
> On Thu, May 17, 2018 at 11:45:57AM -0700, Joe Jin wrote:
>> When run raidconfig from Dom0 we found that the Xen DMA heap is reduced,
>> but Dom Heap is increased by the same size. Tracing raidconfig we found
>> that the related ioctl() in megaraid_sas will call
On Thu, 17 May 2018, Vince Weaver wrote:
> On Thu, 17 May 2018, Peter Zijlstra wrote:
> with cortex-a7 now, would it be possible to later drop that if proper
> cortex-a53 support is added to the armv7 pmu driver? Or would that lead
> to all kinds of back-compatability mess?
For what it's worth
* Andy Shevchenko [180517 16:41]:
> On Thu, May 17, 2018 at 4:56 PM, Tony Lindgren wrote:
> > * Andy Shevchenko [180516 13:12]:
> >> On Wed, 2018-05-16 at 12:47 +0200, Sebastian Andrzej Siewior wrote:
> >> > But since I am on it. You have to enable runtime-PM for the UART. So
> >> > what is the
On 2018 Mai 17, Borislav Petkov wrote:
> On Thu, May 17, 2018 at 08:49:31AM +0200, Johannes Hirte wrote:
> > Maybe I'm missing something, but those RDMSR IPSs don't happen on
> > pre-SMCA systems, right? So the caching should be avoided here, cause
> > the whole lookup looks more expensive to me th
On Thu, 2018-05-17 at 21:23 +0200, Alexandre Belloni wrote:
> ocelot_qsys.h is missing the SPDX identfier, fix that.
>
> Signed-off-by: Alexandre Belloni
Only the copyright holders should ideally be modifying
these and also removing other license content.
For instance, what's the real intent he
On 05/17/2018 02:15 PM, Greg Kroah-Hartman wrote:
Shouldn't we just do this in one place, in the valid_port() function?
That way it keeps the range checking logic in one place (now it is in 3
places in the function), which should make maintenance much simpler.
Yep, I thought about that, the
On 05/17/2018 03:14 AM, Viresh Kumar wrote:
On 17-05-18, 15:00, Taniya Das wrote:
The CPUfreq FW present in some QCOM chipsets offloads the steps necessary
for hanging the frequency of CPUs. The driver implements the cpufreq driver
interface for this firmware.
Signed-off-by: Taniya Das
---
ocelot_qsys.h is missing the SPDX identfier, fix that.
Signed-off-by: Alexandre Belloni
---
drivers/net/ethernet/mscc/ocelot_qsys.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/mscc/ocelot_qsys.h
b/drivers/net/ethernet/mscc/ocelot_qsys.h
index aa7267d
This adds rave-sp powerbutton and backlight devices to RDU1 device tree.
Signed-off-by: Nikita Yushchenko
---
arch/arm/boot/dts/imx51-zii-rdu1.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/imx51-zii-rdu1.dts
b/arch/arm/boot/dts/imx51-zii-rdu1.dts
index 0c99ac
On 05/17/2018 03:14 AM, Viresh Kumar wrote:
+ Rob.
On 17-05-18, 15:00, Taniya Das wrote:
Add QCOM cpufreq firmware device bindings for Qualcomm Technology Inc's
SoCs. This is required for managing the cpu frequency transitions which are
controlled by firmware.
Signed-off-by: Taniya Das
---
On Thu, May 17, 2018 at 12:57:49PM -0500, Gustavo A. R. Silva wrote:
> Hi Greg,
>
> On 05/17/2018 01:51 AM, Greg Kroah-Hartman wrote:
> > On Wed, May 16, 2018 at 05:22:00PM -0500, Gustavo A. R. Silva wrote:
> > > pdev_nr and rhport can be controlled by user-space, hence leading to
> > > a potentia
Christoph Hellwig writes:
> On Thu, May 17, 2018 at 12:28:01AM -0500, Eric W. Biederman wrote:
>> > struct pid_namespace *proc_pid_namespace(struct inode *inode)
>> > {
>> >// maybe warn on for s_magic not on procfs??
>> >return inode->i_sb->s_fs_info;
>> > }
>>
>> That should work. Ide
On Thu, 17 May 2018, Joe Perches wrote:
> On Thu, 2018-05-17 at 20:27 +0200, Borislav Petkov wrote:
> > On Sun, May 13, 2018 at 12:27:45PM -0700, tip-bot for Joe Perches wrote:
> > > Commit-ID: 1de392f5d5e803663abbd8ed084233f154152bcd
> > > Gitweb:
> > > https://git.kernel.org/tip/1de392f5d5e
On Thu, May 17, 2018 at 12:10:22PM -0700, Saravana Kannan wrote:
> On 05/12/2018 10:19 PM, Joel Fernandes wrote:
> > On Tue, May 08, 2018 at 10:42:37AM +0100, Quentin Perret wrote:
> > > On Tuesday 08 May 2018 at 11:09:57 (+0200), Dietmar Eggemann wrote:
> > > > On 05/08/2018 10:22 AM, Viresh Kumar
On Thu, 17 May 2018, Alexander Kappner wrote:
> Oliver and Alan,
>
> thank for investigating.
>
> > this is suspicious. You do not actually whether US_FL_NO_WP_DETECT
> > by itself would make the device work. Can you please test that?
>
> US_FL_NO_WP_DETECT without US_FL_IGNORE_UAS does not mak
From: Ivan Khoronzhuk
Date: Thu, 17 May 2018 01:21:45 +0300
> The early versions of am33xx devices, related to ES1.0 SoC revision
> have errata limiting mq support. That's the same errata as
> commit 7da1160002f1 ("drivers: net: cpsw: add am335x errata workarround for
> interrutps")
>
> AM33xx E
On Thu, May 17, 2018 at 11:18:16PM +0530, Naresh Kamboju wrote:
> On 2 May 2018 at 20:38, David Miller wrote:
> > From: Grygorii Strashko
> > Date: Tue, 1 May 2018 12:41:22 -0500
>
> >> Signed-off-by: Grygorii Strashko
> >
> > Applied and queued up for -stable, thank you.
>
> 4.4 stable-rc bui
On Thu, May 17, 2018 at 11:45:57AM -0700, Joe Jin wrote:
> When run raidconfig from Dom0 we found that the Xen DMA heap is reduced,
> but Dom Heap is increased by the same size. Tracing raidconfig we found
> that the related ioctl() in megaraid_sas will call dma_alloc_coherent()
> to apply memory.
On 05/12/2018 10:19 PM, Joel Fernandes wrote:
On Tue, May 08, 2018 at 10:42:37AM +0100, Quentin Perret wrote:
On Tuesday 08 May 2018 at 11:09:57 (+0200), Dietmar Eggemann wrote:
On 05/08/2018 10:22 AM, Viresh Kumar wrote:
On 08-05-18, 08:33, Dietmar Eggemann wrote:
This reverts commit e2cabe4
Commit-ID: fed71f7d98795ed0fa1d431910787f0f4a68324f
Gitweb: https://git.kernel.org/tip/fed71f7d98795ed0fa1d431910787f0f4a68324f
Author: Thomas Gleixner
AuthorDate: Thu, 17 May 2018 14:36:39 +0200
Committer: Thomas Gleixner
CommitDate: Thu, 17 May 2018 21:00:12 +0200
x86/apic/x2apic: In
2018-05-17 18:23 GMT+02:00 Rob Herring :
> On Wed, May 16, 2018 at 12:51 PM, William Breathitt Gray
> wrote:
>> From: Benjamin Gaignard
>
> v6? Where's v1-v5?
>
>> Add bindings for STM32 Timer quadrature encoder.
>> It is a sub-node of STM32 Timer which implement the
>> counter part of the hardwa
Hi John,
On 05/17/2018 12:27 PM, John Fastabend wrote:
On 05/17/2018 07:08 AM, Gustavo A. R. Silva wrote:
There is a potential execution path in which variable err is
returned without being properly initialized previously.
Fix this by initializing variable err to 0.
Addresses-Coverity-ID: 146
On Thu, 2018-05-17 at 11:26 -0700, Matthew Wilcox wrote:
> On Thu, May 17, 2018 at 01:43:36PM -0400, Jeff Layton wrote:
> > @@ -107,12 +109,10 @@ static void fdatawait_one_bdev(struct block_device
> > *bdev, void *arg)
> > */
> > void ksys_sync(void)
> > {
> > - int nowait = 0, wait = 1;
> >
From: Matt Mullins
Date: Wed, 16 May 2018 10:48:40 -0700
> scatterlist code expects virt_to_page() to work, which fails with
> CONFIG_VMAP_STACK=y.
>
> Fixes: c46234ebb4d1e ("tls: RX path for ktls")
> Signed-off-by: Matt Mullins
Applied and queued up for -stable, thanks.
I'm surprised this pr
> Kernel threads have empty /proc/PID/cmdline and some userland tools
> including ps(1) and older versions of systemd use this to detect
> kernel threads.
Those tools are broken. Systemd is fixed, see
https://github.com/systemd/systemd/blob/master/src/basic/process-util.c#L442
Empty /proc/*/cmdli
On Thu, May 17, 2018 at 05:54:24PM +0300, Michael S. Tsirkin wrote:
> HINTS_DEDICATED seems to be somewhat confusing:
>
> Guest doesn't really care whether it's the only task running on a host
> CPU as long as it's not preempted.
>
> And there are more reasons for Guest to be preempted than host
When run raidconfig from Dom0 we found that the Xen DMA heap is reduced,
but Dom Heap is increased by the same size. Tracing raidconfig we found
that the related ioctl() in megaraid_sas will call dma_alloc_coherent()
to apply memory. If the memory allocated by Dom0 is not in the DMA area,
it will e
On Thu, 2018-05-17 at 20:27 +0200, Borislav Petkov wrote:
> On Sun, May 13, 2018 at 12:27:45PM -0700, tip-bot for Joe Perches wrote:
> > Commit-ID: 1de392f5d5e803663abbd8ed084233f154152bcd
> > Gitweb:
> > https://git.kernel.org/tip/1de392f5d5e803663abbd8ed084233f154152bcd
> > Author: Joe
Hi Qing,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on net-next/master]
[also build test ERROR on v4.17-rc5 next-20180517]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Oliver and Alan,
thank for investigating.
> this is suspicious. You do not actually whether US_FL_NO_WP_DETECT
> by itself would make the device work. Can you please test that?
US_FL_NO_WP_DETECT without US_FL_IGNORE_UAS does not make a difference,
even with the patch you included applied:
[
On 2018-05-17 04:32, Ramon Fried wrote:
From: Eyal Ilsar
...
+int wcn36xx_smd_process_ptt_msg(struct wcn36xx *wcn,
+ struct ieee80211_vif *vif, void *ptt_msg,
size_t len,
+ void **ptt_rsp_msg)
+{
+ struct wcn36xx_hal_process_ptt_msg_req_msg *p
On 2018-05-17 04:32, Ramon Fried wrote:
From: Eyal Ilsar
...
+static int wcn36xx_smd_process_ptt_msg_rsp(void *buf, size_t len,
+ void **p_ptt_rsp_msg)
+{
+ struct wcn36xx_hal_process_ptt_msg_rsp_msg *rsp;
+ int ret = 0;
why initialize 're
On 05/17/2018 12:06 AM, Stephen Rothwell wrote:
> Hi all,
>
on x86_64:
drivers/pwm/pwm-stm32.o: In function `stm32_pwm_raw_capture':
pwm-stm32.c:(.text+0x53d): undefined reference to `stm32_timers_dma_burst_read'
when COMPILE_TEST=y and MFD_STM32_TIMERS is not set.
Any suggestions?
thanks,
-
From: Borislav Petkov
We used rdmsr_safe_on_cpu() to make sure we're reading the proper CPU's
MISC block addresses. However, that caused trouble with CPU hotplug due
to the _on_cpu() helper issuing an IPI while IRQs are disabled.
But we don't have to do that: the block addresses are the same on
From: Borislav Petkov
... into a global, two-dimensional array and service subsequent reads
from that cache to avoid rdmsr_on_cpu() calls during CPU hotplug (IPIs
with IRQs disabled).
In addition, this fixes a KASAN slab-out-of-bounds read due to wrong
usage of the bank->blocks pointer.
Reporte
On Thu, May 17, 2018 at 06:56:37PM +0200, Rafael J. Wysocki wrote:
> On Thu, May 17, 2018 at 6:42 PM, Srinivas Pandruvada
> > What will happen if we look at all core turbo as max and cap any
> > utilization above this to 1024?
>
> I was going to suggest that.
To the basic premise behind all our
On Sun, May 13, 2018 at 12:27:45PM -0700, tip-bot for Joe Perches wrote:
> Commit-ID: 1de392f5d5e803663abbd8ed084233f154152bcd
> Gitweb:
> https://git.kernel.org/tip/1de392f5d5e803663abbd8ed084233f154152bcd
> Author: Joe Perches
> AuthorDate: Thu, 10 May 2018 08:45:30 -0700
> Committer:
On Thu, 17 May 2018, Peter Zijlstra wrote:
> On Thu, May 17, 2018 at 06:55:26PM +0200, Stefan Wahren wrote:
> > > Vince Weaver hat am 17. Mai 2018 um 18:34
> > > geschrieben:
> > > On Thu, 17 May 2018, Stefan Wahren wrote:
> > > > > Eric Anholt hat am 17. Mai 2018 um 15:17
> > > > > geschriebe
On Thu, May 17, 2018 at 01:43:36PM -0400, Jeff Layton wrote:
> @@ -107,12 +109,10 @@ static void fdatawait_one_bdev(struct block_device
> *bdev, void *arg)
> */
> void ksys_sync(void)
> {
> - int nowait = 0, wait = 1;
> -
> wakeup_flusher_threads(WB_REASON_SYNC);
> iterate_supe
On Wed, May 16, 2018 at 6:21 PM Tejun Heo wrote:
> This patch fixes the issue by making proc_pid_cmdline_read() never
> return empty string for user tasks.
Ugh.
That function really is too damn ugly, and this just makes it worse.
Can we please split things up a bit before uglifying the code fu
On Thu, May 17, 2018 at 02:40:06PM +0200, Sebastian Andrzej Siewior wrote:
> In v4.16-RT I noticed a number of warnings from task_fpsimd_load(). The
> code disables BH and expects that it is not preemptible. On -RT the
> task remains preemptible but remains the same CPU. This may corrupt the
Also,
On Thu, May 17, 2018 at 01:36:19PM -0400, Sinan Kaya wrote:
> Try to keep the pool closer to the device's NUMA node by changing kmalloc()
> to kmalloc_node() and devres_alloc() to devres_alloc_node().
Have you measured any performance gains by doing this? The thing is that
these allocations are f
Em Thu, May 17, 2018 at 10:52:30AM -0700, Dave Hansen escreveu:
> On 05/17/2018 02:21 AM, Adrian Hunter wrote:
> > From: Alexander Shishkin
> >
> > Signed-off-by: Alexander Shishkin
>
> For the benefit of the poor souls looking at this code in the decades to
> come, could you please take a few
On 05/17/2018 07:13 AM, Mauro Carvalho Chehab wrote:
Em Thu, 17 May 2018 08:43:24 -0300
Mauro Carvalho Chehab escreveu:
On 05/15/2018 02:39 PM, Dan Carpenter wrote:
You'd need to rebuild the db (possibly twice but definitely once).
How? Here, I just pull from your git tree and do a "m
On Thu, May 17, 2018 at 06:55:26PM +0200, Stefan Wahren wrote:
> > Vince Weaver hat am 17. Mai 2018 um 18:34
> > geschrieben:
> > On Thu, 17 May 2018, Stefan Wahren wrote:
> > > > Eric Anholt hat am 17. Mai 2018 um 15:17 geschrieben:
> > > > The a53 and a7 counters seem to match up, so we adver
Hi Baoquan,
On 17/05/18 03:15, Baoquan He wrote:
> On 05/17/18 at 10:10am, Baoquan He wrote:
>> On 05/07/18 at 02:59pm, AKASHI Takahiro wrote:
>>> On Tue, May 01, 2018 at 06:46:09PM +0100, James Morse wrote:
On 25/04/18 07:26, AKASHI Takahiro wrote:
> We need to prevent firmware-reserved
On Thu, May 17, 2018 at 11:23:22AM -0500, Rob Herring wrote:
>On Wed, May 16, 2018 at 12:51 PM, William Breathitt Gray
> wrote:
>> From: Benjamin Gaignard
>
>v6? Where's v1-v5?
Hi Rob,
I apologize, I should have CC you on the rest of the patchset to give
you a better idea of the context of this
We report the crash:
"KASAN: use-after-free Read in vgacon_invert_region"
This crash was found in v4.17-rc3. Specifically, memory access (read
operation) is invalid, and it is detected by KASAN.
C repro code:
https://kiwi.cs.purdue.edu/static/alexkkid-fuzzer/repro-ba6c1.c
kernel config:
https:/
Change module description to be in line with the other Tegra drivers, just
for consistency.
Signed-off-by: Dmitry Osipenko
---
drivers/cpufreq/tegra20-cpufreq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/tegra20-cpufreq.c
b/drivers/cpufreq/tegra20-cpufre
Hello,
Recently Peter Geis (who is working on Tegra30 cpufreq driver) asked me how
tegra20-cpufreq driver is getting loaded. After taking a look at the code
it became apparent that the drivers code has been rusted a tad and so this
series is intended to refresh the drivers code by disallowing modu
Properly put requested clocks in the module init/exit code.
Signed-off-by: Dmitry Osipenko
---
drivers/cpufreq/tegra20-cpufreq.c | 31 ++-
1 file changed, 26 insertions(+), 5 deletions(-)
diff --git a/drivers/cpufreq/tegra20-cpufreq.c
b/drivers/cpufreq/tegra20-cpufr
Remove unused/unneeded headers and sort them in the alphabet order.
Signed-off-by: Dmitry Osipenko
---
drivers/cpufreq/tegra20-cpufreq.c | 11 ++-
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git a/drivers/cpufreq/tegra20-cpufreq.c
b/drivers/cpufreq/tegra20-cpufreq.c
index 69
The EMC driver has been gone 4 years ago, since the commit a7cbe92cef27
("ARM: tegra: remove tegra EMC scaling driver"). Remove the EMC clock
usage as it does nothing. We may consider re-implementing the EMC scaling
later, probably using PM Memory Bandwidth QoS API.
Signed-off-by: Dmitry Osipenko
g for x86_64, a
> multi_v7_defconfig for arm and a native build of tools/perf. After
> the final fixups (if any), I do an x86_64 modules_install followed by
> builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
> ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i
On Thu, May 17, 2018 at 11:15:59AM +, Bharat Kumar Gogada wrote:
> > > Hi,
> > >
> > > As per NVME specification:
> > > 7.5.1.1 Host Software Interrupt Handling It is recommended that host
> > > software utilize the Interrupt Mask Set and Interrupt Mask Clear
> > > (INTMS/INTMC) registers to ef
Don't even try to request the clocks during of module initialization on
non-Tegra20 machines (this is the case for a multi-platform kernel) for
consistency.
Signed-off-by: Dmitry Osipenko
---
drivers/cpufreq/tegra20-cpufreq.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/cpufre
Remove checking of the CPU number for consistency as it won't ever fail
unless there is a severe bug in the cpufreq core.
Signed-off-by: Dmitry Osipenko
---
drivers/cpufreq/tegra20-cpufreq.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/cpufreq/tegra20-cpufreq.c
b/drivers/cpuf
Remove unneeded variable initialization solely for consistency.
Signed-off-by: Dmitry Osipenko
---
drivers/cpufreq/tegra20-cpufreq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/tegra20-cpufreq.c
b/drivers/cpufreq/tegra20-cpufreq.c
index 797c61c74b65..c0a7
Tegra20-cpufreq driver require a platform device in order to be loaded,
instantiate a simple platform device for the driver during of the machines
late initialization.
Signed-off-by: Dmitry Osipenko
---
arch/arm/mach-tegra/tegra.c | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/
Currently tegra20-cpufreq kernel module isn't getting autoloaded because
there is no device associated with the module, this is one of two patches
that resolves the module autoloading. This patch adds a module alias that
will associate the tegra20-cpufreq kernel module with the platform device,
oth
Nothing prevents Tegra20 CPUFreq module to be unloaded, hence allow it to
be built as a non-builtin kernel module.
Signed-off-by: Dmitry Osipenko
---
drivers/cpufreq/Kconfig.arm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kcon
Remove unneeded blank line and replace whitespaces with a tab in the code
for consistency.
Signed-off-by: Dmitry Osipenko
---
drivers/cpufreq/tegra20-cpufreq.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/cpufreq/tegra20-cpufreq.c
b/drivers/cpufreq/tegra20-cpufr
Hi Changbin,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.17-rc5 next-20180517]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day
Hi Greg,
On 05/17/2018 01:51 AM, Greg Kroah-Hartman wrote:
On Wed, May 16, 2018 at 05:22:00PM -0500, Gustavo A. R. Silva wrote:
pdev_nr and rhport can be controlled by user-space, hence leading to
a potential exploitation of the Spectre variant 1 vulnerability.
This issue was detected with the
Hello,
syzbot found the following crash on:
HEAD commit:e6506eb24187 Merge tag 'trace-v4.17-rc4-2' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=177fe47780
kernel config: https://syzkaller.appspot.com/x/.config?x=f3b4e30da84ec1ed
da
On 05/17/2018 01:35 AM, Huang, Ying wrote:
> From: Huang Ying
>
> This is to take better advantage of general huge page clearing
> optimization (c79b57e462b5d, "mm: hugetlb: clear target sub-page last
> when clearing huge page") for hugetlbfs. In the general optimization
> patch, the sub-page to
On 05/17/2018 02:21 AM, Adrian Hunter wrote:
> @@ -149,9 +149,9 @@ static void __init setup_cpu_entry_area(int cpu)
>
> cea_set_pte(&get_cpu_entry_area(cpu)->entry_trampoline,
>__pa_symbol(_entry_trampoline), PAGE_KERNEL_RX);
> - kclist_add(&per_cpu(kcore_entry_tramp
On 17/05/18 18:23, Mark Brown wrote:
On Thu, May 17, 2018 at 06:10:49PM +0100, Srinivas Kandagatla wrote:
On 17/05/18 07:55, Mark Brown wrote:
On Wed, May 09, 2018 at 01:56:20PM +0100, Srinivas Kandagatla wrote:
This lock only protects the list, it does nothing to ensure that the
port we l
On 05/17/2018 10:08 AM, Michal Hocko wrote:
On Thu 17-05-18 18:49:47, Michal Hocko wrote:
On Thu 17-05-18 16:58:32, Ville Syrjälä wrote:
On Thu, May 17, 2018 at 04:36:29PM +0300, Ville Syrjälä wrote:
On Thu, May 17, 2018 at 03:21:09PM +0200, Michal Hocko wrote:
On Thu 17-05-18 15:59:59, Ville
On 05/17/2018 02:21 AM, Adrian Hunter wrote:
> From: Alexander Shishkin
>
> Signed-off-by: Alexander Shishkin
For the benefit of the poor souls looking at this code in the decades to
come, could you please take a few minutes to write a couple of sentences
about why this is being done?
> diff -
On 2 May 2018 at 20:38, David Miller wrote:
> From: Grygorii Strashko
> Date: Tue, 1 May 2018 12:41:22 -0500
>> Signed-off-by: Grygorii Strashko
>
> Applied and queued up for -stable, thank you.
4.4 stable-rc build failed for arm32.
MACHINE=am57xx-evm
Build error log:
dri
On Wed, May 16, 2018 at 09:21:59AM +0800, Xiaowei Song wrote:
> From: Yao Chen
>
> Add support for MSI.
>
> Signed-off-by: Yao Chen
> Cc: Xiaowei Song
> ---
> drivers/pci/dwc/pcie-kirin.c | 51
>
> 1 file changed, 51 insertions(+)
>
> diff --git
On 05/17/2018 11:02 AM, Jan Beulich wrote:
On 17.05.18 at 16:47, wrote:
>> @@ -64,6 +67,9 @@ ENTRY(pvh_start_xen)
>> mov %eax,%es
>> mov %eax,%ss
>>
>> +mov $PVH_CANARY_SEL,%eax
>> +mov %eax,%gs
> I doubt this is needed for 64-bit (you could equally well load zero or leave
From: Jeff Layton
All of the callback functions for iterate_supers either ignore the
opaque argument, or dereference the pointer only to fetch the int
to which it points.
Change quota_sync_one to just cast the int from the pointer,
and change sync_fs_one_sb to just use a NULL/non-NULL pointer as
On Sat, May 12, 2018 at 02:35:23PM +1000, Stephen Rothwell wrote:
>Hi all,
>
>As an outcome of some discussion, I have added a pending-fixes branch
>to linux-next. This branch contains Linus' tree merged with branches
>containing only fixes pending for the current release. The branch is a
>strict
From: Brian Starkey
Writeback connectors represent writeback engines which can write the
CRTC output to a memory framebuffer. Add a writeback connector type and
related support functions.
Drivers should initialize a writeback connector with
drm_writeback_connector_init() which takes care of sett
From: Brian Starkey
Add the WRITEBACK_OUT_FENCE_PTR property to writeback connectors, to
enable userspace to get a fence which will signal once the writeback is
complete. It is not allowed to request an out-fence without a
framebuffer attached to the connector.
A timeline is added to drm_writeba
Hi,
This is v7 of the writeback connector series. This is just a refresh
of the v6 series in order to get it ready for merging into the kernel,
now that the userspace implementation has been reviewed and ACKed
by Sean Paul here [1].
For anyone that wants a refresh on what changed in v6, the serie
301 - 400 of 1043 matches
Mail list logo
