Commit-ID: cf910e83ae23692fdeefc7e506e504c4c468d38a
Gitweb: http://git.kernel.org/tip/cf910e83ae23692fdeefc7e506e504c4c468d38a
Author: Seiji Aguchi
AuthorDate: Thu, 20 Jun 2013 11:46:53 -0400
Committer: H. Peter Anvin
CommitDate: Thu, 20 Jun 2013 22:25:34 -0700
x86, trace: Add irq
Commit-ID: eddc0e922a3530e0f22cef170229bcae3a7d5e31
Gitweb: http://git.kernel.org/tip/eddc0e922a3530e0f22cef170229bcae3a7d5e31
Author: Seiji Aguchi
AuthorDate: Thu, 20 Jun 2013 11:45:17 -0400
Committer: H. Peter Anvin
CommitDate: Thu, 20 Jun 2013 22:25:01 -0700
x86, trace: Introduce
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in
arch/arm/boot/dts/sun4i-a10.dtsi between commit b21da664120b ("ARM:
sun4i: Add muxing options for the ethernet controller") from the net-next
tree and commit 27cce4ff34ec ("ARM: sun4i: dt: Add i2c muxing options")
from the
Commit-ID: 629f4f9d59a27d8e58aa612e886e6a9a63ea7aeb
Gitweb: http://git.kernel.org/tip/629f4f9d59a27d8e58aa612e886e6a9a63ea7aeb
Author: Seiji Aguchi
AuthorDate: Thu, 20 Jun 2013 11:45:44 -0400
Committer: H. Peter Anvin
CommitDate: Thu, 20 Jun 2013 22:25:13 -0700
x86: Rename variables
Commit-ID: f5abaa1bfc3dbf26d19d3513f39279ca369f8d65
Gitweb: http://git.kernel.org/tip/f5abaa1bfc3dbf26d19d3513f39279ca369f8d65
Author: Steven Rostedt
AuthorDate: Thu, 20 Jun 2013 11:44:44 -0400
Committer: H. Peter Anvin
CommitDate: Thu, 20 Jun 2013 22:24:32 -0700
tracing: Add
This patch series adds support for the dedicated cs pin and
support for exynos5440 spi controller. The first patch
"Polling support for s3c64xx spi controller" in the previous
serias is already applied to Mark's spi-next branch. So created
a new series with remaining 2 patches.
Girish K S (2):
From: Girish K S
The existing driver supports gpio based /cs signal.
For controller's that have one device per controller,
the slave device's /cs signal might be internally controlled
by the chip select bit of slave select register. They are not
externally asserted/deasserted using gpio pin.
From: Girish K S
This patch adds support for the exynos5440 spi controller.
The integration of the spi IP in exynos5440 is different from
other SoC's. The I/O pins are no more configured via gpio, they
have dedicated pins.
Signed-off-by: Girish K S
---
drivers/spi/spi-s3c64xx.c | 12
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in
arch/arm/boot/dts/am33xx.dtsi between commit a82279dd6d3e ("arm: am33xx:
add TSC/ADC mfd device support") from the mfd tree and commit
15e8246bd61b ("ARM: dts: AM33XX: Add ELM node") from the arm-soc tree.
I fixed it up (see
On Thu, Jun 20, 2013 at 5:09 PM, Stephen Rothwell wrote:
> I noticed that the infiniband tree is now based on the net-next tree. I
> assume that is deliberate? I do have to question how much testing that
> tree has had since it is now based on a tree that Dave only released in
> the last 24
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in
arch/arm/boot/dts/am335x-evmsk.dts between commit f6655d697b85 ("ARM:
dts: AM33XX: Add CPSW phy_id device tree data to am335x-evmsk") from the
net-next tree and commit 94a924ca61f0 ("ARM: dts: AM33XX: Add pinmux
configuration
> On 06/20/2013 01:14 AM, Jay Agarwal wrote:
> > - decrease non-prefetch memory size to 128 MB
> > - increase prefetch memory size to 384 MB
> > - above change is done because most pcie devices
> > prefetch memory size requirement is quite higher
> > compared to non-prefetch memory space.
>
>
On 06/21/2013 06:01 AM, Eric W. Biederman wrote:
> Gao feng writes:
>
>> On 06/20/2013 11:02 AM, Gao feng wrote:
>>> If we don't tie audit to user namespace, there is still one problem.
>>
>> One more problem. some audit messages are generated by some net subsystem
>> such as netfilter. If we
On 06/13/2013 06:02 AM, Tang Chen wrote:
> From: Yinghai Lu
>
> No offence, just rebase and resend the patches from Yinghai to help
> to push this functionality faster.
> Also improve the comments in the patches' log.
>
So we need a new version of this which addresses the build problems and
On Thu, Jun 20, 2013 at 1:13 AM, Eduardo Valentin
wrote:
> On 19-06-2013 15:35, Eduardo Valentin wrote:
>> Rui,
>>
>> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
>>> This code splits the exynos tmu driver code into SOC specific data parts.
>>> This will simplify adding new SOC specific data
An awful lot of drivers, mostly DRI drivers, are still mucking with
MTRRs directly as opposed to using ioremap_wc() or similar interfaces.
In addition to the architecture dependency, this is really undesirable
because MTRRs are a limited resource, whereas page table attributes are not.
On 6/21/2013 8:51 AM, Jingoo Han wrote:
diff --git a/drivers/pci/host/pci-designware.c
b/drivers/pci/host/pci-designware.c
new file mode 100644
index 000..f8558ff
--- /dev/null
+++ b/drivers/pci/host/pci-designware.c
If you plan to send next version, then I would suggest to rename it as
On 금, 2013-06-14 at 13:20 +0900, Namjae Jeon wrote:
> 2013/6/11, Namjae Jeon :
> > 2013/6/11, Changman Lee :
> >> On 화, 2013-06-11 at 07:57 +0900, Namjae Jeon wrote:
> >>> 2013/6/10, Changman Lee :
> >>> > Hello, Namjae
> >>> Hi. Changman.
> >>> >
> >>> > If using ACL, whenever i_mode is changed
On Friday, June 21, 2013 1:23 PM, Pratyush Anand wrote:
> On 6/21/2013 8:51 AM, Jingoo Han wrote:
> > diff --git a/drivers/pci/host/pci-designware.c
> > b/drivers/pci/host/pci-designware.c
> > new file mode 100644
> > index 000..f8558ff
> > --- /dev/null
> > +++
Hi Santosh,
On 06/21/2013 06:22 AM, Santosh Shilimkar wrote:
> Cc: Vineet Gupta
> Cc: Russell King
> Cc: Catalin Marinas
> Cc: Will Deacon
> Cc: Mark Salter
> Cc: Aurelien Jacquiot
> Cc: James Hogan
> Cc: Michal Simek
> Cc: Ralf Baechle
> Cc: Jonas Bonn
> Cc: Benjamin Herrenschmidt
>
On Thu, Jun 20, 2013 at 12:50 AM, Eduardo Valentin
wrote:
> On 19-06-2013 15:18, Eduardo Valentin wrote:
>> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
>>> This patch renames and moves include/linux/platform_data/exynos_thermal.h to
>>> drivers/thermal/samsung/exynos_tmu.h. This file movement
Commit-ID: f037e416afb38b9ee8ac598d68733fcbaf665384
Gitweb: http://git.kernel.org/tip/f037e416afb38b9ee8ac598d68733fcbaf665384
Author: H. Peter Anvin
AuthorDate: Thu, 20 Jun 2013 21:16:00 -0700
Committer: H. Peter Anvin
CommitDate: Thu, 20 Jun 2013 21:30:04 -0700
x86, reloc: Use xorl
When using --strict, CamelCase uses are described
with CHECK: messages. These CamelCase uses may
be acceptable and should not generate these messages
when the variable is already defined in a file from
the include/... path.
So, change checkpatch to read all the .h files in
include/... and look
Hi
On Thu, Jun 20, 2013 at 12:48 AM, Eduardo Valentin
wrote:
> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
>> This patch renames and moves include/linux/platform_data/exynos_thermal.h to
>> drivers/thermal/samsung/exynos_tmu.h. This file movement is needed as exynos
>> SOC's are not
On 06/20/2013 03:54:42 AM, Hanjun Guo wrote:
More than 256 entries in ACPI MADT is supported from ACPI 3.0
Specification,
So the outdated description for MADT entries should be removed.
Signed-off-by: Hanjun Guo
---
Documentation/cpu-hotplug.txt |3 ---
1 file changed, 3 deletions(-)
On Friday, June 21, 2013 1:11 PM, Sachin Kamat wrote:
>
> Hi Jingoo,
>
> Some small corrections inline.
>
> On 21 June 2013 08:51, Jingoo Han wrote:
> > Exynos5440 has a PCIe controller which can be used as Root Complex.
> > This driver supports a PCIe controller as Root Complex mode.
> >
> >
(2013/06/21 3:31), Tom Zanussi wrote:
> diff --git a/include/trace/ftrace.h b/include/trace/ftrace.h
> index 88ac7da..7c5627f 100644
> --- a/include/trace/ftrace.h
> +++ b/include/trace/ftrace.h
> @@ -522,14 +522,6 @@ ftrace_raw_event_##call(void *__data, proto)
> \
>
Hi Jingoo,
Some small corrections inline.
On 21 June 2013 08:51, Jingoo Han wrote:
> Exynos5440 has a PCIe controller which can be used as Root Complex.
> This driver supports a PCIe controller as Root Complex mode.
>
> Signed-off-by: Surendranath Gurivireddy Balla
> Signed-off-by: Siva Reddy
On Thu, Jun 20, 2013 at 1:33 AM, Eduardo Valentin
wrote:
> On 02-05-2013 06:18, Amit Daniel Kachhap wrote:
>> TMU probe function now checks for a device tree defined regulator.
>> For compatibility reasons it is allowed to probe driver even without
>> this regulator defined.
>>
>> Signed-off-by:
On 06/21/2013 12:42 AM, Viresh Kumar wrote:
> On 20 June 2013 16:48, Chanwoo Choi wrote:
>> But,
>> To show old frequency/new frequency on load_table debugfs file,
>> governor function(dbs_check_cpu()) pass calculated CPUs load to specific
>> governor(e.g., ondemand)
>> as below function flow.
On 06/19/2013 04:09:18 PM, Paul Clements wrote:
Currently, when a disconnect is requested by the user (via
NBD_DISCONNECT
ioctl) the return from NBD_DO_IT is undefined (it is usually one of
several error codes). This means that nbd-client does not know if a
manual disconnect was performed or
On 06/19/2013 11:23:51 AM, Li Wang wrote:
This patch implements punch hole (fallocate) support for Ceph.
Signed-off-by: Li Wang
Signed-off-by: Yunchuan Wen
+static int ceph_delete_object(struct inode *inode, u64 offset, u64
*length)
+{
+ struct ceph_inode_info *ci =
On Thu, Jun 20, 2013 at 11:17:39AM +0200, Fabio Baltieri wrote:
> Fix sparse warnings:
>
> drivers/dma/ste_dma40.c:81:26: warning: symbol 'dma40_memcpy_conf_phy' was
> not declared. Should it be static?
> drivers/dma/ste_dma40.c:95:26: warning: symbol 'dma40_memcpy_conf_log' was
> not declared.
On 06/20/2013 09:02 PM, Eric Paris wrote:
> On Thu, 2013-06-20 at 11:02 +0800, Gao feng wrote:
>> On 06/20/2013 04:51 AM, Eric Paris wrote:
>>> On Wed, 2013-06-19 at 16:49 -0400, Aristeu Rozanski wrote:
On Wed, Jun 19, 2013 at 09:53:32AM +0800, Gao feng wrote:
> This patchset is first
Bing,
On Tue, Jun 18, 2013 at 1:01 PM, Bing Zhao wrote:
> Hi Doug,
>
>> > I tested Doug's patch on my failing unit.
>> >
>> > Without this patch, mmc got hung_task and rebooted eventually.
>> > With this patch applied, mmc returns CRC error instead of hung_task, and
>> > the error is handled
>>
This patch adds pcie controller node for exynos5440-ssdk5440,
and also adds a phandle for pin controller node.
Signed-off-by: Jingoo Han
Acked-by: Arnd Bergmann
---
arch/arm/boot/dts/exynos5440-ssdk5440.dts |8
arch/arm/boot/dts/exynos5440.dtsi |2 +-
2 files changed,
Exynos5440 has two PCIe controllers which can be used as root complex
for PCIe interface.
Signed-off-by: Jingoo Han
Acked-by: Arnd Bergmann
---
arch/arm/boot/dts/exynos5440.dtsi | 38 +
1 file changed, 38 insertions(+)
diff --git
Enable PCIe support for Exynos5440 which has two PCIe controllers.
Signed-off-by: Jingoo Han
---
arch/arm/Kconfig |1 +
arch/arm/mach-exynos/Kconfig |2 ++
2 files changed, 3 insertions(+)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index ca30d75..421ce68 100644
---
Exynos5440 has a PCIe controller which can be used as Root Complex.
This driver supports a PCIe controller as Root Complex mode.
Signed-off-by: Surendranath Gurivireddy Balla
Signed-off-by: Siva Reddy Kallam
Signed-off-by: Jingoo Han
Acked-by: Arnd Bergmann
---
On Thu, Jun 20, 2013 at 09:43:52AM +0200, Nicolas Ferre wrote:
> On 19/06/2013 13:14, Boris BREZILLON :
> >Replace clk_enable/disable with clk_prepare_enable/disable_unprepare to
> >avoid common clk framework warnings.
> >
> >Signed-off-by: Boris BREZILLON
>
> Acked-by: Nicolas Ferre
>
> BTW
Hi,
This series of patches introduces PCIe support for Samsung Exynos5440,
and is based on the latest 'linux-next' tree (20130620).
These patches was tested with Intel e1000e LAN card on Exynos5440.
This PATCH v9 follows:
* PATCH v8, sent on June, 20th 2013
* PATCH v7, sent on June, 20th 2013
On Fri, 2013-06-21 at 04:50 +0200, Hans J. Koch wrote:
> Does each little driver really need a MAINTAINERS entry?
Hi Hans.
I think a lot of those driver MAINTAINERS entries are
maybe a little useful when the driver is just written
but are progressively less useful after a few months.
I once
With this change dm-verity errors will cause uevents to be
sent to userspace, notifying it that an error has occurred
and potentially triggering recovery actions.
Signed-off-by: Geremy Condra
---
Changelog since v1:
- Removed the DM_VERITY_ERROR_NOTIFY config option
drivers/md/dm-uevent.c | 40
On Thu, Jun 20, 2013 at 6:30 PM, Alasdair G Kergon wrote:
> On Thu, Jun 20, 2013 at 06:12:07PM -0700, Geremy Condra wrote:
>> Assuming nobody currently using DM_UEVENT minds it doesn't cause any
>> problems for me. Any current users object?
>
> DM_UEVENT toggles uevents on or off across the whole
Morten,
On Thu, Jun 20, 2013 at 6:23 PM, Morten Rasmussen
wrote:
> On Sat, Jun 15, 2013 at 01:09:12PM +0100, Lei Wen wrote:
>> On Fri, Jun 14, 2013 at 9:59 PM, Alex Shi wrote:
>> > On 06/14/2013 06:02 PM, Lei Wen wrote:
>> >>> > enqueue_entity
>> >>> >
Signed-off-by: Alexey Kardashevskiy
---
Documentation/vfio.txt |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/vfio.txt b/Documentation/vfio.txt
index c55533c..d7993dc 100644
--- a/Documentation/vfio.txt
+++ b/Documentation/vfio.txt
@@ -172,12 +172,12
Alex,
On Fri, Jun 21, 2013 at 10:39 AM, Alex Shi wrote:
> On 06/21/2013 10:30 AM, Lei Wen wrote:
>> Hi Alex,
>>
>> On Thu, Jun 20, 2013 at 10:59 PM, Alex Shi wrote:
>>> On 06/20/2013 10:46 AM, Lei Wen wrote:
But here I have a question, there is another usage of
On Thu, Jun 20, 2013 at 09:20:27AM -0700, Joe Perches wrote:
> On Thu, 2013-06-20 at 18:01 +0200, Pavel Machek wrote:
> > Anyway, Hans disappeared, so Greg takes patches, again.
I wasn't able to take part in kernel development because I was heavily
involved in hardware development project. I
On Thu, Jun 20, 2013 at 12:31 AM, Eduardo Valentin
wrote:
> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
>> This code bifurcates exynos thermal implementation into common and sensor
>> specific parts. The common thermal code interacts with core thermal layer and
>> core cpufreq cooling parts
From: Wei Yongjun
Fix to return -ENOMEM in the create_singlethread_workqueue() error handling
case instead of 0, as done elsewhere in this function.
Introduced by commit a3299ab18591d36ad5622f5064619123c439b779.
(rsxx: Individual workqueues for interruptible events.)
Signed-off-by: Wei Yongjun
On 06/21/2013 10:30 AM, Lei Wen wrote:
> Hi Alex,
>
> On Thu, Jun 20, 2013 at 10:59 PM, Alex Shi wrote:
>> On 06/20/2013 10:46 AM, Lei Wen wrote:
>>>
>>>
>>> But here I have a question, there is another usage of
>>> __synchronzie_entity_decay
>>> in current kernel, in the switched_from_fair
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
drivers/net/ethernet/freescale/fec_main.c between commit d13919301d9a
("net: fec: Fix build for MCF5272") from the net tree and commit
32bc9b46d840 ("fec: Add support to restart autonegotiate") from the
net-next tree.
I
Hi Alex,
On Thu, Jun 20, 2013 at 10:59 PM, Alex Shi wrote:
> On 06/20/2013 10:46 AM, Lei Wen wrote:
>>
>>
>> But here I have a question, there is another usage of
>> __synchronzie_entity_decay
>> in current kernel, in the switched_from_fair function.
>>
>> If task being frequently switched
(2013/06/21 3:42), Steven Rostedt wrote:
> On Thu, 2013-06-20 at 19:37 +0200, Oleg Nesterov wrote:
>> Steven,
>>
>> Please consider this series for inclusion. It doesn't depend on
>> other changes we are discussing.
>>
>> Only cosmetic changes since v1, everything was acked by Masami.
>>
>
>
>
On 2013-6-21 3:52, Rafael J. Wysocki wrote:
> On Thursday, June 20, 2013 04:54:42 PM Hanjun Guo wrote:
>> More than 256 entries in ACPI MADT is supported from ACPI 3.0 Specification,
>> So the outdated description for MADT entries should be removed.
>
> Well, it kind of is still valid for systems
Firstly, I guess:
since you can spend your time resource to reply, that means "you also
think this patch is valuable, but the comments need improving"
Is it correct ?
On 06/20/2013 09:42 PM, Thomas Gleixner wrote:
> On Thu, 20 Jun 2013, Chen Gang wrote:
>
> kernel/itimer.c: beautify code,
Hi Eduardo,
On Thu, Jun 20, 2013 at 1:25 AM, Eduardo Valentin
wrote:
> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
>> This patch adds some extra register bitfield definations and cleans
>> up the code to prepare for moving register macros and definations inside
>> the TMU data section.
>>
>>
On Thu, Jun 20, 2013 at 06:46:41PM -0700, Guenter Roeck wrote:
> On Fri, Jun 21, 2013 at 11:21:01AM +1000, Michael Ellerman wrote:
> >
> > On Wed, 2013-06-19 at 16:24 -0700, Guenter Roeck wrote:
> > > On Wed, Jun 19, 2013 at 03:15:19PM -0700, Greg Kroah-Hartman wrote:
> > > > On Wed, Jun 19, 2013
On Thu, Jun 20, 2013 at 12:15 AM, Eduardo Valentin
wrote:
> Amit,
>
> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
>> This code bifurcates exynos thermal implementation into common and sensor
>> specific parts. The common thermal code interacts with core thermal layer and
>> core cpufreq
> -Original Message-
> From: linux-arm-kernel [mailto:linux-arm-kernel-boun...@lists.infradead.org]
> On Behalf Of Boris BREZILLON
> Sent: 2013年6月11日 18:51
> To: Wim Van Sebroeck; Jean-Christophe Plagniol-Villard; Ferre, Nicolas;
> linux-watch...@vger.kernel.org
> Cc:
On Tue, Jun 18, 2013 at 11:16:17AM +0200, Linus Walleij wrote:
> On Mon, Jun 17, 2013 at 7:14 PM, Stephen Boyd wrote:
> > On 06/16/13 22:54, Linus Walleij wrote:
> >> On Tue, Jun 4, 2013 at 9:20 PM, Stephen Boyd wrote:
> >>
> >>> Commit 7bce696 (gpio: Make gpio-msm-v1 into a platform driver,
>
On Fri, Jun 21, 2013 at 11:21:01AM +1000, Michael Ellerman wrote:
>
> On Wed, 2013-06-19 at 16:24 -0700, Guenter Roeck wrote:
> > On Wed, Jun 19, 2013 at 03:15:19PM -0700, Greg Kroah-Hartman wrote:
> > > On Wed, Jun 19, 2013 at 01:43:48PM -0700, Guenter Roeck wrote:
> > > > On Wed, Jun 19, 2013
> -Original Message-
> From: linux-arm-kernel [mailto:linux-arm-kernel-boun...@lists.infradead.org]
> On Behalf Of Boris BREZILLON
> Sent: 2013年6月11日 18:51
> To: Wim Van Sebroeck; Jean-Christophe Plagniol-Villard; Ferre, Nicolas
> Cc: Boris BREZILLON; Russell King;
> -Original Message-
> From: linux-arm-kernel [mailto:linux-arm-kernel-boun...@lists.infradead.org]
> On Behalf Of Boris BREZILLON
> Sent: 2013年6月11日 18:51
> To: Wim Van Sebroeck; Jean-Christophe Plagniol-Villard; Ferre, Nicolas
> Cc: linux-watch...@vger.kernel.org;
On 06/18, Stephen Boyd wrote:
> This patchset allows me to compile and run the DT based MSM
> platforms in the multi-platform ARM kernel. This is built on
> top of a couple patches I've sent out already (specifically
> the debug_ll patch series and the clocksource_of conversion)
> as well a patch
On Thu, Jun 20, 2013 at 01:46:59PM -0400, Paul Gortmaker wrote:
>
> The below pseudo-pull-request will show the scope of changes against
> the linux-next tree from today. It is a real branch that people
> can pull and build/test against if they are interested in doing so.
> Or, just pull the
On Thu, Jun 20, 2013 at 06:12:07PM -0700, Geremy Condra wrote:
> Assuming nobody currently using DM_UEVENT minds it doesn't cause any
> problems for me. Any current users object?
DM_UEVENT toggles uevents on or off across the whole of device-mapper.
If there is no particular need for verity
On 06/17, Stephen Boyd wrote:
> Resending to collect higher level maintainer acks per Olof's request.
> The plan is to push this patchset through MSM to the arm-soc tree.
>
> This patchset moves the existing MSM clock code and affected drivers to the
> common clock framework. A prerequisite of
correct for irq. irq number is get by gludriver, while irq is
requested by EHCO HCD.
On Fri, Jun 21, 2013 at 9:07 AM, Chao Xie wrote:
> On Fri, Jun 21, 2013 at 1:25 AM, Alan Stern wrote:
>> On Thu, 20 Jun 2013, Felipe Balbi wrote:
>>
>>> > In fact, the PHY setting and handling is related to
Note: this patch must be ordered _after_ "fs/fs-writeback.c: make
wb_do_writeback() as static" to avoid build errors.
After commit 839a8e86("writeback: replace custom worker pool implementation
with unbound workqueue"), bdi_writeback_workfn runs off bdi_writeback->dwork,
on each execution, it
Changelog:
v4 -> v5:
* indent the comment
After commit 839a8e86("writeback: replace custom worker pool implementation
with unbound workqueue"), there is no bdi forker thread any more. However,
WB_REASON_FORKER_THREAD is still used due to it is TPs userland visible
and we won't be exposing
wb_reason_name is not used any more, this patch remove it.
Reviewed-by: Tejun Heo
Reviewed-by: Fengguang Wu
Signed-off-by: Wanpeng Li
---
include/linux/writeback.h |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/include/linux/writeback.h b/include/linux/writeback.h
The default zonelist order selecter will select "node" order if any node's
DMA zone comprises greater than 70% of its local memory instead of 60%,
according to default_zonelist_order::low_kmem_size > total * 70/100.
Reviewed-by: Michal Hocko
Signed-off-by: Wanpeng Li
---
On 06/20/2013 08:55 PM, Thomas Gleixner wrote:
> On Thu, 20 Jun 2013, Chen Gang wrote:
>
>> >
>> > Oh, sorry, maybe it is a trivial patch, also need send to
>> > triv...@kernel.org.
> No. This is not a trivial patch, it's changing the code flow.
>
OK, that is not a trivial patch, but a minor
The old codes accumulate addr to get right pmd, however,
currently pmds are preallocated and transfered as a parameter,
there is unnecessary to accumulate addr variable any more, this
patch remove it.
Reviewed-by: Michal Hocko
Reviewed-by: Zhang Yanfei
Signed-off-by: Wanpeng Li
---
Transparent huge zero page is used during the page fault instead of
in khugepaged.
# ls /sys/kernel/mm/transparent_hugepage/
defrag enabled khugepaged use_zero_page
# ls /sys/kernel/mm/transparent_hugepage/khugepaged/
alloc_sleep_millisecs defrag full_scans max_ptes_none pages_collapsed
On Wed, 2013-06-19 at 16:24 -0700, Guenter Roeck wrote:
> On Wed, Jun 19, 2013 at 03:15:19PM -0700, Greg Kroah-Hartman wrote:
> > On Wed, Jun 19, 2013 at 01:43:48PM -0700, Guenter Roeck wrote:
> > > On Wed, Jun 19, 2013 at 10:42:36AM -0300, Fabio Estevam wrote:
> > > > Hi Guenter,
> > > >
> > >
On 06/20/2013 09:17 PM, Zhang Yanfei wrote:
On 06/20/2013 06:10 PM, Tang Chen wrote:
pageblock_nr_page should be pageblock_nr_pages, and fist is
a typo of first.
Signed-off-by: Tang Chen
---
mm/page_isolation.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git
On Fri, Jun 21, 2013 at 1:25 AM, Alan Stern wrote:
> On Thu, 20 Jun 2013, Felipe Balbi wrote:
>
>> > In fact, the PHY setting and handling is related to platform or SOC,
>> > and for different SOC they can
>> > have same EHCI HCD but they PHY handling can be different.
>> > Omap'a case is the
Andrey Wagin writes:
> On Tue, Jun 18, 2013 at 02:56:51AM +0400, Andrey Wagin wrote:
>> 2013/6/17 Eric W. Biederman :
>> > So for anyone seriously worried about this kind of thing in general we
>> > already have the memory control group, which is quite capable of
>> > limiting this kind of
On Thu, Jun 20, 2013 at 02:21:00PM -0700, Geremy Condra wrote:
> With this change and config option, dm-verity errors
> will cause uevents to be sent to userspace, notifying
> it that an error has occurred and potentially
> triggering recovery actions.
> +config DM_VERITY_ERROR_NOTIFY
> +
After commit 839a8e86("writeback: replace custom worker pool implementation
with unbound workqueue"), bdi_writeback_workfn runs off bdi_writeback->dwork,
on each execution, it processes bdi->work_list and reschedules if there are
more things to do instead of flush any work that race with us
The old codes accumulate addr to get right pmd, however,
currently pmds are preallocated and transfered as a parameter,
there is unnecessary to accumulate addr variable any more, this
patch remove it.
Reviewed-by: Michal Hocko
Reviewed-by: Zhang Yanfei
Signed-off-by: Wanpeng Li
---
wb_reason_name is not used any more, this patch remove it.
Reviewed-by: Tejun Heo
Reviewed-by: Fengguang Wu
Signed-off-by: Wanpeng Li
---
include/linux/writeback.h |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/include/linux/writeback.h b/include/linux/writeback.h
Transparent huge zero page is used during the page fault instead of
in khugepaged.
# ls /sys/kernel/mm/transparent_hugepage/
defrag enabled khugepaged use_zero_page
# ls /sys/kernel/mm/transparent_hugepage/khugepaged/
alloc_sleep_millisecs defrag full_scans max_ptes_none pages_collapsed
The default zonelist order selecter will select "node" order if any node's
DMA zone comprises greater than 70% of its local memory instead of 60%,
according to default_zonelist_order::low_kmem_size > total * 70/100.
Reviewed-by: Michal Hocko
Signed-off-by: Wanpeng Li
---
Changelog:
v4 -> v5:
* indent the comment
After commit 839a8e86("writeback: replace custom worker pool implementation
with unbound workqueue"), there is no bdi forker thread any more. However,
WB_REASON_FORKER_THREAD is still used due to it is TPs userland visible
and we won't be exposing
On some PAE architectures, the entire range of physical memory could reside
outside the 32-bit limit. These systems need the ability to specify the
initrd location using 64-bit numbers.
This patch globally modifies the early_init_dt_setup_initrd_arch() function to
use 64-bit numbers instead of
Hi Linus,
This series fixes a couple of build failures, and fixes MTRR cleanup
and memory setup on very specific memory maps. Finally, it fixes
triggering backtraces on all CPUs, which was inadvertently disabled on
x86.
The following changes since commit
On 06/20/2013 07:02 PM, Sergei Shtylyov wrote:
> Hello.
Hi,
Thanks for your comments.
>
> On 20-06-2013 6:26, Aaron Lu wrote:
>>
>> +void ata_acpi_hotplug_init(struct ata_host *host)
>> +{
>> +int i;
>> +
>> +for (i = 0; i < host->n_ports; i++) {
>> +struct ata_port *ap =
Commit-ID: 4a90a99c4f8002edaa6be11bd756872ebf3f3d97
Gitweb: http://git.kernel.org/tip/4a90a99c4f8002edaa6be11bd756872ebf3f3d97
Author: Borislav Petkov
AuthorDate: Sun, 9 Jun 2013 12:07:33 +0200
Committer: H. Peter Anvin
CommitDate: Thu, 20 Jun 2013 17:38:14 -0700
x86: Add a
On 06/21/2013 06:51 AM, Daniel Baluta wrote:
> On Thu, Jun 20, 2013 at 7:59 PM, Zhang Yanfei
> wrote:
>> On 06/20/2013 11:12 PM, Ghennadi Procopciuc wrote:
>>> Inserting the following kernel module:
>>>
>>>
>>>
>>> static int simple_test_init(void)
>>> {
>>> size_t i, j;
>>>
Commit-ID: 5700f743b597951743da9c7d891d3989aac0486e
Gitweb: http://git.kernel.org/tip/5700f743b597951743da9c7d891d3989aac0486e
Author: Borislav Petkov
AuthorDate: Sun, 9 Jun 2013 12:07:32 +0200
Committer: H. Peter Anvin
CommitDate: Thu, 20 Jun 2013 17:37:19 -0700
x86: Sanity-check
Commit-ID: c3b83598c1eeb1507603b461f5843ec2a49e3033
Gitweb: http://git.kernel.org/tip/c3b83598c1eeb1507603b461f5843ec2a49e3033
Author: Borislav Petkov
AuthorDate: Sun, 9 Jun 2013 12:07:30 +0200
Committer: H. Peter Anvin
CommitDate: Thu, 20 Jun 2013 17:06:07 -0700
x86, cpu: Add a
Commit-ID: 5f8c4218148822fde6eebbeefc34bd0a6061e031
Gitweb: http://git.kernel.org/tip/5f8c4218148822fde6eebbeefc34bd0a6061e031
Author: Borislav Petkov
AuthorDate: Sun, 9 Jun 2013 12:07:34 +0200
Committer: H. Peter Anvin
CommitDate: Thu, 20 Jun 2013 17:38:22 -0700
x86, fpu: Use
When using --strict, CamelCase uses are described
with CHECK: messages. These CamelCase uses may
be acceptable and should not generate these messages
when the variable is already defined in a file from
the include/... path.
So, change checkpatch to read all the .h files in
include/... and look
> --- a/include/linux/writeback.h
> +++ b/include/linux/writeback.h
> @@ -47,6 +47,12 @@ enum wb_reason {
> WB_REASON_LAPTOP_TIMER,
> WB_REASON_FREE_MORE_MEM,
> WB_REASON_FS_FREE_SPACE,
> + /*
> + * There is no bdi forker thread any more and works are done
> + * by
Hi Andy,
On 06/17/2013 11:43 PM, Andy Shevchenko wrote:
It seems there is no user of the wp_gpio driver in the kernel. Let's remove it.
I never liked this wp code there too.
Signed-off-by: Andy Shevchenko
Acked-by: Mika Westerberg
Acked-by: David Cohen
--
To unsubscribe from this
On Fri, Jun 21, 2013 at 08:28:49AM +0800, Wanpeng Li wrote:
> wb_reason_name is not used any more, this patch remove it.
>
> Reviewed-by: Tejun Heo
> Signed-off-by: Wanpeng Li
Reviewed-by: Fengguang Wu
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
This series adds Device Tree support for Samsung S3C64xx SoC series.
It fixes several problems preventing from booting an S3C64xx-based system
using Device Tree, adds all the infrastructure for Device Tree-based board
support, including mach-s3c64xx-dt and dts include files for S3C64xx SoCs,
and
1 - 100 of 1526 matches
Mail list logo
