On 03/17/2015 07:37 PM, Fabian Frederick wrote:
> of_device_id is always used as const.
> (See driver.of_match_table and open firmware functions)
>
> Signed-off-by: Fabian Frederick
> ---
> drivers/net/ethernet/xilinx/ll_temac_main.c | 2 +-
> drivers/net/ethernet/xilinx/xilinx_axienet_mai
From: Graeme Gregory
ACPI 5.1 does not currently support S states for ARM64 hardware but
ACPI code will call acpi_target_system_state() and acpi_sleep_init()
for device power management, so introduce
CONFIG_ACPI_SYSTEM_POWER_STATES_SUPPORT and select it for x86 and
ia64 only to make sleep functio
On Tue, 17 Mar 2015, Joe Perches wrote:
> On Tue, 2015-03-17 at 08:06 -0400, Nicholas Mc Guire wrote:
> > Converting milliseconds to jiffies by "val * HZ / 1000" is technically
> > OK but msecs_to_jiffies(val) is the cleaner solution and handles all
> > corner cases correctly. This is a minor API
On 18 March 2015 at 06:10, MyungJoo Ham wrote:
>> Hello,
>>
>> something happened during the last cycle and an old version of the devfreq
>> driver was merged.
>>
>> This thread contains patches that bring it up to date to the last submitted
>> version and also incorporates the feedback that that
I started to work with PPI interface so that it would be available
under character device sysfs directory and realized that chip
registeration was still too messy.
In TPM 1.x in some rare scenarios (errors that almost never occur)
wrong order in deinitialization steps was taken in teardown. I
repr
Hi all,
Changes since 20150317:
The vfs tree still had its build failure for which I applied a patch
and gained a conflict against the ext3 tree.
The slave-dma tree gained conflicts against the arm-soc and renesas trees.
The crypto tree lost its build failure.
The virtio tree gained a
2015-03-17 18:46 GMT+09:00 Aneesh Kumar K.V :
> Joonsoo Kim writes:
>
>> I passed boot test on x86, ARM32 and ARM64. I did some stress tests
>> on x86 and there is no problem. Feel free to enjoy and please give me
>> a feedback. :)
>
> Tested on ppc64 with kvm. (I used the CONFIG_SPARSEMEM_VMEMMAP
add device tree for psci-0.2 on mt8173 platform
add device tree for cupidle-arm64 on mt8173 platform
Signed-off-by: Howard Chen
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 30 ++
1 file changed, 26 insertions(+), 4 deletions(-)
diff --git a/arch/arm64/boot/dts/med
If a platform has a particular device permanently attached to a UART,
there may be out-of-band signaling necessary to power the device
on and off.
This driver controls that signalling for a number of different devices.
It can
- enable/disable a regulator
- toggle a GPIO
- register an 'rfkill' w
Hi again,
here is version 3 of support for tty-slaves.
This version introduces a new bus-type for tty-slaves, and causes
a tty-slave device to appear in /sys/devices between the uart and the
tty.
It effectively intercepts and calls from the tty to the uart (i.e. any
tty_operations) and appli
uart_{suspend,resume}_port seach the children of a uart device
to find a particular tty device.
This requires all the ttys to be direct children of the uart.
A future patch will allow a 'tty_slave' to intervene between
the port and the uart, voiding this requirement.
So change to use class_find_d
A "tty slave" is a device connected via UART.
Such a device may need its own driver, e.g. for powering
it up on tty open and powering it down on tty release.
tty-slave is a new bus-type which drivers can be written and devices
created.
A "tty slave" device is declared as a child of the uart in
de
2015-03-17 21:15 GMT+09:00 Mark Rutland :
> Commit 9aabf810a67cd97e ("mm/slub: optimize alloc/free fastpath by
> removing preemption on/off") introduced an occasional hang for kernels
> built with CONFIG_PREEMPT && !CONFIG_SMP.
>
> The problem is the following loop the patch introduced to
> slab_al
On Tue, 2015-03-17 at 16:17 -0700, Andrew Morton wrote:
> ---
> a/scripts/checkpatch.pl~checkpatch-match-more-world-writable-permissions-fix
[]
> -$our $mode_perms_world_writable = qr{
> +our $mode_perms_world_writable = qr{
You're a perl monk too? Cool!
Thanks.
--
To unsubscribe from this li
2015-03-13 21:12 GMT+09:00 Roman Pen :
> Previous implementation allocates new vmap block and repeats search of a free
> block from the very beginning, iterating over the CPU free list.
>
> Why it can be better??
>
> 1. Allocation can happen on one CPU, but search can be done on another CPU.
>I
2015-03-13 21:12 GMT+09:00 Roman Pen :
> In original implementation of vm_map_ram made by Nick Piggin there were two
> bitmaps: alloc_map and dirty_map. None of them were used as supposed to be:
> finding a suitable free hole for next allocation in block. vm_map_ram
> allocates
> space sequentia
Provide MT6397 RTC interrupt, base address, and register in
MT6397 MFD.
Signed-off-by: Eddie Huang
---
drivers/mfd/mt6397-core.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/drivers/mfd/mt6397-core.c b/drivers/mfd/mt6397-core.c
index b61c4eb..ef431d8 100644
--- a/drivers/
Add Mediatek RTC driver to maintainer entry.
Signed-off-by: Eddie Huang
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index ddc5a8c..ca27a69 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1202,6 +1202,13 @@ W: http://www.digriz.org.uk/
From: Tianping Fang
Add Mediatek MT6397 RTC driver
Signed-off-by: Tianping Fang
Signed-off-by: Eddie Huang
---
drivers/rtc/Kconfig | 10 ++
drivers/rtc/Makefile | 1 +
drivers/rtc/rtc-mt6397.c | 454 +++
3 files changed, 465 insertions(+
RTC is one submodule of Mediatek MT6397 PMIC chip[1]. This series
support RTC driver that work with Mediatek SoC like MT8135, MT8173.
It implements second counter and also provide alarm function.
This series base on 4.0-rc1, and Sascha's PMIC mfd patch[2]. Test ok
on MT8173 platform.
[1] https:
Document the device tree binding for Broadcom iProc architecture based
clock controller
Signed-off-by: Ray Jui
Reviewed-by: Scott Branden
---
.../bindings/clock/brcm,iproc-clocks.txt | 171
1 file changed, 171 insertions(+)
create mode 100644
Documentation/devi
This adds basic and generic support for various iProc PLLs and clocks
including the ARMPLL, GENPLL, LCPLL, MIPIPLL, and ASIU clocks.
SoCs under the iProc architecture can define their specific register
offsets and clock parameters for their PLL and clock controllers. These
parameters can be passed
Remove old Cygnus dummy clock binding document, as it's replaced by
Documentation/devicetree/bindings/clock/brcm,iproc-clocks.txt
Signed-off-by: Ray Jui
---
.../devicetree/bindings/clock/bcm-cygnus-clock.txt | 34
1 file changed, 34 deletions(-)
delete mode 100644 Documen
Replace current device tree dummy clocks with real clock support for
Broadcom Cygnus SoC
Signed-off-by: Ray Jui
Reviewed-by: Scott Branden
---
arch/arm/boot/dts/bcm-cygnus-clock.dtsi | 112 ---
arch/arm/boot/dts/bcm-cygnus.dtsi |2 +-
2 files changed, 88 i
The Broadcom Cygnus SoC is architected under the iProc architecture. It
has the following PLLs: ARMPLL, GENPLL, LCPLL0, MIPIPLL, all dervied
from an onboard crystal. Cygnus also has various ASIU clocks that are
derived directly from the onboard crystal.
Signed-off-by: Ray Jui
Reviewed-by: Scott B
This patchset contains the initial common clock support for Broadcom's iProc
family of SoCs. The iProc clock architecture comprises of various PLLs, e.g.,
ARMPLL, GENPLL, LCPLL0, MIPIPLL, and etc. An onboard crystal serves as the
basic reference clock for these PLLs. Each PLL may have several leaf
The clock code under drivers/clk/bcm now contains code for both the
Broadcom mobile SoCs and the iProc SoCs. Change the the makefile
dependency to be under config flag CONFIG_ARCH_BCM that's enabled for
both families of SoCs
Signed-off-by: Ray Jui
---
drivers/clk/Makefile |2 +-
1 file chang
At 2015-03-17 18:25:24, "Linus Walleij" wrote:
>On Fri, Mar 6, 2015 at 3:04 AM, Chao Xie wrote:
>
>> Signed-off-by: Chao Xie
>
>First can some of the MMP people comment on this driver please?
>(Eric/Haojian)
>
>So this driver duplicates drivers/gpio/gpio-pxa.c in some sense but
>is nicer and c
On Fri, Mar 13, 2015 at 09:45:59AM -0400, Paul Moore wrote:
> On Monday, March 09, 2015 04:24:32 PM Boqun Feng wrote:
> > Ping.
> > Any opinion?
>
> You might want to look at some of the recent changes to Al's vfs.git#for-next
> branch; at the very least it looks like your patch should be rebased
Hi Linus:
On Mon, Mar 09, 2015 at 04:19:50PM +1100, Herbert Xu wrote:
>
> This push fixes a bug in the ARM XTS implementation that can
> cause failures to in decrypting encrypted disks.
For some reason this didn't get pulled so I'm resending it with
another fix.
The new fix is a memory overwrit
> As the DT bindings don't have an operating-points property any more,
> build the OPP table from the frequencies supported by the EMC clock.
>
> Signed-off-by: Tomeu Vizoso
> ---
> drivers/devfreq/tegra-devfreq.c | 12 ++--
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --g
Hardware random number quality is measured from 0 (no entropy) to 1024
(perfect entropy). Allow hardware devices to assert the full range by
truncating the device-provided value at 1024 instead of 1023.
Signed-off-by: Keith Packard
---
drivers/char/hw_random/core.c | 3 ++-
1 file changed, 2 ins
On Tue, Mar 17, 2015 at 10:13:28PM -0700, Keith Packard wrote:
> Hardware random number quality is measured from 0 (no entropy) to 1024
> (perfect entropy). Allow hardware devices to assert the full range by
> truncating the device-provided value at 1024 instead of 1023.
>
> Signed-off-by: Keith P
> Hello,
>
> something happened during the last cycle and an old version of the devfreq
> driver was merged.
>
> This thread contains patches that bring it up to date to the last submitted
> version and also incorporates the feedback that that version received, plus
> some other small fixes and i
2015-03-18 6:58 GMT+09:00 Andrew Morton :
> On Tue, 17 Mar 2015 17:22:46 +0900 Roman Peniaev wrote:
>
>> >> My second patch fixes this problem.
>> >> I occupy the block on allocation and avoid jumping to the search loop.
>> >
>> > I'm not sure that this fixes above case.
>> > 'vm_map_ram (3) * 85'
2015-03-17 17:22 GMT+09:00 Roman Peniaev :
> On Tue, Mar 17, 2015 at 4:29 PM, Joonsoo Kim wrote:
>> On Tue, Mar 17, 2015 at 02:12:14PM +0900, Roman Peniaev wrote:
>>> On Tue, Mar 17, 2015 at 1:56 PM, Joonsoo Kim wrote:
>>> > On Fri, Mar 13, 2015 at 09:12:55PM +0900, Roman Pen wrote:
>>> >> If sui
Resending v2 soon. This version was from wrong branch :( Sorry.
On Wed, Mar 18, 2015 at 06:50:01AM +0200, Jarkko Sakkinen wrote:
> I started to work with PPI interface so that it would be available
> under character device sysfs directory and realized that chip
> registeration was still too messy.
From: "Tom(JeHyeon) Yeon"
change "deadlock_detect" to "chwalk" following by commit 8930ed80
Signed-off-by: Tom(JeHyeon) Yeon
---
kernel/locking/rtmutex.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c
index 6357265..b7
Hi,
FYI, we noticed performance changes on `fsmark.files_per_sec' by
d4b4c2cdffab86f5c7594c44635286a6d277d5c6:
> commit d4b4c2cdffab86f5c7594c44635286a6d277d5c6
> Author: s...@kernel.org
> AuthorDate: Mon Dec 15 12:57:03 2014 +1100
> Commit: NeilBrown
> CommitDate:
Hi,
FYI, we noticed performance changes on `fsmark.files_per_sec' by
4400755e356f9a2b0b7ceaa02f57b1c7546c3765:
> commit 4400755e356f9a2b0b7ceaa02f57b1c7546c3765
> Author: NeilBrown
> AuthorDate: Thu Feb 26 12:47:56 2015 +1100
> Commit: NeilBrown
> CommitDate: Wed Ma
On Tue, 2015-03-17 at 21:19 +0530, Shreyas B Prabhu wrote:
>
> On Tuesday 17 March 2015 03:09 PM, Benjamin Herrenschmidt wrote:
> > On Tue, 2015-03-17 at 19:57 +1100, Michael Ellerman wrote:
> >>
> >> >From what I can see below, the decision as to whether you apply the
> >> >workaround
> >> or no
I started to work with PPI interface so that it would be available
under character device sysfs directory and realized that chip
registeration was still too messy.
In TPM 1.x in some rare scenarios (errors that almost never occur)
wrong order in deinitialization steps was taken in teardown. I
repr
On Tue, 2015-03-17 at 16:46 -0400, Peter Hurley wrote:
> This reverts commit 2fa645cb2703d9b3786d850db815414dfeefa51d.
>
> The assumption that at least 1 preferred console will be registered
> when the stdout-path property is set is invalid, which can result
> in _no_ consoles.
>
> Signed-off-by:
From: Frederic Weisbecker
Create a cpumask that limit the affinity of all unbound workqueues.
This cpumask is controlled though a file at the root of the workqueue
sysfs directory.
It works on a lower-level than the per WQ_SYSFS workqueues cpumask files
such that the effective cpumask applied fo
Current apply_workqueue_attrs() includes pwqs-allocation and pwqs-installation,
so when we batch multiple apply_workqueue_attrs()s as a transaction, we can't
ensure the transaction must succeed or fail as a complete unit.
To solve this, we split apply_workqueue_attrs() into three stages.
The first
This patchset mostly copies from Frederic and split the apply_workqueue_attrs()
as TJ's suggest.
This patchset still doesn't include the patch "workqueue: Allow changing
attributions
of ordered workqueues", I hope to reduce the review processing. The handling
for the ordered workqueue will be rep
Allow to modify the low-level unbound workqueues cpumask through
sysfs. This is performed by traversing the entire workqueue list
and calling wq_unbound_install_ctx_prepare() on the unbound workqueues
with the low level mask passed in. Only after all the preparation are done,
we commit them all tog
From: Frederic Weisbecker
The sysfs code usually belongs to the botom of the file since it deals
with high level objects. In the workqueue code it's misplaced and such
that we'll need to work around functions references to allow the sysfs
code to call APIs like apply_workqueue_attrs().
Lets move
On Sat, Mar 14, 2015 at 11:55:16PM +0300, Evgeniy Polyakov wrote:
> Hi David
>
> 12.03.2015, 03:54, "David Fries" :
> > Would that be removing all four refcnt, w1_slave, w1_master,
> > w1_family, w1_cb_block, or just some of them? It sounds good to me,
> > if that had bugs there would be much mor
> The misleading log "releasing devfreq which doesn't exist" prints out
> for well behaved clients. This is due to the fact that _remove_devfreq
> calls itself recursively by proxy (via put_device()). The second time
> _devfreq_remove is called the respective device has already been
> deleted, ca
Hi all,
Today's linux-next merge of the kvm-arm tree got a conflict in
virt/kvm/arm/vgic.c between commit ae705930fca6 ("arm/arm64: KVM: Keep
elrsr/aisr in sync with software model") from Linus' tree and commit
71760950bf3d ("arm/arm64: KVM: add a common vgic_queue_irq_to_lr fn")
from the kvm-arm
Yes. The last commit that modifies 'ubifs/dir.c' (sorry for missing
the context). All error handling routines introduced by
'd7f0b70d30ffb9bbe6b8a3e1035cf0b79965ef53' 1) incorrectly 'unlock' and
2) incorrectly restore 'i_size'.
Thanks,
Taesoo
On 03/17/15 at 08:18pm, Brian Norris wrote:
> On Tue,
Hi Uwe,
On Tue, 2015-03-17 at 14:43 +0100, Uwe Kleine-König wrote:
> Hello Eddie,
>
> On Tue, Mar 17, 2015 at 08:31:14PM +0800, Eddie Huang wrote:
> > On Mon, 2015-03-16 at 16:30 +0100, Uwe Kleine-König wrote:
> > > On Wed, Jan 28, 2015 at 05:27:56PM +0800, Eddie Huang wrote:
> > > > [...]
> > >
Add enable-method property to enable SMP support.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-a23.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-a23.dtsi b/arch/arm/boot/dts/sun8i-a23.dtsi
index 78440dffd678..b5684a0048b2 100644
--- a/arch/arm/
The A23 SoC has the architected timer, but the existing firmware from
Allwinner does not set CNTFRQ at all.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-a23.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-a23.dtsi b/arch/arm/boot/dts/sun8i-
The A23 is a dual Cortex-A7. Add the logic to use the IPs used to
control the CPU configuration and the CPU power so that we can
bring up secondary CPUs at boot.
Signed-off-by: Chen-Yu Tsai
---
We can't use of_io_request_and_map() here, as it will conflict
with PRCM, and leave us without a seria
Hi Maxime,
This series adds support for SMP and arch-timer for the
A23. This follows our discussion from yesterday about
getting arch-timer support for sun8i and sun9i. I will
post a separate patch for sun9i-a80.
I know some people would like to see arch-timer and SMP
supported with PSCI, but wor
On Tue, Mar 17, 2015 at 10:09:26PM -0400, Taesoo Kim wrote:
> When ubifs_init_security() fails, 'ui_mutex' is incorrectly
> unlocked and incorrectly restores 'i_size'. There are four
> such places that were introduce by the last commit.
"The last commit" is not very descriptive. Are you speaking o
On Wed, Mar 18, 2015 at 12:02 AM, K. Y. Srinivasan
wrote:
Optimize notifying the host by deferring notification until there
are no more packets to be sent. This will help in batching the
requests
on the host.
Signed-off-by: K. Y. Srinivasan
---
drivers/net/hyperv/hyperv_net.h |2 +-
On Tue, Mar 17, 2015 at 08:33:27AM -0700, Kees Cook wrote:
> On Mon, Mar 16, 2015 at 4:24 PM, Dave Chinner
> wrote:
> > On Mon, Mar 09, 2015 at 02:00:11PM +, David Drysdale wrote:
> >> Test basic openat(2) behaviour.
> >>
> >> Test that if O_BENEATH flag is set, openat() will only open
> >> pa
This patch change /proc/stat to show each cpu,
we show each present cpus instead of eacn online cpu,
because some cpus are online / offline dynamically,
we should also show its cputime even it is offline,
some lib will read this file to detect cpu numbers,
we should also return the real present cpu
[+cc Rafael]
Hi Rajat,
On Tue, Mar 17, 2015 at 2:11 PM, Rajat Jain wrote:
> Hello,
>
> I was wondering if any one has a any suggestions to make here. I
> believe this is a pretty serious deadlock - and I'm looking for ideas
> on what should be the right way to fix this.
I agree, this definitely
Hi Jaegeuk,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Wednesday, March 18, 2015 12:58 AM
> To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net
> Cc: Jaegeuk Kim
> Subject: [f2fs-dev] [PATCH 2/4] f2fs:
When ubifs_init_security() fails, 'ui_mutex' is incorrectly
unlocked and incorrectly restores 'i_size'. There are four
such places that were introduce by the last commit.
Signed-off-by: Taesoo Kim
---
fs/ubifs/dir.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/
When 'jh->b_transaction == transaction' (asserted by below)
J_ASSERT_JH(jh, (jh->b_transaction == transaction || ...
'journal->j_list_lock' will be incorrectly unlocked, since
the the lock is aquired only at the end of if / else-if
statements (missing the else case).
Signed-off-by: Taesoo Kim
On Die, 2015-03-17 at 19:43 +0530, Arjun Sreedharan wrote:
[...]
> On a related note, IMO strcmp() should return {-1,0,1} since many
> programmers just expect this behavior. just my opinion.
-ENOPATCH.
MfG,
Bernd
--
"I dislike type abstraction if it has no real reason. And saving
on typi
On 2015/3/17 22:33, Rafael J. Wysocki wrote:
> On Tuesday, March 17, 2015 12:10:02 PM Hanjun Guo wrote:
>> On 2015/3/17 11:23, Rafael J. Wysocki wrote:
>>> On Tuesday, March 17, 2015 10:36:47 AM Hanjun Guo wrote:
On 2015/3/17 10:28, Rafael J. Wysocki wrote:
> On Tuesday, March 17, 2015 09:
> -Original Message-
> From: David Rientjes [mailto:rient...@google.com]
> Sent: Wednesday, March 18, 2015 7:02 AM
> To: Wang, Yalin
> Cc: a...@linux-foundation.org; heiko.carst...@de.ibm.com;
> t...@linutronix.de; linux-kernel@vger.kernel.org
> Subject: Re: [RFC] proc: change /proc/stat sh
On 17 March 2015 at 08:22, Ingo Molnar wrote:
>
> * Ian Malone wrote:
>
>> Looks like Ingo Molnar has committed to tip which is probably a good
>> sign, thanks all.
>> (Have to hand this system on to someone who wont be patching kernels...)
>
> Guys, since I don't have the affected hardware, min
On Tue, 2015-03-17 at 15:24 -0400, Johannes Weiner wrote:
> On Tue, Mar 17, 2015 at 10:15:29AM -0700, Linus Torvalds wrote:
> > Explicitly adding the emails of other people involved with that commit
> > and the original oom thread to make sure people are aware, since this
> > didn't get any respons
On Wed, Mar 18, 2015 at 10:37 AM, Rafael J. Wysocki wrote:
> On Tuesday, March 10, 2015 11:07:36 PM Rafael J. Wysocki wrote:
>> Hi,
>>
>> As per the subject, avoid evaluating ACPI_HANDLE() if we can as that one is
>> rather costly.
>
> Linus, Alexandre, any objections to this series?
>
> If not, w
Hi Rusty,
After merging the virtio tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/virtio/virtio_mmio.c:250:12: error: redefinition of 'vm_generation'
static u32 vm_generation(struct virtio_device *vdev)
^
drivers/virtio/virtio_mmio.c:240:12: note: prev
* Linus Walleij [150317 18:31]:
> On Tue, Mar 10, 2015 at 7:33 PM, Nishanth Menon wrote:
> > On 03/10/2015 12:31 PM, Tony Lindgren wrote:
>
> >> Yes except I'd make use of some kind of #pinctrl-cells here just like
> >> interrupt controller has #interrupt-cells. Then you can have the values
> >>
On Tue, Mar 17, 2015 at 6:43 AM, Oleg Nesterov wrote:
> On 03/16, Oleg Nesterov wrote:
>>
>> On 03/16, Andy Lutomirski wrote:
>> >
>> > Ick, you're probably right. For what it's worth, the vdso *seems* to
>> > be okay (on 64-bit only, and only if you don't poke at it too hard) if
>> > you mremap
The value of cxt->record_size does not change in the loop,
so this patch optimize the assign statement by dropping
sz entirely and using cxt->record_size in its place.
Signed-off-by: Wang Long
---
fs/pstore/ram.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/fs/psto
Hi Rusty,
Today's linux-next merge of the virtio tree got a conflict in
net/9p/trans_virtio.c between commit 8051a2a518fc ("9p/trans_virtio:
fix hot-unplug") from Linus' tree and commit 1991755689ad
("9p/trans_virtio: fix hot-unplug") from the virtio tree.
I fixed it up (the latter is an older ve
On Wed, Mar 11, 2015 at 10:15 AM, Linus Walleij
wrote:
> On Tue, Mar 10, 2015 at 6:57 PM, Ray Jui wrote:
>> On 3/10/2015 3:20 AM, Linus Walleij wrote:
>>> On Mon, Mar 9, 2015 at 9:45 PM, Ray Jui wrote:
>>>
This adds the initial support of the Broadcom Cygnus GPIO/PINCONF driver
that su
On Wed, Mar 11, 2015 at 12:05 PM, Thierry Reding
wrote:
> On Fri, Jan 16, 2015 at 09:06:14AM +0800, kbuild test robot wrote:
>> drivers/pwm/pwm-stmpe.c:99:3-8: No need to set .owner here. The core will do
>> it.
>>
>> Remove .owner field if calls are used which set it automatically
>>
>> Generat
Hi
On 2015년 03월 18일 07:40, Jaehoon Chung wrote:
> On 03/17/2015 05:45 PM, Ingi Kim wrote:
>> This patch adds the device tree bindings for ktd2692 flash LEDs.
>> Add optional properties 'flash-timeout-us' to control flash timeout
>> and 'vin-supply' for flash-led regulator
>>
>> Signed-off-by: Ingi
On Tue, Mar 10, 2015 at 11:10 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> In acpi_gpiochip_request_interrupts() the handle local
> variable already contains the value that we want to pass
> to acpi_walk_resources(), so it is better to use that
> variable instead of evaluating ACPI
On 2015/3/18 1:39, Kees Cook wrote:
> On Tue, Mar 17, 2015 at 2:31 AM, Wang Long wrote:
>> The value of cxt->record_size does not change in the loop,
>> so this patch optimize the assign statement by moving
>> it to outer.
>>
>> Signed-off-by: Wang Long
>> ---
>> fs/pstore/ram.c | 4 ++--
>> 1 f
On Thu, Mar 12, 2015 at 8:45 AM, Jacek Anaszewski
wrote:
> Add macros for defining boost mode and trigger type properties
> of flash LED devices.
>
Applied, thanks,
-Bryan
> Signed-off-by: Jacek Anaszewski
> Acked-by: Kyungmin Park
> Cc: Bryan Wu
> Cc: Richard Purdie
> ---
> include/dt-bindi
On Tue, Mar 10, 2015 at 11:08 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> If dev is NULL in __gpiod_get_index() and both ACPI and OF are
> enabled, it will be checked twice before the code decides to give
> up with DT/ACPI lookup, so avoid that.
>
> Also use the observation that A
On Tue, Mar 10, 2015 at 7:33 PM, Nishanth Menon wrote:
> On 03/10/2015 12:31 PM, Tony Lindgren wrote:
>> Yes except I'd make use of some kind of #pinctrl-cells here just like
>> interrupt controller has #interrupt-cells. Then you can have the values
>> seprate and the controller knows what to do
On 2015/3/17 22:29, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> The acpi_suspend() function has no callers, so drop it.
>
> Signed-off-by: Rafael J. Wysocki
Reviewed-by: Hanjun Guo
> ---
> drivers/acpi/sleep.c | 15 ---
> drivers/acpi/sleep.h |2 --
> 2 files chan
MIPS R5, MIPS R6 and MSA HW specs allow a broad range of address exception
on unalaigned MSA load/store operations - from none unaligned up to
full support in HW. In practice, it is expected that HW can occasionally
triggers AdE for non-aligned data access (misalignment). It is usually
expected on
On 03/17/15 04:29, Lorenzo Pieralisi wrote:
> On Mon, Mar 16, 2015 at 10:08:19PM +, Stephen Boyd wrote:
>> On 03/03/15 04:29, Daniel Lezcano wrote:
>>> The code is optimized to use the __init section intensively in order to
>>> reduce
>>> the memory footprint after the driver is initialized an
On Tuesday, March 10, 2015 11:07:36 PM Rafael J. Wysocki wrote:
> Hi,
>
> As per the subject, avoid evaluating ACPI_HANDLE() if we can as that one is
> rather costly.
Linus, Alexandre, any objections to this series?
If not, would there be any problem if I took these to my tree? I'll probably
ha
Hi Jaegeuk,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Wednesday, March 18, 2015 12:58 AM
> To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net
> Cc: Jaegeuk Kim
> Subject: [f2fs-dev] [PATCH 4/4] f2fs:
On Monday, March 16, 2015 09:46:29 PM Peter Huewe wrote:
> This patchset introduces the module_pnp_driver macro which is a
> convenience macro for PNP driver modules similar to module_pci_driver
> and convert the affected drivers to the new helper macro.
> It is intended to be used by drivers which
On Tue, Mar 17, 2015 at 02:02:32PM +0100, Radim Krčmář wrote:
> If EPT was enabled, unrestricted_guest was allowed in L1 regardless of
> L0. L1 triple faulted when running L2 guest that required emulation.
>
> Another side effect was 'WARN_ON_ONCE(vmx->nested.nested_run_pending)'
> in L0's dmesg:
On Tue, Mar 10, 2015 at 4:08 PM, Arnd Bergmann wrote:
> On Friday 20 February 2015 19:01:10 Maxime Coquelin wrote:
>> +/* Pull-Up/Down */
>> +#define NO_PULL0
>> +#define PULL_UP1
>> +#define PULL_DOWN 2
>> +
>> +/* Type */
>> +#define PUSH_PULL (0 << 2)
On Tue, Mar 10, 2015 at 9:34 AM, Nicolas Ferre wrote:
> Le 09/03/2015 17:14, Linus Walleij a écrit :
>> On Sun, Feb 8, 2015 at 7:23 PM, Boris Brezillon
>> wrote:
>>
>>> The gpiochip_lock_as_irq call can fail and return an error, while the
>>> irq_startup is not expected to fail (returns an unsign
On Tue, 17 Mar 2015 12:46:41 + (UTC)
Mathieu Desnoyers wrote:
> > Would that help?
> >
> > this_cpu_write(saved_next, next);
> > rq = context_switch(rq, prev, next);
> > rq->curr = this_cpu_read(saved_next);
>
> Assuming there is a full memory barrier (e.g. load_cr3) within
> c
On Tuesday, March 17, 2015 09:58:58 AM Adrian Hunter wrote:
> The "read array" variants of the device property functions
> can be used to return the number of values in an array.
> Update the comments to reflect that.
>
> Signed-off-by: Adrian Hunter
Looks OK to me.
Greg, any objections?
> ---
Hi Vinod,
Today's linux-next merge of the slave-dma tree got a conflict in
arch/arm/mach-shmobile/board-mackerel.c between commit a521422ea4ae
("ARM: shmobile: mackerel: Remove Legacy C board code") from the
arm-soc tree and commit c078c62a7528 ("mmc: sh_mobile_sdhi: remove
sh_mobile_sdhi_info v2"
Hi Vinod,
Today's linux-next merge of the slave-dma tree got a conflict in
arch/arm/mach-shmobile/board-ape6evm.c between commit 9d07d414d4c3
("ARM: shmobile: r8a73a4: ape6evm: Remove legacy platform") from the
renesas tree and commit c078c62a7528 ("mmc: sh_mobile_sdhi: remove
sh_mobile_sdhi_info
dev_get_regulator() does not exist, fix the typo.
Signed-off-by: Axel Lin
---
include/linux/regulator/driver.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/regulator/driver.h b/include/linux/regulator/driver.h
index d4ad5b5..045f709 100644
--- a/include/linux
On Tuesday, March 17, 2015 04:38:10 PM Nicolas Ferre wrote:
> From: Dan Carpenter
>
> There is a typo here so we deadlock.
>
> Fixes: dd1f1f391dd7 ('rtc: at91rm9200: rework wakeup and interrupt handling')
> Signed-off-by: Dan Carpenter
> Acked-by: Boris Brezillon
> Reported-also-by: David Duec
The mutex lock is not used at all, remove it.
The *vmmc_regulator is not necessary, use a local variable in
stw481x_vmmc_regulator_probe() instead.
Signed-off-by: Axel Lin
Reviewed-by: Linus Walleij
Acked-by: Lee Jones
---
Hi Mark,
Lee prefers this patch to be applied via regulator tree,
so I r
1 - 100 of 928 matches
Mail list logo
