kmemcheck used to do it's own basic instruction decoding, which is
just a duplication of the work done in arch/x86/lib/insn.c.
Instead, switch it to using the already existing dissasembler, and
switch the magic opcode numbers into something meaningful.
Signed-off-by: Sasha Levin
---
Enable reset driver support in order to have opportunity
to reboot SoC by watchdog and by software.
Signed-off-by: Ivan Khoronzhuk
---
arch/arm/configs/keystone_defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/configs/keystone_defconfig
Remove reset stuff in flavour of using keystone reset driver:
driver/power/reset/keystone-reset.c
Signed-off-by: Ivan Khoronzhuk
---
arch/arm/mach-keystone/keystone.c | 35 ---
1 file changed, 35 deletions(-)
diff --git a/arch/arm/mach-keystone/keystone.c
These patches introduce keystone reset driver.
The keystone SoC can be rebooted in several ways. By external reset
pin, by soft and by watchdogs. This driver allows software reset or reset
by one of the watchdogs. Also added opportunity to set soft/hard reset type.
Based on v3.15-rc1
v1..v2
The keystone SoC can be rebooted in several ways. By external reset
pin, by soft and by watchdogs. To allow keystone SoC reset if
watchdog is triggered we have to enable it in reset mux configuration
register regarding of watchdog configuration. Also we need to set
soft/hard reset we are going to
The reset controller registers are part of the PLL Controller MMRs.
According to TRM there are the following registers:
RSTYPE, RSCTRL, RSCFG and RSISO. Currently declared only one of them,
but that is not enough to correctly setup reset properties, so add
whole range of pll registers - pllregs.
From: Randy Dunlap
Fix new s390 kernel-doc warning:
Warning(arch/s390/include/asm/ccwgroup.h:27): No description found for
parameter 'ungroup_work'
Signed-off-by: Randy Dunlap
Cc: Sebastian Ott
Cc: Peter Oberparleiter
Cc: linux-s...@vger.kernel.org
Cc: Martin Schwidefsky
On Mon 14-04-14 10:56:58, Thavatchai Makphaibulchoke wrote:
> On 04/02/2014 11:41 AM, Jan Kara wrote:
> > Thanks for the patches and measurements! So I agree we contend a lot on
> > orphan list changes in ext4. But what you do seems to be unnecessarily
> > complicated and somewhat hiding the
TCP_FASTOPEN option can be set via setsockopt(), but the value cannot be
gotten via getsockopt(). This patch adds the option to getsockopt().
Sighned-off-by: Kenjiro Nakayama
Add option to get TCP_FASTOPEN to getsockopt()
---
net/ipv4/tcp.c | 5 +
1 file changed, 5 insertions(+)
On Mon, 2014-04-14 at 13:34 -0400, David Miller wrote:
> From: Eric Dumazet
> Date: Mon, 14 Apr 2014 10:12:29 -0700
>
> > Hmm, it seems commit 31c70d5956fc l2tp: keep original skb ownership
> > is the problem.
> >
> > ip_queue_xmit() assumes the socket attached to skb is an inet socket.
>
>
From: Geert Uytterhoeven
The availability of SPI Dual or Quad Transfer Mode as indicated by the
"spi-tx-bus-width" and "spi-rx-bus-width" properties in the device tree is
a hardware property of the SPI master, SPI slave, and board wiring. Hence
the SPI core should not reject an SPI slave
On Mon, Apr 14, 2014 at 06:28:37PM +0200, Bartlomiej Zolnierkiewicz wrote:
> As a nice side effect this fixes the cf_port leak on
> dma_coerce_mask_and_coherent() or ata_host_activate()
> failure.
>
> Cc: Ralf Baechle
> Cc: David Daney
> Suggested-by: Guenter Roeck
> Signed-off-by: Bartlomiej
On Mon, Apr 14, 2014 at 10:26 AM, Kees Cook wrote:
> On Mon, Apr 14, 2014 at 10:17 AM, Alexei Starovoitov
> wrote:
>> On Mon, Apr 14, 2014 at 10:11 AM, Kees Cook wrote:
>>> This sets the correct error code when final filter memory is unavailable,
>>> and frees the raw filter no matter what.
On Sun, Apr 13, 2014 at 08:12:57PM +0530, RAGHAVENDRA GANIGA wrote:
> +static const struct spi_device_id ds1343_id[] = {
> + { "ds1343", 0 },
> + { "ds1344", 1 },
> + { }
> +};
> +MODULE_DEVICE_TABLE(spi, ds1343_id);
If the 0 and 1 mean anything there they should have #defines,
From: Eric Dumazet
Date: Mon, 14 Apr 2014 10:12:29 -0700
> Hmm, it seems commit 31c70d5956fc l2tp: keep original skb ownership
> is the problem.
>
> ip_queue_xmit() assumes the socket attached to skb is an inet socket.
This is similar to the "send over AF_PACKET" issue we were discussing
the
On Mon, Apr 14, 2014 at 12:27:47PM -0400, Pranith Kumar wrote:
> On Mon, Apr 14, 2014 at 12:19 PM, Pranith Kumar wrote:
> > Hi Paul,
> >
> > On Mon, Apr 14, 2014 at 12:07 PM, Paul E. McKenney
> > wrote:
> >> On Sun, Apr 13, 2014 at 05:53:53PM -0400, Pranith Kumar wrote:
> >>> remove duplicate
On Mon, Apr 14, 2014 at 01:41:34PM +0100, Liu hua wrote:
> 于 2014/4/14 19:37, Will Deacon 写道:
> > On Thu, Mar 27, 2014 at 08:00:39AM +, Liu Hua wrote:
> >> For vmcore generated by LPAE enabled kernel, user space
> >> utility such as crash needs additional infomation to
> >> parse.
> >>
> >> So
From: "Li, Zhen-Hua"
Date: Mon, 14 Apr 2014 18:08:36 +0800
> For the cosa module, CONFIG_COSA can only be checked as 'm',
> and cosa module can only be compiled as a module.
That's not true, it's "tristate" in drivers/net/wan/Kconfig so it
could be set to 'y' too.
But there is another reason
On Mon, Apr 14, 2014 at 10:17 AM, Alexei Starovoitov wrote:
> On Mon, Apr 14, 2014 at 10:11 AM, Kees Cook wrote:
>> This sets the correct error code when final filter memory is unavailable,
>> and frees the raw filter no matter what.
>>
>> unreferenced object 0x8800d6ea4000 (size 512):
>>
On 14/04/14 17:51, David Miller wrote:
> From: David Vrabel
> Date: Mon, 14 Apr 2014 10:42:20 +0100
>
>> On 12/04/14 21:51, David Miller wrote:
>>> From: Vincenzo Maffione
>>> Date: Sat, 12 Apr 2014 11:55:40 +0200
>>>
This patch fixes the initialization of an array used in the TX
Hello,
I recently found out the hard way, that using mempool_alloc together with
__GFP_ZERO is not a good idea since memory which comes from the pool of
preallocated elemtents is not zeroed. Fixing this doesn't seem to be trivial
since mempool is not aware of the size of the objects it manages.
On Mon, Apr 14, 2014 at 8:49 AM, Andy Lutomirski wrote:
> [Resent because I forgot to email lkml. This also surreptitiously
> fixes a silly typo on a patch description.]
>
> This is my attempt to come up with a workable way to use so-called
> entropy sources like a TPM to feed /dev/urandom.
>
>
On 4/14/14, 9:52 AM, Jiri Olsa wrote:
From: Arnaldo Carvalho de Melo
We will share it among threads in the same process.
Signed-off-by: Arnaldo Carvalho de Melo
Cc: Adrian Hunter
Cc: David Ahern
Cc: Don Zickus
Cc: Frederic Weisbecker
Cc: Mike Galbraith
Cc: Namhyung Kim
Cc: Paul
On Mon, Apr 14, 2014 at 10:11 AM, Kees Cook wrote:
> This sets the correct error code when final filter memory is unavailable,
> and frees the raw filter no matter what.
>
> unreferenced object 0x8800d6ea4000 (size 512):
> comm "sshd", pid 278, jiffies 4294898315 (age 46.653s)
> hex dump
On Mon, Apr 14, 2014 at 09:53:27AM -0700, Joe Perches wrote:
> On Mon, 2014-04-14 at 09:32 -0700, Paul E. McKenney wrote:
> > On Mon, Apr 14, 2014 at 12:19:31PM -0400, Pranith Kumar wrote:
> > > Hi Paul,
> > >
> > > On Mon, Apr 14, 2014 at 12:07 PM, Paul E. McKenney
> > > wrote:
> > > > On Sun,
>From 5cd11ca62acfcde2757fbcc9bbb55e9449d2d50b Mon Sep 17 00:00:00 2001
From: Konstantin Tokarev
Date: Mon, 14 Apr 2014 20:38:00 +0400
Subject: [PATCH] sh: Implemented syscall_{get|set}_arguments for i != 0.
syscall_get_arguments and syscall_set_arguments implementations for SH
will not call
n Mon, 14 Apr 2014, Grygorii Strashko wrote:
> Hi All,
>
> I'm observing a huge number of warnings produced during the boot of my
> Keystone 2 board
> when USB is enabled.
>
> [2.496460] BUG: using __this_cpu_read() in preemptible [] code:
> khubd/202
> [2.504030] caller is
On Tue, 2014-04-15 at 01:01 +0800, Zhan Jianyu wrote:
> On Mon, Apr 14, 2014 at 11:19 PM, James Chapman wrote:
> > Please send the complete oops message.
>
> Hi, complete oops message is :
>
>
> [ 100.243737] BUG: unable to handle kernel NULL pointer dereference
> at 02c0
> [
This sets the correct error code when final filter memory is unavailable,
and frees the raw filter no matter what.
unreferenced object 0x8800d6ea4000 (size 512):
comm "sshd", pid 278, jiffies 4294898315 (age 46.653s)
hex dump (first 32 bytes):
21 00 00 00 04 00 00 00 15 00 01 00 3e 00
> -Original Message-
> From: H. Peter Anvin [mailto:h...@zytor.com]
> Sent: Monday, April 14, 2014 10:08 AM
> To: KY Srinivasan; x...@kernel.org; gre...@linuxfoundation.org; linux-
> ker...@vger.kernel.org; de...@linuxdriverproject.org; o...@aepfle.de;
> a...@canonical.com;
> fput could go into print_stat_spark
I wanted to keep the function generic, so that it can be easily
used in other places. Adding the space is somewhat specific
to stat.
Also the rest of the stat code has the white space printing
centralized in the caller too. I suppose makes it easier to
On 04/14/2014 10:46 AM, K. Y. Srinivasan wrote:
> + new_val = inb(PIC_MASTER_IMR);
> + if (probe_val != new_val) {
Nitpick: Linux coding style should have this as:
if (new_val != probe_val)
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Mon, Apr 14, 2014 at 9:18 AM, Alexei Starovoitov wrote:
> On Mon, Apr 14, 2014 at 9:02 AM, Masami Ichikawa wrote:
>> kmemleak reported some memory leak as below.
>
> grrr. yes. sorry.
>
>> unreferenced object 0x8800d6ea4000 (size 512):
>> comm "sshd", pid 278, jiffies 4294898315 (age
Hi Alan,
the patch fix the issue. I tested it on a notebook with a cardbus
controller and on desktop machine with a thunderbolt interface. Both are
working.
Thunderbolt will sometimes crash but i think this is a issue with
dynamic added pci bridges, which cause a lot of trouble and headache to
On Mon, 2014-04-14 at 09:47 -0700, Davidlohr Bueso wrote:
> On Mon, 2014-04-14 at 09:44 -0700, Davidlohr Bueso wrote:
> > On Tue, 2014-04-15 at 00:19 +0800, Jiang Liu wrote:
> > > Hi Davidlohr,
> > > Thanks for providing the DMAR table. According to the DMAR
> > > table, one bug in the iommu
> -Original Message-
> From: H. Peter Anvin [mailto:h...@zytor.com]
> Sent: Monday, April 14, 2014 10:02 AM
> To: KY Srinivasan; x...@kernel.org; gre...@linuxfoundation.org; linux-
> ker...@vger.kernel.org; de...@linuxdriverproject.org; o...@aepfle.de;
> a...@canonical.com;
tick_check_new_device() is calling tick_check_percpu() which has this as the
first test:
if (!cpumask_test_cpu(cpu, newdev->cpumask))
return false;
And so the same isn't required to be repeated by tick_check_new_device(). Remove
it.
This also initializes several
From: Geert Uytterhoeven
There's no need for this to be synchronous
Signed-off-by: Geert Uytterhoeven
---
drivers/thermal/rcar_thermal.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/thermal/rcar_thermal.c b/drivers/thermal/rcar_thermal.c
index
On Mon, Apr 14, 2014 at 11:19 PM, James Chapman wrote:
> Please send the complete oops message.
Hi, complete oops message is :
[ 100.243737] BUG: unable to handle kernel NULL pointer dereference
at 02c0
[ 100.244985] IP: [] ip_queue_xmit+0x20/0x3e0
[ 100.262266] PGD 0
[
On 04/14/2014 10:46 AM, K. Y. Srinivasan wrote:
> This patch implements the proposal put forth by H. Peter Anvin
> .
>
> In version V1 of the patch, I had cleaned up the code based on comments from
> Peter.
> In version V2 of the patch, I have addressed additional comments from Peter.
> In
On 04/02/2014 11:41 AM, Jan Kara wrote:
> Thanks for the patches and measurements! So I agree we contend a lot on
> orphan list changes in ext4. But what you do seems to be unnecessarily
> complicated and somewhat hiding the real substance of the patch. If I
> understand your patch correctly,
This does some trivial fixups:
- breaking lines longer than 80 columns
- merging few lines together
- don't break print messages even if they cross 80 columns
- remove few whitespaces
- remove few extra blank lines
Signed-off-by: Viresh Kumar
---
include/linux/tick.h | 3 ++-
Rearrange members of 'struct tick_sched' to make it more readable. i.e. By
keeping all ktime_t members together, similarly 'unsigned long' and 'int' as
well. I couldn't figure out breaking any logical blocks here which we wanted to
keep together.
This is the change in footprints after this
From: Geert Uytterhoeven
Signed-off-by: Geert Uytterhoeven
---
lib/Kconfig.debug |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 140b66a874c1..3da1ba468305 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -576,8
This is tick-oneshot specific routine and hence must be there in this file. Also
it isn't used outside of kernel/time/ and so moving its declaration to
tick-internal.h.
Signed-off-by: Viresh Kumar
---
include/linux/tick.h| 1 -
kernel/time/tick-common.c | 14 --
tick_resume_oneshot() and tick_setup_oneshot() have almost the same
implementation and tick_setup_oneshot() can be used easily instead of
tick_resume_oneshot(). So, remove tick_resume_oneshot() and use
tick_setup_oneshot() in its place.
Signed-off-by: Viresh Kumar
---
kernel/time/tick-common.c
On Mon, Apr 14, 2014 at 09:09:14AM -0700, H. Peter Anvin wrote:
> I think the default should be zero, so each hwrng driver maintainer would
> have to consider what guarantees that particular driver can give. If
> anything 50% ought to be the maximum.
Repost of v4 just for patch 03/03 is on its
tick_switch_to_oneshot() is just reading value of
__this_cpu_read(tick_cpu_device.mode) and doesn't need to disable local
interrupts for that. Drop local_irq_save/restore calls from this routine.
Signed-off-by: Viresh Kumar
---
kernel/time/tick-oneshot.c | 9 +
1 file changed, 1
tick_check_replacement() returns if a replacement of clock_event_device is
possible or not. It does this as the first check:
if (tick_check_percpu(curdev, newdev, smp_processor_id()))
return false;
This looks wrong as we are returning false when tick_check_percpu() cpu
From: Geert Uytterhoeven
Signed-off-by: Geert Uytterhoeven
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
---
drivers/misc/Kconfig |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index 1cb74085e410..8baff0effc7d 100644
---
If 'curdev' passed to tick_check_preferred() is the current clock_event_device
then these two checks look exactly same, because td->mode = TICKDEV_MODE_ONESHOT
is only called when the event device had ONESHOT feature.
if (curdev && (curdev->features & CLOCK_EVT_FEAT_ONESHOT))
tick_check_replacement() is now nothing more than a wrapper over
tick_check_preferred() and hence can be removed. Use tick_check_preferred()
everywhere.
Signed-off-by: Viresh Kumar
---
kernel/time/clockevents.c | 2 +-
kernel/time/tick-common.c | 16 +---
While OMAP4 and OMAP5 had 3 separate clock domains, DRA7 has only 2
and the first one then is internally divided into 2 sub clock domains.
To better represent this in the driver, we use the concept of submodule.
The address defintions in the devicetree is as per the high level
clock
On Mon, 2014-04-14 at 09:32 -0700, Paul E. McKenney wrote:
> On Mon, Apr 14, 2014 at 12:19:31PM -0400, Pranith Kumar wrote:
> > Hi Paul,
> >
> > On Mon, Apr 14, 2014 at 12:07 PM, Paul E. McKenney
> > wrote:
> > > On Sun, Apr 13, 2014 at 05:53:53PM -0400, Pranith Kumar wrote:
> > >> remove
We return false from tick_check_preferred() if newdev doesn't have ONESHOT
feature but curdev has, but we don't return true when newdev has ONESHOT and
curdev doesn't. Instead we go on, check ratings and other things in that case.
This patch tries to fix this by rewriting some portion of this
From: Sricharan R
Since omap_l3_noc driver is now being used for OMAP5 and reusable with
DRA7 and AM437x, using omap4 specific naming is misleading.
Signed-off-by: Sricharan R
Signed-off-by: Nishanth Menon
---
drivers/bus/omap_l3_noc.c | 24
This patch implements the proposal put forth by H. Peter Anvin
.
In version V1 of the patch, I had cleaned up the code based on comments from
Peter.
In version V2 of the patch, I have addressed additional comments from Peter.
In this version of the patch, I have addressed Jan's comments
From: David Vrabel
Date: Mon, 14 Apr 2014 10:42:20 +0100
> On 12/04/14 21:51, David Miller wrote:
>> From: Vincenzo Maffione
>> Date: Sat, 12 Apr 2014 11:55:40 +0200
>>
>>> This patch fixes the initialization of an array used in the TX
>>> datapath that was mistakenly initialized together with
This is an embarrassing patch :(.
Texas Corporation does not make OMAP. Texas Instruments Inc does.
For that matter I dont seem to be able to find a Texas Corporation on
the internet either.
While at it, update coverage to the current year and update the template
to remove redundant information
The variable use_gptimer_clksrc is only used by two __init functions,
So we can freely free it after boot.
Signed-off-by: Oussama Ghorbel
---
arch/arm/mach-omap2/timer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/timer.c b/arch/arm/mach-omap2/timer.c
From: Geert Uytterhoeven
The English and Korean translations were updated, the Chinese and Japanese
weren't.
Signed-off-by: Geert Uytterhoeven
---
Documentation/ja_JP/HOWTO |2 +-
Documentation/ja_JP/stable_kernel_rules.txt |6 +++---
Documentation/zh_CN/HOWTO
Currently we use __raw_readl and writel in this driver, however, there
is no strict sequencing needs for this driver, hence we should be good
with the relaxed variants.
While at it, simplify address computation using variables for register.
Signed-off-by: Nishanth Menon
---
just simplify derefencing that is equivalent.
Signed-off-by: Nishanth Menon
---
drivers/bus/omap_l3_noc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/bus/omap_l3_noc.c b/drivers/bus/omap_l3_noc.c
index 0d346e6..b39ef93 100644
--- a/drivers/bus/omap_l3_noc.c
l3->dev is not populated, so populate it and use it to print information
relevant to the device instead of using a generic pr_*.
Signed-off-by: Nishanth Menon
---
drivers/bus/omap_l3_noc.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git
we do not use iclk directly anymore. And, even if we had to, we
should be using pm_runtime APIs to do the same to be completely SoC
independent.
Signed-off-by: Nishanth Menon
---
drivers/bus/omap_l3_noc.h |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/bus/omap_l3_noc.h
This allows us to encompass target information and flag mux offset that
points to the target information into a singular structure. This saves
us the need to look up two different arrays indexed by module ID for
information.
This allows us to reduce the static target information allocation to
On Mon, 2014-04-14 at 09:44 -0700, Davidlohr Bueso wrote:
> On Tue, 2014-04-15 at 00:19 +0800, Jiang Liu wrote:
> > Hi Davidlohr,
> > Thanks for providing the DMAR table. According to the DMAR
> > table, one bug in the iommu driver fails to handle this entry:
> > [1D2h 0466 1] Device
On Mon, Apr 14, 2014 at 08:38:53AM +0100, Chanho Min wrote:
> Clock providers should be initialized before clocksource_of_init.
> If not, Clock source initialization can be fail to get the clock.
>
> Signed-off-by: Chanho Min
Acked-by: Will Deacon
Will
> ---
> arch/arm64/kernel/setup.c |
Move the L3 master structure out of the static definition to enable
reuse for other SoCs.
Signed-off-by: Nishanth Menon
---
drivers/bus/omap_l3_noc.h | 15 +++
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/drivers/bus/omap_l3_noc.h b/drivers/bus/omap_l3_noc.h
From: Afzal Mohammed
Add AM4372 information to handle L3 error.
AM4372 has two clk domains 100f and 200s. Provide flagmux and data
associated with it.
NOTE: Timeout doesn't have STDERRLOG_MAIN register. And per hardware
team, L3 timeout error cannot be cleared the normal way (by setting
bit 31
Le 13/04/2014 23:36, Paul Bolle a écrit :
> On Sun, 2014-04-13 at 21:13 +0200, Pascal COMBES wrote:
>> From: Pascal COMBES
>>
>> Fix coding style problem in drivers/staging/crystalhd/crystalhd_lnx.c:
>> No space needed before a cast.
>>
>> Signed-off-by: Pascal COMBES
>> ---
>> diff --git
On Mon, Apr 14, 2014 at 09:08:03AM +0100, Chanho Min wrote:
> 'make savedefconfig' doesn't generate defconfig properly due to
> missing COMPAT default. So Add default and set to yes.
I thought a missing `default' line in a Kconfig entry meant that the option
ended up defaulting to 'n'. What
On Tue, 2014-04-15 at 00:19 +0800, Jiang Liu wrote:
> Hi Davidlohr,
> Thanks for providing the DMAR table. According to the DMAR
> table, one bug in the iommu driver fails to handle this entry:
> [1D2h 0466 1] Device Scope Entry Type : 01
> [1D3h 0467 1] Entry Length
Currently the target instance information is organized indexed by bit
field offset into multiple arrays.
1. We currently have offsets specific to each target associated with each
clock domains are in seperate arrays:
l3_targ_inst_clk1
l3_targ_inst_clk2
l3_targ_inst_clk3
2. Then they are
On Mon, Apr 14, 2014 at 9:24 AM, Torsten Duwe wrote:
> On Mon, Apr 14, 2014 at 09:09:14AM -0700, H. Peter Anvin wrote:
>> I think the default should be zero, so each hwrng driver maintainer would
>> have to consider what guarantees that particular driver can give. If
>> anything 50% ought to
From: Sricharan R
DRA7xx SoC has the same l3-noc interconnect ip (as OMAP4 and OMAP5), but
AM437x SoC has just 2 modules instead of 3 which other SoCs have.
So, stop using direct access of array indices and use of->match data and
simplify implementation to benefit future usage.
While at it,
From: Rajendra Nayak
DRA7 is distinctly different from OMAP4 in terms of masters and clock
domain organization. There two main clock domains which is divided as
follows:
<0x4400 0x100> is clk1 and clk2 is the sub clock domain
<0x4500 0x1000> is clk3
Add all the data needed
Hi,
The following series is based on v3.15-rc1 + peter's patch series:
patch #1: https://patchwork.kernel.org/patch/3923141/
(drivers: bus: omap_l3: Convert to use devm_kzalloc)
patch #2: https://patchwork.kernel.org/patch/3923061/
(drivers: bus: omap_l3: Convert
tick_setup_device() is always passed cpumask of 'cpu', which is also passed as
parameter to this routine. So, just calculate the cpumask(cpu) in
tick_setup_device() instead of passing from every caller.
Signed-off-by: Viresh Kumar
---
kernel/time/tick-common.c | 8
1 file changed, 4
'broadcast' is used just once and we can easily use tick_resume_broadcast()
directly instead. Also it changes the code a bit to get rid of extra indentation
level which was forcing us to break function calls into two lines.
Signed-off-by: Viresh Kumar
---
kernel/time/tick-common.c | 15
From: Rajendra Nayak
On DRA7, unlike on OMAP4 and OMAP5, the flag mux input numbers used
to indicate the source of errors are not continous. Have a way in the
driver to catch these and WARN the user of the flag mux input thats
either undocumented or wrong.
In the similar vein, Timeout errors in
On Mon, Apr 14, 2014 at 9:06 AM, Torsten Duwe wrote:
>
> This patch introduces a derating factor to struct hwrng for
> the random bits going into the kernel input pool, and a common
> default derating for drivers which do not specify one.
>
> Signed-off-by: Torsten Duwe
>
> ---
>
Was using my machine normally, then my mouse cursor vanished. After switching
to a VT and back to X11, my cursor came back. But I did notice a nasty trace in
dmesg (below).
I have a few options specified on my command line related to i915, but these
worked fine through 3.13.9:
The logic between handling CUSTOM_ERROR and STANDARD_ERROR
is just the reporting style.
So make it generic, simplify and standardize the reporting
with both master and target information printed to log.
While at it, fix a minor formatting error.
Signed-off-by: Nishanth Menon
---
Currently we use __raw_readl and writel in this driver, however, there
is no strict sequencing needs for this driver, hence we should be good
with the relaxed variants.
While at it, simplify address computation using variables for register.
Signed-off-by: Nishanth Menon
---
tick_shutdown() calls clockevents_exchange_device() which already sets mode to
CLOCK_EVT_MODE_UNUSED and so tick_shutdown() doesn't need to do it.
Signed-off-by: Viresh Kumar
---
kernel/time/tick-common.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/kernel/time/tick-common.c
Part of tick_check_new_device() is exactly same as what's being done by
tick_install_replacement(). And so we can actually call
tick_install_replacement() directly from tick_check_new_device() instead of
replicating code.
Signed-off-by: Viresh Kumar
---
kernel/time/tick-common.c | 10 +++---
We have already checked if 'cpu' is online or not and so don't need to recheck
it.
Signed-off-by: Viresh Kumar
---
kernel/time/tick-sched.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
index 9cbba513..c81b6cf 100644
---
Hi All,
I'm observing a huge number of warnings produced during the boot of my Keystone
2 board
when USB is enabled.
[2.496460] BUG: using __this_cpu_read() in preemptible [] code:
khubd/202
[2.504030] caller is __mod_zone_page_state+0x20/0xc8
[2.509094] CPU: 1 PID: 202
__tick_nohz_task_switch() calls tick_nohz_full_kick(), which is already checking
tick_nohz_full_cpu() and so we don't need to repeat the same check here.
Remove it.
Signed-off-by: Viresh Kumar
---
kernel/time/tick-sched.c | 4
1 file changed, 4 deletions(-)
diff --git
On Mon, Apr 14, 2014 at 9:13 AM, Torsten Duwe wrote:
> On Mon, Apr 14, 2014 at 08:49:58AM -0700, Andy Lutomirski wrote:
>> [Resent because I forgot to email lkml. This also surreptitiously
>> fixes a silly typo on a patch description.]
>>
>> This is my attempt to come up with a workable way to
Am Montag, den 14.04.2014, 12:27 -0400 schrieb Alan Stern:
> On Mon, 14 Apr 2014 stef...@seibold.net wrote:
>
> > Zitat von Alan Stern :
> >
> >
> > >> <6>[ 167.936921] usb 2-2.1: new full-speed USB device number 3
> > >> using ohci-pci
> > >> <6>[ 168.067890] usb 2-2.1: New USB device
In tick_do_update_jiffies64() we are processing ticks only if delta is greater
than tick_period. This is what we are supposed to do here and it broke a bit
with this patch:
commit 47a1b796306356f358e515149d86baf0cc6bf007
Author: John Stultz
Date: Thu Dec 12 13:10:55 2013 -0800
tick_sched_handle() is called from two places and both pass 'regs' to it almost
same way. This patch removes this parameter to tick_sched_handle() and updates
tick_sched_handle() to get that by itself.
The only point of difference in the way this routine was called from its callers
was, don't
tick_nohz_task_switch() and __tick_nohz_task_switch() routines get task_struct
passed to them (always for the 'current' task), but they never use it. Remove
it.
Signed-off-by: Viresh Kumar
---
include/linux/tick.h | 8
kernel/sched/core.c | 2 +-
kernel/time/tick-sched.c | 2
__tick_nohz_task_switch() was called only from tick_nohz_task_switch() and there
is nothing much in tick_nohz_task_switch() as well. IOW, we don't need
unnecessary wrapper over __tick_nohz_task_switch() to be there. Merge all code
from __tick_nohz_task_switch() into tick_nohz_task_switch() and
On 04/14/2014 11:25 AM, Nishanth Menon wrote:
Please ignore this one patch from the series, there is a replacement
patch already posted as part of the series... this stale patch got
through :(
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
From: Borislav Petkov
So tools/ has been growing three, at a different stage of their
development export.h headers and so we should unite into one. Add
tools/include/ to the include path of virtio and liblockdep to pick the
shared header now.
Cc: Sasha Levin
Cc: Peter Zijlstra
Cc: Paul
nohz_full_buf[] is used at only one place, i.e. inside tick_nohz_init(). Make it
a local variable. Can move it out in case it is used in some other routines in
future.
Signed-off-by: Viresh Kumar
---
kernel/time/tick-sched.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
On Mon, Apr 14, 2014 at 12:19:31PM -0400, Pranith Kumar wrote:
> Hi Paul,
>
> On Mon, Apr 14, 2014 at 12:07 PM, Paul E. McKenney
> wrote:
> > On Sun, Apr 13, 2014 at 05:53:53PM -0400, Pranith Kumar wrote:
> >> remove duplicate definition of extern resched_cpu
> >>
> >> Signed-off-by: Pranith
401 - 500 of 2040 matches
Mail list logo
