From: Thomas Hebb
The USB PLL divider set by the marvell,berlin2-usb-phy compatible is not
correct for BG2. We couldn't change it before because BG2Q incorrectly
used the same compatible string. Now that BG2Q's compatible is fixed,
change BG2's divider to the correct value.
Signed-off-by:
From: Thomas Hebb
The marvell,berlin2cd-usb-phy compatible incorrectly sets the PLL
divider to BG2's value instead of BG2CD/BG2Q's. Change it to the right
value.
Signed-off-by: Thomas Hebb
Cc: sta...@vger.kernel.org
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-berlin-usb.c |
From: Sebastian Ott
Fix this compile error:
drivers/built-in.o: In function 'mv_usb2_phy_probe':
phy-pxa-28nm-usb2.c:(.text+0x25ec): undefined reference to
'devm_ioremap_resource'
drivers/built-in.o: In function 'mv_hsic_phy_probe':
phy-pxa-28nm-hsic.c:(.text+0x3084): undefined reference to
From: Roger Quadros
Relying on PM-ops for shutting down PHY clocks was a
bad idea since the users (e.g. PCIe/SATA) might not
have been suspended by then.
The main culprit for not shutting down the clocks was
the stray pm_runtime_get() call in probe.
Fix the whole thing in the right way by
Hi Greg,
Please find the pull request for 4.2 -rc cycle. This includes
a couple of driver fixes, one to fix suspend/resume and the other
to fix pll divider values. It also includes a Kconfig fix to fix
a compiler error.
Let me know if I have to change something.
Cheers
Kishon
The following
This driver will provide support for calls into the firmware that will
be used by other drivers like cpufreq and vc4.
Signed-off-by: Eric Anholt
Acked-by: Stephen Warren
---
v2: Improve commit message, point to mailbox.txt for how mboxes work.
v3: Use Lee's suggestion for mailbox phandle docs,
This gives us a function for making mailbox property channel requests
of the firmware, which is most notable in that it will let us get and
set clock rates.
Signed-off-by: Eric Anholt
Acked-by: Stephen Warren
---
v2: Drop power-domains stuff for now since we don't have the driver
core
Signed-off-by: Eric Anholt
Acked-by: Lee Jones (previous version with pm-domains)
Acked-by: Stephen Warren
---
v2: Drop pm-domains stuff since I've dropped it from the firmware
driver for now, until we get drivers/base fixed.
v3: Rename the compatible to "raspberrypi,bcm2835-firmware"
Hi
samsung s6,280euro,
imac,nikon,samsung products
site: isgayre. com
On Fri, Jul 17, 2015 at 10:39:25PM +0200, Thomas Gleixner wrote:
> Aside of documenting what that resume thing is for and why
> init_intel_energy_perf() needs to be called, I'm quite sure that this
> will fill up pretty fast with other stuff which gets lost across S/R.
Haha, I was thinking the
From: zhengxing
The driver is used for rockchip board using a max98090.
Reviewed-by: Dylan Reid
Signed-off-by: zhengxing
---
Changes in v2: None
.../bindings/sound/rockchip-max98090.txt | 19 ++
sound/soc/rockchip/Kconfig | 10 +
From: zhengxing
Hi,
The simple-card is not common at present, soc maybe need own machine
driver for jack detection.
Add drivers for two families of rockchip-bases chromebooks. These
machine drives don't use simplecard because we need custom jack
detection plumbing.
- use ts3a227e for ext
From: zhengxing
The driver is used for rockchip board using a rt5645/rt5650.
Reviewed-by: Dylan Reid
Signed-off-by: zhengxing
---
Changes in v2:
Signed-off-by: zhengxing
.../devicetree/bindings/sound/rockchip-rt5645.txt | 17 ++
sound/soc/rockchip/Kconfig |
On Fri, Jul 17, 2015 at 12:32:20PM -0500, Josh Poimboeuf wrote:
> Well, but this isn't some whitelist code to make stackvalidate happy.
>
> It's actually a real runtime frame pointer bug, and the rsp dependency
> is real. If it does the call without first creating the stack frame
> then it
On Fri, Jul 17, 2015 at 09:52:35AM -0700, Greg Kroah-Hartman wrote:
> On Fri, Jul 17, 2015 at 06:51:18PM +0530, Sudip Mukherjee wrote:
> > Now since all cleanups are done and the code is ready to be merged lets
> > move it out of staging into fbdev location.
>
> This is really hard for the fbdev
On Fri, Jul 17, 2015 at 05:33:55PM +0200, Jakub Sitnicki wrote:
> On Thu, Jul 16, 2015 at 01:28 PM CEST, Sudip Mukherjee
> wrote:
> > Stop using DBG_88E which is a custom macro for printing debugging
> > messages. Instead start using pr_debug and in the process define
> > pr_fmt.
>
> In the
+static int snd_rk_mc_remove(struct platform_device *pdev)
+{
+struct snd_soc_card *soc_card = platform_get_drvdata(pdev);
+
+snd_soc_card_set_drvdata(soc_card, NULL);
+snd_soc_unregister_card(soc_card);
+platform_set_drvdata(pdev, NULL);
No need for any of the _set_drvdata()
Create the documentation for SM712. Mention all the supported modes and
how to use.
Signed-off-by: Sudip Mukherjee
---
Documentation/fb/sm712fb.txt | 31 +++
1 file changed, 31 insertions(+)
create mode 100644 Documentation/fb/sm712fb.txt
diff --git
Now since sm712fb has moved out of staging update the maintainers list
accordingly.
Signed-off-by: Sudip Mukherjee
---
MAINTAINERS | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8133cef..2c77c30 100644
--- a/MAINTAINERS
+++
Now since all cleanups are done and the code is ready to be merged lets
move it out of staging into fbdev location.
Signed-off-by: Sudip Mukherjee
---
drivers/staging/Kconfig |2 -
drivers/staging/Makefile |1 -
drivers/staging/sm7xxfb/Kconfig | 13 -
Hi Mark,
On 2015年07月18日 02:11, Mark Brown wrote:
On Wed, Jul 15, 2015 at 11:15:43AM +0800, Xing Zheng wrote:
From: zhengxing
The driver is used for rockchip board using a rt5645/rt5650.
Same comments here, mostly good but some minor issues. The other thing
with both of these is that you
On 2015年07月18日 02:04, Mark Brown wrote:
On Wed, Jul 15, 2015 at 11:15:42AM +0800, Xing Zheng wrote:
This looks pretty good, a couple of minor points below which should be
quick to fix.
+static int rk_init(struct snd_soc_pcm_runtime *runtime)
+{
+ struct snd_soc_card *card =
On Sat, Jul 18, 2015 at 04:51:16AM +0200, Ingo Molnar wrote:
> Note what the names _don't_ contain: that we generate debug info! That fact
> is not
> present in the naming, and that's very much intentional, because the precise
> form
> of debug info is conditional:
>
> - if
* Andy Lutomirski wrote:
> On Fri, Jul 17, 2015 at 12:46 PM, Peter Zijlstra wrote:
> > On Fri, Jul 17, 2015 at 11:47:28AM -0500, Josh Poimboeuf wrote:
> >> stackvalidate reports the following warnings for __schedule():
> >>
> >> stackvalidate: kernel/sched/core.o: __schedule()+0x3e7:
* Luis R. Rodriguez wrote:
> On Thu, Jul 09, 2015 at 06:34:22PM -0700, Luis R. Rodriguez wrote:
> > From: "Luis R. Rodriguez"
> >
> > Ingo,
> >
> > You had asked for this to be kept in my tree until the end of the
> > merge window. I sent it a bit earlier than the end of the merge window,
>
* H. Peter Anvin wrote:
> On 07/16/2015 12:14 PM, Dave Hansen wrote:
> > The FPU rewrite removed the dynamic allocations of 'struct fpu'.
> > But, this potentially wastes massive amounts of memory (2k per
> > task on systems that do not have AVX-512 for instance).
> >
> > Instead of having a
Commit-ID: 5aaeb5c01c5b6c0be7b7aadbf3ace9f3a4458c3d
Gitweb: http://git.kernel.org/tip/5aaeb5c01c5b6c0be7b7aadbf3ace9f3a4458c3d
Author: Ingo Molnar
AuthorDate: Fri, 17 Jul 2015 12:28:12 +0200
Committer: Ingo Molnar
CommitDate: Sat, 18 Jul 2015 03:42:51 +0200
x86/fpu, sched: Introduce
Commit-ID: 0c8c0f03e3a292e031596484275c14cf39c0ab7a
Gitweb: http://git.kernel.org/tip/0c8c0f03e3a292e031596484275c14cf39c0ab7a
Author: Dave Hansen
AuthorDate: Fri, 17 Jul 2015 12:28:11 +0200
Committer: Ingo Molnar
CommitDate: Sat, 18 Jul 2015 03:42:35 +0200
x86/fpu, sched: Dynamically
Commit-ID: d132803e6c611d50c19baedc8ae520203a2baca7
Gitweb: http://git.kernel.org/tip/d132803e6c611d50c19baedc8ae520203a2baca7
Author: Andy Lutomirski
AuthorDate: Wed, 15 Jul 2015 14:25:16 -0700
Committer: Ingo Molnar
CommitDate: Fri, 17 Jul 2015 16:08:22 +0200
x86/entry: Fix
Commit-ID: 3c71ba3f80bbd476bbfb2a008da9b676031cbd32
Gitweb: http://git.kernel.org/tip/3c71ba3f80bbd476bbfb2a008da9b676031cbd32
Author: Alexey Brodkin
AuthorDate: Tue, 14 Jul 2015 12:05:20 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 15 Jul 2015 11:57:28 -0300
perf tools:
Commit-ID: a7fde09a78a8ae40b81cfb5096c3cefef6c078c9
Gitweb: http://git.kernel.org/tip/a7fde09a78a8ae40b81cfb5096c3cefef6c078c9
Author: Adrian Hunter
AuthorDate: Tue, 14 Jul 2015 15:32:41 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 15 Jul 2015 11:57:28 -0300
perf
On Fri, Jul 17, 2015 at 07:31:17PM +0200, Oleg Nesterov wrote:
> On 07/17, Dave Chinner wrote:
> >
> > On Thu, Jul 16, 2015 at 07:32:56PM +0200, Oleg Nesterov wrote:
> > >
> > > #ifdef CONFIG_LOCKDEP
> > > /*
> > >* We want lockdep to tell us about possible deadlocks with
Linus,
Please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
# HEAD: 5aaeb5c01c5b6c0be7b7aadbf3ace9f3a4458c3d x86/fpu, sched: Introduce
CONFIG_ARCH_WANTS_DYNAMIC_TASK_STRUCT and use it on x86
Two
Linus,
Please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
# HEAD: 0f44705175347ec96935d60b765b5d14ecc763bb tick: Move the export of
tick_broadcast_oneshot_control to the proper place
Fix for a
* Andy Lutomirski wrote:
> On Fri, Jul 17, 2015 at 9:47 AM, Josh Poimboeuf wrote:
> > These patches fix many of the warnings reported by stackvalidate.
> > They're based on top of the "Compile-time stack validation" v7 patch set
> > [1].
> >
> > They've been compile-tested and boot tested in a
Linus,
Please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
# HEAD: d49db342f0e276b354383b3281c5668b6b80f5c2 sched/fair: Test list head
instead of list entry in throttle_cfs_rq()
A rq throttling
Linus,
Please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
# HEAD: a6acd6a41168dc304738e84c8360cda9a6b86887 Merge tag
'perf-urgent-for-mingo' of
* Josh Poimboeuf wrote:
> On Fri, Jul 17, 2015 at 12:44:42PM -0700, Andy Lutomirski wrote:
> > On Fri, Jul 17, 2015 at 12:43 PM, Ingo Molnar wrote:
> > >
> > > * Josh Poimboeuf wrote:
> > >
> > >> ENTRY(aesni_set_key)
> > >> + FRAME
> > >> #ifndef __x86_64__
> > >> pushl KEYP
> >
I am David Wei .I am involved with the Guiyang Intellectual property bureau
which is in the Guizhou province of mainland China. I am getting in touch with
you regarding property investment that was facilitated by myself and my
colleagues a few years ago.
We had started this process with a
* Paul E. McKenney wrote:
> On Fri, Jul 17, 2015 at 09:51:31PM +0200, Ingo Molnar wrote:
> >
> > * Paul E. McKenney wrote:
> >
> > > And here is a prototype patch, which I intend to merge with the existing
> > > patch
> > > that renames rcu_lockdep_assert() to RCU_LOCKDEP_WARN(). I will
- On Jul 17, 2015, at 7:44 PM, Tom Zanussi tom.zanu...@linux.intel.com
wrote:
> On Fri, 2015-07-17 at 15:48 +, Mathieu Desnoyers wrote:
>> - On Jul 16, 2015, at 9:35 PM, Tom Zanussi tom.zanu...@linux.intel.com
>> wrote:
>>
>> > Hi Mathieu,
>> >
>> > On Thu, 2015-07-16 at 23:25
Linus,
Please pull the latest irq-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
irq-urgent-for-linus
# HEAD: 591e5bec13f15feb13fc445b6c9c59954711c4ac irqchip/gicv3-its: Fix
mapping of LPIs to collections
Misc irq fixes:
- two driver fixes,
Le 07/17/15 16:53, Stas Sergeev a écrit :
> 18.07.2015 02:35, Florian Fainelli пишет:
>> On 17/07/15 16:24, Stas Sergeev wrote:
>>> 18.07.2015 01:01, Florian Fainelli пишет:
On 17/07/15 13:03, Stas Sergeev wrote:
> 17.07.2015 21:50, Florian Fainelli пишет:
>> On 17/07/15 04:26, Stas
Hi Matthias,
Sascha hopes we can put CPU MTCMOS driver to his mtk-scpsys.c. We
understood but please let us describe our opinion.
(1) The code to initial CPU for SMP operation is in very early stage
during bring-up, the mtk-scpsys.c is not ready at the moment.
(2) The CPU MTCMOS driver may chip
On 2015年07月17日 09:59, Ian Munsie wrote:
Excerpts from Sukadev Bhattiprolu's message of 2015-07-17 11:51:04 +1000:
Are you seeing this on big-endian or little-endian system?
IIRC, I saw the opposite behavior on an LE system a few months ago.
i.e. without 1028ccf5, 'perf listf|grep syscall'
* Dave Hansen wrote:
> On 07/17/2015 12:23 PM, Ingo Molnar wrote:
>
> > Dave, can I put your Signed-off-by into this patch? I have already tested
> > these
> > two patches and they are looking good here - so unless you can see some
> > breakage
> > or other problem I'd prefer it to keep it
On Thu, Jul 16, 2015 at 4:23 PM, Toshi Kani wrote:
> ioremap() checks if a target range is in RAM and fails the request
> if true. There are multiple issues in the iormap RAM check interfaces.
>
> 1. region_is_ram() always fails with -1.
> 2. The check calls two functions, region_is_ram() and
On 7/17/15 6:02 PM, pi3orama wrote:
An example: we want to count the number of cycles between entry and exit point
of a particular library function (glibc write() for example). Context switch is
possible, but we don't care cycles consumed by other tasks. Then we need to
create a perf event in
发自我的 iPhone
> 在 2015年7月18日，上午8:42，Alexei Starovoitov 写道：
>
>> On 7/17/15 4:27 PM, pi3orama wrote:
>> Then we also need another BPF_MAP_TYPE_PERF_EVENT_HASHMAP for events in task
>> context.
>
> hmm. why? don't see a use case yet.
An example: we want to count the number of cycles between
Hi,
On (07/18/15 07:42), Minchan Kim wrote:
> I asked to remove the comment of zs_can_compact about lock.
> "Should be called under class->lock."
Oh... I somehow quickly read it and thought you were talking
about the commit message. Fixed and resent.
> Otherwise,
>
> Acked-by: Minchan Kim
On 07/06, dingu...@opensource.altera.com wrote:
> From: Dinh Nguyen
>
> Use of_clk_parent_fill to fill in the parent clock names' array.
>
> Signed-off-by: Dinh Nguyen
> Cc: Maxime Ripard
> Cc: "Emilio López"
> ---
Applied to clk-next with that fix I posted.
--
Qualcomm Innovation Center,
On 07/06, dingu...@opensource.altera.com wrote:
> From: Dinh Nguyen
>
> Use of_clk_parent_fill to fill in the parent clock names' array.
>
> Signed-off-by: Dinh Nguyen
> Tested-by Gabriel Fernandez
> Cc: Peter Griffin
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a
On 07/06, dingu...@opensource.altera.com wrote:
> From: Dinh Nguyen
>
> Use of_clk_parent_fill to fill in the parent clock names' array.
>
> Signed-off-by: Dinh Nguyen
> Cc: Tero Kristo
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux
On 07/06, dingu...@opensource.altera.com wrote:
> From: Dinh Nguyen
>
> Use of_clk_parent_fill to fill in the parent clock names' array.
>
> Signed-off-by: Dinh Nguyen
> Cc: Boris Brezillon
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a
On 07/06, dingu...@opensource.altera.com wrote:
> From: Dinh Nguyen
>
> Use of_clk_parent_fill to fill in the parent clock names' array.
>
> Signed-off-by: Dinh Nguyen
> Acked-by: Santosh Shilimkar
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora
On 07/06, dingu...@opensource.altera.com wrote:
> From: Dinh Nguyen
>
> Use of_clk_parent_fill to fill in the parent clock names' array.
>
> Signed-off-by: Dinh Nguyen
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation
On 07/06, dingu...@opensource.altera.com wrote:
> From: Dinh Nguyen
>
> Use of_clk_parent_fill to fill in the parent clock names' array.
>
> Signed-off-by: Dinh Nguyen
> Cc: Maxime Ripard
> Cc: "Emilio López"
> ---
Adds a warning. Squashed this in:
diff --git
We can avoid taking class ->lock around zs_can_compact() in
zs_shrinker_count(), because the number that we return back
is outdated in general case, by design. We have different
sources that are able to change class's state right after we
return from zs_can_compact() -- ongoing I/O operations,
From: Rafael J. Wysocki
acpi_processor_unregister_performance() actually doesn't use its
first argument, so drop it and update the callers accordingly.
Signed-off-by: Rafael J. Wysocki
---
drivers/acpi/processor_perflib.c|4 +---
drivers/cpufreq/acpi-cpufreq.c |5 ++---
From: Rafael J. Wysocki
After commit 8cfcfd39000d (acpi-cpufreq: Fix an ACPI perf unregister
issue) we store both a pointer to per-CPU data of the first policy
CPU and the number of that CPU which are redundant.
Since the CPU number has to be stored anyway for the unregistration,
the pointer to
Hi,
The following two patches clean up a couple of things in the ACPI processor
driver and the ACPI cpufreq driver:
[1/2] Drop the unused first argument of acpi_processor_unregister_performance().
[2/2] Drop the now redundant acpi_data pointer from acpi_cpufreq_data.
Both patches on top of the
On 07/10, James Liao wrote:
> MT8173 MMPLL frequency settings are different from common PLLs.
> It needs different post divider settings for some ranges of frequency.
> This patch add support for MT8173 MMPLL frequency setting by adding
> div-rate table to lookup suitable post divider setting
On 07/10, James Liao wrote:
> Avoid u32 overflow when calculate post divider setting, and
> increase the max post divider setting from 3 (/8) to 4 (/16).
>
> Signed-off-by: James Liao
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux
On 07/10, James Liao wrote:
> Write postdiv and pcw settings at the same time for PLLs if postdiv
> and pcw settings are on the same register.
>
> This is need by PLLs such as MT8173 MMPLL and ARM*PLL.
>
> Signed-off-by: James Liao
> ---
Applied to clk-next
--
Qualcomm Innovation Center,
On 7/17/15 4:27 PM, pi3orama wrote:
Then we also need another BPF_MAP_TYPE_PERF_EVENT_HASHMAP for events in task
context.
hmm. why? don't see a use case yet.
I choose current implementation because I think we may need perf event not
wrapped in map in future (for example, tracepoints). With
On 07/17/2015 05:36 PM, Dmitry Torokhov wrote:
Wakeup property of device is not Linux-specific, it describes intended
system behavior regardless of the OS being used. Therefore let's drop
"linux," prefix, and, while at it, use the same name as I2C bus does:
"wakeup-source".
We keep parsing old
On Fri, 2015-07-17 at 11:35 +0200, Luis de Bethencourt wrote:
> bool Reval is set to match the value of bHalfWirelessN24GMode just to
> this. The value can be returned directly. Removing uneeded bool.
trivia:
> diff --git a/drivers/staging/rtl8192u/r8192U_core.c
>
Wakeup property of device is not Linux-specific, it describes intended
system behavior regardless of the OS being used. Therefore let's drop
"linux," prefix, and, while at it, use the same name as I2C bus does:
"wakeup-source".
We keep parsing old name to keep compatibility with old DTSes.
Wakeup property of device is not Linux-specific, it describes intended
system behavior regardless of the OS being used. Therefore let's drop
"linux," prefix, and, while at it, use the same name as I2C bus does:
"wakeup-source".
We keep parsing old name to keep compatibility with old DTSes.
Wakeup property of device is not Linux-specific, it describes intended
system behavior regardless of the OS being used. Therefore let's drop
"linux," prefix, and, while at it, use the same name as I2C bus does:
"wakeup-source".
We keep parsing old name to keep compatibility with old DTSes.
Wakeup property of device is not Linux-specific, it describes intended
system behavior regardless of the OS being used. Therefore let's drop
"linux," prefix, and, while at it, use the same name as I2C bus does:
"wakeup-source".
We keep parsing old name to keep compatibility with old DTSes.
Hi,
Currently input drivers use many forms of annotating devices that should
be set up as wakeup sources for the system. This patch series converts them
all to use "wakeup-source" name (to match what i2c devices are using) while
keeping old names as fallback to keep compatibility with existing
Wakeup property of device is not Linux-specific, it describes intended
system behavior regardless of the OS being used. Therefore let's drop
"linux," prefix, and, while at it, use the same name as I2C bus does:
"wakeup-source".
We keep parsing old name to keep compatibility with old DTSes.
Wakeup property of device is not Linux-specific, it describes intended
system behavior regardless of the OS being used. Therefore let's drop
"linux," prefix, and, while at it, use the same name as I2C bus does:
"wakeup-source".
We keep parsing old name to keep compatibility with old DTSes.
The "ARM: mm: Introduce virt_to_idmap() with an arch hook" defines
arch_virt_to_idmap hook in arch/arm/mm/idmap.c. That breaks systems w/o
MMU because that file is not built for them.
This patch fixes this bug.
Signed-off-by: Vitaly Andrianov
---
arch/arm/include/asm/memory.h | 4
1 file
On Fri, 2015-07-17 at 15:59 +0200, Joseph-Eugene Winzer wrote:
> Fixed a few lines that were longer than 80 chars.
[]
> diff --git a/drivers/staging/rtl8192u/r8192U_core.c
> b/drivers/staging/rtl8192u/r8192U_core.c
[]
> @@ -212,7 +212,9 @@ static void rtl819x_set_channel_map(u8 channel_plan,
>
On Fri, 2015-07-17 at 15:59 +0200, Joseph-Eugene Winzer wrote:
> Reformatting the code without introducing other warnings
> like 'Avoid unnecessary line continuations' or breaking strings.
Very few of these seem to be improvements and many
of them should likely be in separate patches.
> diff
On Tuesday, July 14, 2015 10:52:35 AM Pan Xinhui wrote:
> hi, Rafael,
> let me do more explanation :)
>
> On 2015年07月14日 10:09, Pan Xinhui wrote:
> > hi, Rafael,
> > thanks for you reply :)
> > On 2015年07月14日 07:26, Rafael J. Wysocki wrote:
> >> On Monday, July 13, 2015 02:33:08 PM Pan
On Fri, Jul 17, 2015 at 04:20:57PM -0700, Andy Lutomirski wrote:
> On Fri, Jul 17, 2015 at 3:55 PM, Paul E. McKenney
> wrote:
> > On Fri, Jul 17, 2015 at 03:13:36PM -0700, Andy Lutomirski wrote:
> >> On Fri, Jul 17, 2015 at 2:19 PM, Paul E. McKenney
> >> wrote:
> >> > On Fri, Jul 17, 2015 at
On Thu, Jul 16, 2015 at 07:42:03PM -0500, Eric W. Biederman wrote:
> Dave Chinner writes:
>
> > On Wed, Jul 15, 2015 at 11:47:08PM -0500, Eric W. Biederman wrote:
> >> Casey Schaufler writes:
> >> > On 7/15/2015 6:08 PM, Andy Lutomirski wrote:
> >> >> If I mount an unprivileged filesystem, then
18.07.2015 02:35, Florian Fainelli пишет:
On 17/07/15 16:24, Stas Sergeev wrote:
18.07.2015 01:01, Florian Fainelli пишет:
On 17/07/15 13:03, Stas Sergeev wrote:
17.07.2015 21:50, Florian Fainelli пишет:
On 17/07/15 04:26, Stas Sergeev wrote:
17.07.2015 02:25, Florian Fainelli пишет:
On
On Fri, Jul 17, 2015 at 4:31 PM, Andi Kleen wrote:
> On Fri, Jul 17, 2015 at 03:00:18PM -0700, Stephane Eranian wrote:
>> Andi,
>>
>> On Fri, Jul 17, 2015 at 2:19 PM, Andi Kleen wrote:
>> >> But then, the SDM is misleading. It is not describing what's
>> >> implemented for SKL.
>> >
>> >
On Tue, May 5, 2015 at 10:50 AM, Ingo Molnar wrote:
>
> * Linus Torvalds wrote:
>
>> On Tue, May 5, 2015 at 9:23 AM, Ingo Molnar wrote:
>> > 83 files changed, 3742 insertions(+), 2841 deletions(-)
>>
>> How much of this is just the added instrumentation? [...]
>
> Half of it is that, plus a
On 09/07/2015 at 08:45:54 +0100, S Twiss wrote :
> From: S Twiss
>
> Add device tree bindings for the DA9062 RTC driver component
>
> Signed-off-by: Steve Twiss
>
> ---
> Checks performed with linux-next/next-20150708/scripts/checkpatch.pl
> da9062.txttotal: 0 errors, 0
On Sat, Jul 18, 2015 at 01:29:30AM +0200, Oleg Nesterov wrote:
> On 07/15, Paul E. McKenney wrote:
> >
> > On Wed, Jul 15, 2015 at 09:36:01PM +0200, Oleg Nesterov wrote:
> > >
> > > Do you mean you need another user except percpu_rw_semaphore? I do
> > > not see any right now...
> >
> > Not asking
From: "Paul E. McKenney"
The rcu_torture_cbflood() function correctly checks for flavors of
RCU that lack analogs to call_rcu() and rcu_barrier(), but in that
case it fails to terminate correctly. In fact, it terminates so
incorrectly that segfaults can result. This commit therefore causes
Hi,
On 09/07/2015 at 08:45:53 +0100, S Twiss wrote :
> From: S Twiss
>
> Add DA9062 RTC support into the existing DA9063 RTC driver component by
> using generic access tables for common register and bit mask definitions.
>
> The following change will add generic register and bit mask support
Hello!
This series contains torture-test updates:
1. Improve bounds checking for n_barrier_cbs: No more negatives.
2. Improve bounds checking for nfakewriters: No more negatives.
3. Improve bounds checking for shuffle_interval: No more negatives.
4. Fix
From: "Paul E. McKenney"
Specifying a negative rcutorture.shuffle_interval value will cause a
negative value to be used as a sleep time. This commit therefore
refuses to start shuffling unless the rcutorture.shuffle_interval
value is greater than zero.
Signed-off-by: Paul E. McKenney
---
From: "Paul E. McKenney"
Currently, a negative value for rcutorture.nfakewriters= can cause
rcutorture to pass a negative size to the memory allocator, which
is not really a particularly good thing to do. This commit therefore
adds bounds checking to this parameter, so that values that are less
From: "Paul E. McKenney"
Although RCU-tasks isn't really designed to support rcu_dereference()
and list manipulation, that is how rcutorture tests it. Which means
that lockdep-RCU complains about the rcu_dereference_check() invocations
because RCU-tasks doesn't have read-side markers. This
From: "Paul E. McKenney"
Currently none of the RCU-tasks scenarios enables lockdep-RCU, which
causes bugs to be missed. This commit therefore enables lockdep-RCU
on TASKS01.
Signed-off-by: Paul E. McKenney
---
tools/testing/selftests/rcutorture/configs/rcu/TASKS01 | 4 ++--
1 file changed, 2
From: "Paul E. McKenney"
A negative value for rcutorture.n_barrier_cbs can pass a negative value
to the memory allocator, so this commit instead causes rcu_barrier()
testing to be disabled in this case.
Signed-off-by: Paul E. McKenney
---
kernel/rcu/rcutorture.c | 2 +-
1 file changed, 1
On Fri, Jul 10, 2015 at 03:00:33PM +0900, Krzysztof Kozlowski wrote:
> i2c_driver does not need to set an owner because i2c_register_driver()
> will set it.
>
> Signed-off-by: Krzysztof Kozlowski
Applied, thank you.
>
> ---
>
> The coccinelle script which generated the patch was sent here:
>
On Fri, 2015-07-17 at 15:48 +, Mathieu Desnoyers wrote:
> - On Jul 16, 2015, at 9:35 PM, Tom Zanussi tom.zanu...@linux.intel.com
> wrote:
>
> > Hi Mathieu,
> >
> > On Thu, 2015-07-16 at 23:25 +, Mathieu Desnoyers wrote:
> >> * Tom Zanussi wrote:
> >> >> Add tracing_map, a
Hi Sanchayan,
On Thu, Jul 16, 2015 at 08:43:21PM +0530, Sanchayan Maity wrote:
> The Colibri Vybrid VF50 module supports 4-wire touchscreens using
> FETs and ADC inputs. This driver uses the IIO consumer interface
> and relies on the vf610_adc driver based on the IIO framework.
This looks
On 17/07/15 16:24, Stas Sergeev wrote:
> 18.07.2015 01:01, Florian Fainelli пишет:
>> On 17/07/15 13:03, Stas Sergeev wrote:
>>> 17.07.2015 21:50, Florian Fainelli пишет:
On 17/07/15 04:26, Stas Sergeev wrote:
> 17.07.2015 02:25, Florian Fainelli пишет:
>> On 16/07/15 07:50, Stas
From: "Paul E. McKenney"
The grace-period kthread sleeps waiting to do a force-quiescent-state
scan, and when awakened sets rsp->gp_state to RCU_GP_DONE_FQS.
However, this is confusing because the kthread has not done the
force-quiescent-state, but is instead just starting to do it. This commit
From: Peter Zijlstra
The synchronize_sched_expedited() currently invokes try_stop_cpus(),
which schedules the stopper kthreads on each online non-idle CPU,
and waits until all those kthreads are running before letting any
of them stop. This is disastrous for real-time workloads, which
get hit
From: "Paul E. McKenney"
The CONFIG_RCU_CPU_STALL_INFO has been default-y for a couple of
releases with no complaints, so it is time to eliminate this Kconfig
option entirely, so that the long-form RCU CPU stall warnings cannot
be disabled. This commit does just that.
Signed-off-by: Paul E.
1 - 100 of 1936 matches
Mail list logo
