On Mon 12-01-15 12:30:37, Vladimir Davydov wrote:
> Since try_to_free_mem_cgroup_pages() can now call slab shrinkers, we
> should initialize reclaim_state and account reclaimed slab pages in
> scan_control->nr_reclaimed.
I am sorry, I didn't get to this one yet. As pointed out in othere email
Adding new build framework into 'tools/build' to be used
by tools.
There's no change for actual building at this point, it comes
in the next patches.
The idea and more details are explained in the
'tools/build/Documentation/Build' file.
I stole everything from the kernel build system, with some
Commit-ID: 2966d9566beb39c53477c96525820b9415de7a7d
Gitweb: http://git.kernel.org/tip/2966d9566beb39c53477c96525820b9415de7a7d
Author: Jiang Liu
AuthorDate: Wed, 7 Jan 2015 15:31:35 +0800
Committer: Thomas Gleixner
CommitDate: Thu, 15 Jan 2015 11:24:23 +0100
iommu/vt-d: Prepare for
Dmitry Eremin-Solenikov writes:
> Fix the following warning:
>
> WARNING: drivers/clocksource/built-in.o(.text.unlikely+0x70): Section
> mismatch in reference from the function pxa_timer_common_init() to the
> function .init.text:clocksource_mmio_init()
> The function pxa_timer_common_init()
15.01.2015 15:49, Dmitry Osipenko пишет:
CPU1 "resettable" status is already cleared by final suspend function in case
of suspend abortion and by reset handler in case of completed CPU powergate,
no point to do it again.
Signed-off-by: Dmitry Osipenko
---
Eliad Peller writes:
> On Fri, Jan 9, 2015 at 7:03 PM, Kalle Valo wrote:
>> Giel van Schijndel writes:
>>
>>> This highlights the differences (e.g. the bug fixed in the previous
>>> commit).
>>>
>>> Signed-off-by: Giel van Schijndel
>>> ---
>>> drivers/net/wireless/ti/wlcore/acx.c | 22
On Thu, Jan 15, 2015 at 01:58:20PM +0100, Michal Hocko wrote:
> On Thu 15-01-15 11:37:53, Vladimir Davydov wrote:
> > current->reclaim_state is only used to count the number of slab pages
> > reclaimed by shrink_slab(). So instead of initializing it before we are
> >
> > Note that after this
Le 14/01/2015 17:21, Alexandre Belloni a écrit :
> Hi Felipe,
>
> The following series replace the previous series sent by Boris named:
> - [PATCH v5 00/11] memory: add Atmel EBI (External Bus Interface) driver
> - [PATCH 00/11] usb: gadget: at91_udc: Rework for multi-platform support
>
> The
On Thu, Jan 15, 2015 at 12:52:38PM +, Chanwoo Choi wrote:
> On Thu, Jan 15, 2015 at 9:46 PM, Chanwoo Choi wrote:
> > Hi Mark,
> >
> > On Thu, Jan 15, 2015 at 8:29 PM, Mark Rutland wrote:
> >> On Wed, Jan 14, 2015 at 11:57:00PM +, Chanwoo Choi wrote:
> >>> Hi Kukjin,
> >>>
> >>> On
Hi Peter,
On 01/15/2015 01:23 PM, Peter Zijlstra wrote:
On Thu, Jan 15, 2015 at 12:23:43PM +0100, Luca Abeni wrote:
There are some parts of the patch that I do not understand (for example:
if I understand well, if the task is not throttled you set dl_new to 1...
And if it is throttled you
On Thursday 13 November 2014, Jeff Kirsher wrote:
> On Wed, 2014-11-12 at 18:18 -0500, David Miller wrote:
> > From: Ondrej Zary
> > Date: Wed, 12 Nov 2014 23:47:25 +0100
> >
> > > Enabling WoL on some Toshiba laptops (such as Portege R100) causes
> > > battery drain after shutdown (WoL is active
> Hi,
>
> On Sunday 11 January 2015 06:08 PM, Yaniv Gardi wrote:
>> This change adds a support for a 20nm qcom-ufs phy that is required in
>> platforms that use ufs-qcom controller.
>>
>> Signed-off-by: Yaniv Gardi
>>
>> ---
>> drivers/phy/Kconfig | 7 +
>> drivers/phy/Makefile
On Thu, Jan 15, 2015 at 02:06:42PM +0100, Michal Hocko wrote:
> On Thu 15-01-15 13:39:06, Michael S. Tsirkin wrote:
> > Most of our code has
> > struct foo {
> > }
> >
> > Fix two instances where balloon is inconsistent.
>
> I hate to complain but is it really necessary to post such patches to
>
Hi,
On Thu, Jan 15, 2015 at 05:00:37AM +0300, Dmitry Eremin-Solenikov wrote:
> enable_irq_wakeup returns 0 in case it correctly enabled the IRQ to
> generate the wakeup event (and thus resume should call disable_irq_wake).
> Currently gpio-charger driver has this logic inverted. Correct that thus
Hi,
On Thu, Jan 15, 2015 at 05:00:38AM +0300, Dmitry Eremin-Solenikov wrote:
> Teach collie_battery driver to communicate to the kernel that it can
> generate wakeup events. Handle enabling/disabling wakeup on battery full
> event in suspend/resume callbacks.
Thanks, applied:
On Wed, Jan 14, 2015 at 7:55 PM, Daniel Vetter wrote:
> On Tue, Jan 13, 2015 at 05:18:04PM -0500, Stephane Viau wrote:
>> From: Beeresh Gopal
>>
>> This patch implements the hardware accelarated cursor
>> support for MDP5 platforms.
>>
>> Signed-off-by: Beeresh Gopal
>> Signed-off-by: Wentao Xu
Larry Finger writes:
> On 01/10/2015 10:24 AM, Rickard Strandqvist wrote:
>> Removes some functions that are not used anywhere:
>> ex_halbtc8821a1ant_periodical() ex_halbtc8821a1ant_pnp_notify()
>> ex_halbtc8821a1ant_halt_notify() ex_halbtc8821a1ant_bt_info_notify()
>>
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-linus
This fixes a regression in the latest fuse update plus a fix for a rather
theoretical memory ordering issue.
Thanks,
Miklos
---
Miklos Szeredi (2):
fuse: fix LOOKUP vs INIT compat
On Wed, Jan 14, 2015 at 08:58:18PM +, Suman Anna wrote:
> This patch adds the generic common bindings used to represent
> a hwlock device and use/request locks in a device-tree build.
>
> All the platform-specific hwlock driver implementations need the
> number of locks and associated base id
On Thu, Jan 15, 2015 at 01:52:01PM +, Mark Rutland wrote:
> On Wed, Jan 14, 2015 at 08:58:18PM +, Suman Anna wrote:
> > This patch adds the generic common bindings used to represent
> > a hwlock device and use/request locks in a device-tree build.
> >
> > All the platform-specific hwlock
On Thu, 15 Jan 2015 17:10:40 +1100
Michael Ellerman wrote:
> >
> > I don't like setting the swap task flag for syscall tracing, as
> > nothing will unset it.
>
> We could unset it in the unregfunc(), I did that in my original patch
> but took it out because I wasn't sure it was necessary.
Yes
Hi Yamada-san,
Thank you for the patch.
On Thursday 15 January 2015 17:52:40 Masahiro Yamada wrote:
> Signed-off-by: Masahiro Yamada
Acked-by: Laurent Pinchart
> ---
>
> Documentation/devicetree/bindings/gpio/gpio.txt | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff
Commit-ID: 7f530a2771fe7ea6a068340c9e22f814edfcc3c4
Gitweb: http://git.kernel.org/tip/7f530a2771fe7ea6a068340c9e22f814edfcc3c4
Author: Jiang Liu
AuthorDate: Wed, 7 Jan 2015 15:31:32 +0800
Committer: Thomas Gleixner
CommitDate: Thu, 15 Jan 2015 11:24:22 +0100
x86/apic: Kill useless
On Thu, 15 Jan 2015 19:59:36 +0900
Masami Hiramatsu wrote:
> > @@ -3637,6 +3639,7 @@ int
> > register_ftrace_function_probe(char *glob, struct ftrace_probe_ops
> > *ops, void *data)
> > {
> > + struct ftrace_ops_hash old_hash_ops;
>
> Would it be better to be old_ops_hash? since it's not an
dai-link params for codec-codec links were fixed. The fixed
link between codec and another chip which may be another codec,
baseband, bluetooth codec etc may require run time configuaration
changes. This change provides an optional alsa control to select
one of the params from a list of params.
On Thu, Jan 15, 2015 at 2:52 AM, Masahiro Yamada
wrote:
> Signed-off-by: Masahiro Yamada
Perhaps some explanation. You can't just remove properties. Please
explain to what extent the old/wrong name is used. This patch is only
okay if there are no users of gpio-phandle.
Rob
> ---
>
>
On Wed, Jan 14, 2015 at 07:27:03PM +, Mark Brown wrote:
> On Wed, Jan 07, 2015 at 03:31:45PM +0800, Zidan Wang wrote:
>
> > + for (i = 0; i < ARRAY_SIZE(dac_divs); ++i) {
> > + if (wm8960->sysclk == lrclk * dac_divs[i]) {
> > + for (j = 0; j <
Useful for testing device virtio 1 compatibility.
Based on patch by Rusty - couldn't resist putting
that flying car joke in there!
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/virtio_pci_common.h | 10 ++
drivers/virtio/Kconfig | 19 +++
Hi Rob,
On Thursday 15 January 2015 08:07:18 Rob Herring wrote:
> On Thu, Jan 15, 2015 at 2:52 AM, Masahiro Yamada
>
> wrote:
> > Signed-off-by: Masahiro Yamada
>
> Perhaps some explanation. You can't just remove properties. Please
> explain to what extent the old/wrong name is used. This
On Tue, Jan 6, 2015 at 1:59 PM, Arnd Bergmann wrote:
> On Tuesday 06 January 2015 11:20:01 Catalin Marinas wrote:
>> On Mon, Jan 05, 2015 at 08:16:30PM +, Arnd Bergmann wrote:
>> > On Monday 05 January 2015 13:13:02 Catalin Marinas wrote:
>> > > > since passing no DT tables to OS but
>> > > >
On 01/15/2015 02:12 AM, Geert Uytterhoeven wrote:
On Mon, Jan 12, 2015 at 6:59 PM, Guenter Roeck wrote:
Build failures, seen since next-20150109:
m68k:allmodconfig
powerpc:ppc6xx_defconfig
It looks like parisc is also suffering:
The current implementation of the libahci allows using one PHY per
port but we still have one single regulator for the whole
controller. This series adds the support of multiple regulators.
This is the forth version of the series.
The improvement of this version is the use of
Le 12/01/2015 20:26, Boris Brezillon a écrit :
> Hi Alexandre,
>
> On Mon, 12 Jan 2015 19:42:09 +0100
> Alexandre Belloni wrote:
>
>> Hi,
>>
>> This patch set cleans a lot of remaining header, config options and functions
>> that are not used anymore since the switch to DT only.
>>
>> Patch 5
It is now possible to use a regulator property for each port of the
AHCI controller.
Signed-off-by: Gregory CLEMENT
---
Documentation/devicetree/bindings/ata/ahci-platform.txt | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git
Add the regulators to each SATA port.
Signed-off-by: Gregory CLEMENT
---
arch/arm/boot/dts/armada-388-gp.dts | 126
1 file changed, 126 insertions(+)
diff --git a/arch/arm/boot/dts/armada-388-gp.dts
b/arch/arm/boot/dts/armada-388-gp.dts
index
The current implementation of the libahci allows using multiple PHYs
but not multiple regulators. This patch adds the support of multiple
regulators. Until now it was mandatory to have a PHY under a subnode,
now a port subnode can contain either a regulator or a PHY (or both).
In order to be able
The phy_ functions handle the NULL pointer case, so there is no need
to skip them if there is a NULL pointer. Moreover, after the error
label there is already no check on the pointer. This patch removes the
unnecessary tests and brings some consistency.
Signed-off-by: Gregory CLEMENT
Acked-by:
On Thu 15-01-15 15:44:12, Michael S. Tsirkin wrote:
> On Thu, Jan 15, 2015 at 02:06:42PM +0100, Michal Hocko wrote:
> > On Thu 15-01-15 13:39:06, Michael S. Tsirkin wrote:
> > > Most of our code has
> > > struct foo {
> > > }
> > >
> > > Fix two instances where balloon is inconsistent.
> >
> > I
With this patch, a user can define an id for a peer netns by providing a FD or a
PID. These ids are local to the netns where it is added (ie valid only into this
netns).
The main function (ie the one exported to other module), peernet2id(), allows to
get the id of a peer netns. If no id has been
This patch adds a new attribute (IFLA_LINK_NETNSID) which contains the 'link'
netns id when this netns is different from the netns where the interface
stands (for example for x-net interfaces like ip tunnels).
With this attribute, it's possible to interpret correctly all advertised
information
Signed-off-by: Yaowei Bai
---
Documentation/acpi/enumeration.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/acpi/enumeration.txt
b/Documentation/acpi/enumeration.txt
index b60d2ab..9b121a5 100644
--- a/Documentation/acpi/enumeration.txt
+++
Implement rtnl_link_ops->get_link_net() callback so that IFLA_LINK_NETNSID is
added to rtnetlink messages.
Signed-off-by: Nicolas Dichtel
---
drivers/net/vxlan.c | 8
include/net/ip6_tunnel.h | 1 +
include/net/ip_tunnels.h | 1 +
net/ipv4/ip_gre.c| 2 ++
On 15/01/2015 05:25, Michael Ellerman wrote:
> On Mon, 2014-11-24 at 15:07 +0100, Laurent Dufour wrote:
>> On pseries system (LPAR) xmon failed to enter when running in LE mode, system
>> is hunging. Inititating xmon will lead to such an output on the console:
>>
>> SysRq : Entering xmon
>> cpu
The goal of this serie is to be able to multicast netlink messages with an
attribute that identify a peer netns.
This is needed by the userland to interpret some information contained in
netlink messages (like IFLA_LINK value, but also some other attributes in case
of x-netns netdevice (see also
On Thu, 15 Jan 2015 20:57:29 +0900
Masami Hiramatsu wrote:
>
> > If the function tracer traces the jprobe handler, the hook function
> > for that handler will not be called, and its saved return address
> > will be used for the next function. This will result in a kernel
> > crash.
>
>
This patch adds the ability to create a netdevice in a specified netns and
then move it into the final netns. In fact, it allows to have a symetry between
get and set rtnl messages.
Signed-off-by: Nicolas Dichtel
---
net/core/rtnetlink.c | 25 ++---
1 file changed, 22
Thursday, January 15, 2015, 2:04:34 PM, you wrote:
> With more knowledge of Xen interrupt manangement subsytem, I realized
> previous three versions to fix https://lkml.org/lkml/2014/12/19/178 are
> just plainly wrong. Those patches try to fix the issue by creating
> irqdomain for IOAPICs for PV
On Tue, Jan 13, 2015 at 2:42 AM, Jacek Anaszewski
wrote:
> On 01/12/2015 05:55 PM, Rob Herring wrote:
>>
>> Adding Mark B and Liam...
>>
>> On Mon, Jan 12, 2015 at 10:10 AM, Jacek Anaszewski
>> wrote:
>>>
>>> On 01/12/2015 02:52 PM, Rob Herring wrote:
On Mon, Jan 12, 2015 at 2:32
Le 09/01/2015 14:20, Nicolas Ferre a écrit :
> Add a README file to describe Atmel SoCs (aka AT91) support in Mainline Linux:
> - SoC list + datasheet web links
> - Basic but useful information
> - Device Tree conventions and Work In Progress statement.
>
> Signed-off-by: Nicolas Ferre
> Cc: ARM
Changes from V6:
- change#1 in the V6 series: 0001-phy-qcom-ufs-add-support-for-20nm-phy
has been divided into 2 patches:
A: phy: qcom-ufs: add support for QUALCOMM Technologies UFS PHY drivers
B: phy: qcom-ufs: add support for 20nm phy
in order to seperate the common code of the Qualcomm
This change adds support for Qualcomm Technologies Inc platforms that
use UFS driver. for example, it adds :
- PM specific operations during hibern8, suspend, resume, clock setup
- qcom-ufs generic phy driver initialization, calibration,
power-on/off sequence, etc.
- UFS Controller specific
This change adds a support for a 20nm qcom-ufs phy that is required in
platforms that use ufs-qcom controller.
Signed-off-by: Yaniv Gardi
---
drivers/phy/Makefile| 1 +
drivers/phy/phy-qcom-ufs-i.h| 43 +-
drivers/phy/phy-qcom-ufs-qmp-20nm.c | 257
This change adds a support for a 14nm qcom-ufs phy that is
required in platforms that use ufs-qcom controller.
Signed-off-by: Yaniv Gardi
---
drivers/phy/Makefile| 1 +
drivers/phy/phy-qcom-ufs-qmp-14nm.c | 201
From: Yaniv Gardi
In-order to enhance storage encryption performance,
an Inline Cryptographic Engine is introduced to UFS.
This patch adds in-line encryption capabilities to the UFS
driver.
Signed-off-by: Yaniv Gardi
---
drivers/scsi/ufs/Kconfig| 12 +
drivers/scsi/ufs/Makefile
Le 13/01/2015 19:12, Alexandre Belloni a écrit :
> This series enables RTC on the at91sam9n12 and at91rm9200.
> It also adds nodes for the SRAM availabe on at91 SoCs.
>
> Finally it adds a dtsi for the at91sam9xe and uses it for the ethernut5 dts.
>
> Changes in v3:
> - corrected the 9260 and
This change adds a generic and common API support for ufs phy QUALCOMM
Technologies. This support provides common code and also points
to specific phy callbacks to differentiate between different behaviors
of frequent use-cases (like power on, power off, phy calibration etc).
Signed-off-by: Yaniv
On 2015/1/15 22:22, Sander Eikelenboom wrote:
>
> Thursday, January 15, 2015, 2:04:34 PM, you wrote:
>
>> With more knowledge of Xen interrupt manangement subsytem, I realized
>> previous three versions to fix https://lkml.org/lkml/2014/12/19/178 are
>> just plainly wrong. Those patches try to
On Thu, Jan 15, 2015 at 6:33 AM, Sylwester Nawrocki
wrote:
> On 12/01/15 18:06, Mark Brown wrote:
>> On Mon, Jan 12, 2015 at 10:55:29AM -0600, Rob Herring wrote:
>>> > On Mon, Jan 12, 2015 at 10:10 AM, Jacek Anaszewski
> > There are however devices that don't fall into this category, i.e.
Hi,
On Thu, Jan 15, 2015 at 08:36:44AM +0100, Dr. H. Nikolaus Schaller wrote:
> > 1. Perform conversion in input core rather than individual drivers. I
> > think we should allocate a new bitmaps for some transformations and have
> > the code do X/Y flip/clip of the coordinates.
>
> Do you have a
On Thu, Jan 15, 2015 at 7:55 AM, Mark Rutland wrote:
> On Thu, Jan 15, 2015 at 01:52:01PM +, Mark Rutland wrote:
>> On Wed, Jan 14, 2015 at 08:58:18PM +, Suman Anna wrote:
>> > This patch adds the generic common bindings used to represent
>> > a hwlock device and use/request locks in a
From: Sergey Popov < popov_ser...@ukr.net >
Prevent increase of console_loglevel by 'quiet'
'quiet' kernel option that follows the 'loglevel=N' should
not blindly overwrite console_loglevel, instead it should
respect and keep lower 'loglevel'.
Signed-off-by: Sergey Popov < popov_ser...@ukr.net
On 01/15/2015 04:42 AM, Michal Simek wrote:
.owner files is filled by module_platform_driver().
Signed-off-by: Michal Simek
---
Reviewed-by: Guenter Roeck
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On Thu 15-01-15 16:25:16, Vladimir Davydov wrote:
> On Thu, Jan 15, 2015 at 01:58:20PM +0100, Michal Hocko wrote:
> > On Thu 15-01-15 11:37:53, Vladimir Davydov wrote:
> > > current->reclaim_state is only used to count the number of slab pages
> > > reclaimed by shrink_slab(). So instead of
Introduce __KVM_HAVE_ARCH_INTC_INITIALIZED define and
associated kvm_arch_intc_initialized function. This latter
allows to test whether the virtual interrupt controller is initialized
and ready to accept virtual IRQ injection. On some architectures,
the virtual interrupt controller is dynamically
On arm/arm64 the VGIC is dynamically instantiated and it is useful
to expose its state, especially for irqfd setup.
This patch defines __KVM_HAVE_ARCH_INTC_INITIALIZED and
implements kvm_arch_intc_initialized.
Signed-off-by: Eric Auger
Acked-by: Christoffer Dall
---
v6 -> v7:
- usage of the
This patch enables irqfd on arm/arm64.
Both irqfd and resamplefd are supported. Injection is implemented
in vgic.c without routing.
This patch enables CONFIG_HAVE_KVM_EVENTFD and CONFIG_HAVE_KVM_IRQFD.
KVM_CAP_IRQFD is now advertised. KVM_CAP_IRQFD_RESAMPLE capability
automatically is
CONFIG_HAVE_KVM_IRQCHIP is needed to support IRQ routing (along
with irq_comm.c and irqchip.c usage). This is not the case for
arm/arm64 currently.
This patch unsets the flag for both arm and arm64.
Signed-off-by: Eric Auger
Acked-by: Christoffer Dall
Acked-by: Will Deacon
---
This patch series enables irqfd on arm and arm64.
Irqfd framework enables to inject a virtual IRQ into a guest upon an
eventfd trigger. User-side uses KVM_IRQFD VM ioctl to provide KVM with
a kvm_irqfd struct that associates a VM, an eventfd, a virtual IRQ number
(aka. the gsi). When an actor
On 01/15/2015 04:42 AM, Michal Simek wrote:
.owner files is filled by module_platform_driver().
Signed-off-by: Michal Simek
---
Big cleanup was done and this new driver was missed.
Actually, it was included in 'watchdog: drop owner assignment from
platform_drivers'
by Wolfram Sang. It just
On Thu, 2015-01-15 at 14:40 +0100, Ondrej Zary wrote:
> On Thursday 13 November 2014, Jeff Kirsher wrote:
> > On Wed, 2014-11-12 at 18:18 -0500, David Miller wrote:
> > > From: Ondrej Zary
> > > Date: Wed, 12 Nov 2014 23:47:25 +0100
> > >
> > > > Enabling WoL on some Toshiba laptops (such as
No functional changes.
Signed-off-by: Michal Simek
---
drivers/tty/serial/8250/8250_core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/tty/serial/8250/8250_core.c
b/drivers/tty/serial/8250/8250_core.c
index 11c66856ba2f..65e52c9109e2 100644
---
This patch remove unnecessary KERN_INFO in time.c
Signed-off-by: Masanari Iida
---
arch/openrisc/kernel/time.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/arch/openrisc/kernel/time.c b/arch/openrisc/kernel/time.c
index 7c52e94..3b50ffd 100644
---
This patch should be the part of:
"tty: serial: 8250_core: use the ->line argument as a hint in
serial8250_find_match_or_unused()"
(sha1: 59b3e898ddfc81a65975043b5eb44103cc29ff6e)
port->line can be setup by DT driver to -1 which needs to
be also checked.
Signed-off-by: Michal Simek
---
I have
Move at91rm9200_idle() along with at91sam9_idle() in clk/at91/pmc.c.
Signed-off-by: Alexandre Belloni
Acked-by: Michael Turquette
---
arch/arm/mach-at91/at91rm9200.c | 9 -
arch/arm/mach-at91/generic.h| 1 +
drivers/clk/at91/pmc.c | 9 +
3 files changed, 10
Check UDP and UHP on sam9x5, sam9n12 and the sama5 series.
Check UHP on the sam9g45.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.c | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/arch/arm/mach-at91/pm.c b/arch/arm/mach-at91/pm.c
index
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/sama5d4.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mach-at91/sama5d4.c b/arch/arm/mach-at91/sama5d4.c
index 7638509639f4..fa127fb79221 100644
--- a/arch/arm/mach-at91/sama5d4.c
+++ b/arch/arm/mach-at91/sama5d4.c
@@ -56,7
SRAM initialization is now done through the mmio-sram driver and
at91_init_sram() is not called anymore, remove it.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/generic.h | 2 --
arch/arm/mach-at91/setup.c | 20
2 files changed, 22 deletions(-)
diff --git
Split at91_pm_init() in three variants that are called by the respective SoCs
.init_machine. This allows to remove the of_machine_is_compatible() calls and
move at91_pm_init() out of arch_initcall() which is required for multiplatform.
Signed-off-by: Alexandre Belloni
---
Store SoC differences in a struct to remove cpu_is_* usage.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.c | 54 ++---
1 file changed, 33 insertions(+), 21 deletions(-)
diff --git a/arch/arm/mach-at91/pm.c b/arch/arm/mach-at91/pm.c
Now that the SRAM is initialized by the mmio-sram driver, .map_io is useless.
remove it.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/at91rm9200.c | 6 --
arch/arm/mach-at91/at91sam9260.c | 27 ---
arch/arm/mach-at91/at91sam9261.c | 9 -
Reviewed-by: Dov Levenglick
Dov Levenglick
QUALCOMM ISRAEL, on behalf of Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a
Linux Foundation Collaborative Project
> -Original Message-
> From: linux-scsi-ow...@vger.kernel.org
Now that the SRAM is part of a genpool, use it to allocate memory to use for the
slowclock implementation.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/Kconfig | 1 +
arch/arm/mach-at91/pm.c| 46 +-
2 files changed, 46 insertions(+), 1
This patch sets is based on AT91 cleanup for 3.20 #1
and depends on AT91 DT for 3.20 #1 because it uses the added SRAM nodes.
The first two patches rework the pm code to get rid of cpu_is_xxx (they will be
dropped soon) and use the SRAM from the genpool instead of relying on the remap
done by
Hi,
Am 15.01.2015 um 15:38 schrieb Sebastian Reichel :
> Hi,
>
> On Thu, Jan 15, 2015 at 08:36:44AM +0100, Dr. H. Nikolaus Schaller wrote:
>>> 1. Perform conversion in input core rather than individual drivers. I
>>> think we should allocate a new bitmaps for some transformations and have
>>>
From: Sergey Popov
Prevent increase of console_loglevel by 'quiet'
'quiet' kernel option that follows the 'loglevel=N' should
not blindly overwrite console_loglevel, instead it should
respect and keep lower 'loglevel'.
Signed-off-by: Sergey Popov
---
init/main.c | 7 ++-
1 file changed,
[Adding a few people to CC that have expressed interest in the
progress of the updates of this page, or who may be able to
provide review feedback. Eventually, you'll all get CCed on
the new draft of the page.]
Hello Thomas,
On 05/15/2014 04:14 PM, Thomas Gleixner wrote:
> On Thu, 15 May 2014,
Hello Darren,
I give you the same apology as to Thomas for the
long-delayed response to your mail.
And I repeat my note to Thomas:
In the next day or two, I hope to send out the new version
of the futex(2) page for review. The new draft is a bit
bigger (okay -- 4 x bigger) than the current
Reviewed-by: Dov Levenglick
> This change adds a generic and common API support for ufs phy QUALCOMM
> Technologies. This support provides common code and also points
> to specific phy callbacks to differentiate between different behaviors
> of frequent use-cases (like power on, power off, phy
Reviewed-by: Dov Levenglick
> This change adds a support for a 20nm qcom-ufs phy that is required in
> platforms that use ufs-qcom controller.
>
> Signed-off-by: Yaniv Gardi
>
> ---
> drivers/phy/Makefile| 1 +
> drivers/phy/phy-qcom-ufs-i.h| 43 +-
>
Reviewed-by: Dov Levenglick
> This change adds a support for a 14nm qcom-ufs phy that is
> required in platforms that use ufs-qcom controller.
>
> Signed-off-by: Yaniv Gardi
>
> ---
> drivers/phy/Makefile| 1 +
> drivers/phy/phy-qcom-ufs-qmp-14nm.c | 201
>
Reviewed-by: Dov Levenglick
> This change adds a support for a 20nm qcom-ufs phy that is required in
> platforms that use ufs-qcom controller.
>
> Signed-off-by: Yaniv Gardi
>
> ---
> drivers/phy/Makefile| 1 +
> drivers/phy/phy-qcom-ufs-i.h| 43 +-
>
On Thursday 15 January 2015, Jeff Kirsher wrote:
> On Thu, 2015-01-15 at 14:40 +0100, Ondrej Zary wrote:
> > On Thursday 13 November 2014, Jeff Kirsher wrote:
> > > On Wed, 2014-11-12 at 18:18 -0500, David Miller wrote:
> > > > From: Ondrej Zary
> > > > Date: Wed, 12 Nov 2014 23:47:25 +0100
> > >
Namjae Jeon writes:
> We introduce per-file freeze feature for unifying defrag ext4 and xfs
> as first ingredient. We get the idea courtesy of Dave Chinner
> (https://lkml.org/lkml/2014/7/14/759)
> per-file freeze will be used to avoid that file is not modified while
> userspace is doing the
Reviewed-by: Dov Levenglick
> This change adds support for Qualcomm Technologies Inc platforms that
> use UFS driver. for example, it adds :
> - PM specific operations during hibern8, suspend, resume, clock setup
> - qcom-ufs generic phy driver initialization, calibration,
> power-on/off
Reviewed-by: Dov Levenglick
> From: Yaniv Gardi
>
> In-order to enhance storage encryption performance,
> an Inline Cryptographic Engine is introduced to UFS.
> This patch adds in-line encryption capabilities to the UFS
> driver.
>
> Signed-off-by: Yaniv Gardi
>
> ---
>
cpumask_next_and() does cpumask_next() src1 in a loop and tests if found
cpu is alsop present in src2. remove that loop and perform cpumask_and()
of src1 and src2 first and use to find cpumask_next() intead.
Signed-off-by: Sergey Senozhatsky
---
lib/cpumask.c | 9 +
1 file changed, 5
On Jan 15, 2015 4:37 AM, "Masami Hiramatsu"
wrote:
>
> (2015/01/14 6:49), Andy Lutomirski wrote:
> > x86 instructions cannot exceed 15 bytes, and the instruction decoder
> > should enforce that. Prior to 6ba48ff46f76, the instruction length
> > limit was implicitly set to 16, which was an
On 12 January 2015 at 10:23, Krzysztof Kozlowski
wrote:
> Hi,
>
>
> I would like to hear some comments about idea of scaling MMC clock
> frequency. The basic idea is to lower the clock when device is
> completely idle or not busy enough.
>
> The patchset adds MMC card as a devfreq device and uses
From: "Steven Rostedt (Red Hat)"
Commit 5f893b2639b2 "tracing: Move enabling tracepoints to just after
rcu_init()" broke the enabling of system call events from the command
line. The reason was that the enabling of command line trace events
was moved before PID 1 started, and the syscall
Linus,
This holds a few fixes to the ftrace infrastructure as well as
the mixture of function graph tracing and kprobes.
When jprobes and function graph tracing is enabled at the same time
it will crash the system.
# modprobe jprobe_example
# echo function_graph >
1201 - 1300 of 1820 matches
Mail list logo
