On Sun 03-02-13 20:29:01, Hugh Dickins wrote:
> Whilst I run the risk of a flogging for disloyalty to the Lord of Sealand,
> I do have CONFIG_MEMCG=y CONFIG_MEMCG_KMEM not set, and grow tired of the
> "mm/memcontrol.c:4972:12: warning: `memcg_propagate_kmem' defined but not
> used [-Wunused-functio
Support new model RTS5227.
Signed-off-by: Roger Tseng
Reviewed-by: Wei WANG
---
drivers/mfd/Makefile | 2 +-
drivers/mfd/rts5227.c| 234 +++
drivers/mfd/rtsx_pcr.c | 5 +
drivers/mfd/rtsx_pcr.h | 1 +
include/linux/mfd/rt
Implement different ways of selecting driving capability(a necessary adjustment
along with voltage change). It was origionally in device-independent
mmc/host/rtsx_pci_sdmmc.c. Moving it here to support devices which may have a
different way of adjustment.
Signed-off-by: Roger Tseng
Reviewed-by: W
The patchset makes necessary changes in mfd and mmc tree for supporting RTS5227
card reader.
Roger Tseng (3):
MMC: rtsx: remove driving adjustment
mfd: rtsx: implement driving adjustment to device-dependent callbacks
mfd: rtsx: support RTS5227
drivers/mfd/Makefile | 2 +-
dr
Several new models of readers use different way to select driving
capability(a necessary adjustment along with voltage change). Removing this
from device-independent rtsx_pci_sdmmc module. It will be implemented in
device-depend calls encapsulated by rtsx_pci_switch_output_voltage().
Signed-off-by
On 01/02/13 19:25, Stephen Warren wrote:
> On 02/01/2013 10:27 AM, Stephen Warren wrote:
>> On 02/01/2013 09:51 AM, Rob Herring wrote:
>>> On 02/01/2013 03:01 AM, Srinivas KANDAGATLA wrote:
Hi Stephen,
Not sure if you have already noticed this but,
I did try this patch on my 3.8, and
Hi all,
Changes since 20130202:
The powerpc tree still had a build failure.
The nfsd tree still had its build failure so I used the version from
next-20130128.
The security tree gained a conflict against Linus' tree.
The tip tree lost its build failure.
The xen-two tree gained a build failure
On Mon, 2013-02-04 at 08:46 +0900, Minchan Kim wrote:
> Lockdep complains about recursive deadlock of zram->init_lock.
> [1] made it false positive because we can't request IO to zram
> before setting disksize. Anyway, we should shut lockdep up to
> avoid many reporting from user.
>
> [1] : zram:
On Wed, 2013-01-30 at 10:03 +0800, Huang Shijie wrote:
> The panic_nand_wait() expects the timeo in ms and not in jiffies.
> But in nand_wait(), the timeo for panic_nand_wait() is assigned with
> wrong value(jiffies + some delay). The timeo should be set like the
> panic_nand_write() does.
>
> Thi
On 02/04/2013 08:29 AM, Hugh Dickins wrote:
> Whilst I run the risk of a flogging for disloyalty to the Lord of Sealand,
> I do have CONFIG_MEMCG=y CONFIG_MEMCG_KMEM not set, and grow tired of the
> "mm/memcontrol.c:4972:12: warning: `memcg_propagate_kmem' defined but not
> used [-Wunused-function]
Hi Minchan,
On Mon, 2013-02-04 at 08:46 +0900, Minchan Kim wrote:
> Now zram document syas "set disksize is optional"
> but partly it's wrong. When you try to use zram firstly after
> booting, you must set disksize, otherwise zram can't work because
> zram gendisk's size is 0. But once you do it, y
On Sun, Feb 03, 2013 at 09:37:16PM +0100, Stephane Eranian wrote:
> On Tue, Jan 29, 2013 at 9:03 AM, Ingo Molnar wrote:
> >
> > * Stephane Eranian wrote:
> >
> >> On Mon, Jan 28, 2013 at 9:52 PM, Stephane Eranian
> >> wrote:
SNIP
> Adding the option for users to link with libpfm4 was no big
>
Andrew suggested I make the nr_pages argument an unsigned long rather
than just a long. I was initially worried that nr_pages would be compared
with signed longs, but this isn't the case, so his suggestion is perfectly
valid.
Sending as a 'fix' change, to be collapsed with the original in -mm.
Si
These 3 changes are to improve the handling of large mm_populate and
munlock operations. They apply on top of mmotm (in particular, they
depend on both my prior mm_populate work and Kirill's "thp: avoid
dumping huge zero page" change).
- Patch 1 fixes an integer overflow issue when populating 2^32
Hi Andrew,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/mm/init_64.c: In function 'remove_pmd_table':
arch/x86/mm/init_64.c:921:3: error: implicit declaration of function
'map_low_page' [-Werror=implicit-function-declaration]
arch/x86/mm/
munlock_vma_pages_range() was always incrementing addresses by PAGE_SIZE
at a time. When munlocking THP pages (or the huge zero page), this resulted
in taking the mm->page_table_lock 512 times in a row.
We can do better by making use of the page_mask returned by follow_page_mask
(for the huge zero
This change adds a follow_page_mask function which is equivalent to
follow_page, but with an extra page_mask argument.
follow_page_mask sets *page_mask to HPAGE_PMD_NR - 1 when it encounters a
THP page, and to 0 in other cases.
__get_user_pages() makes use of this in order to accelerate populatin
From: fangxiaozhi
1. Optimize the match rules with new macro for Huawei USB storage devices,
to avoid to load USB storage driver for the modem interface
with Huawei devices.
2. Add to support new switch command for new Huawei USB dongles.
Signed-off-by: fangxiaozhi
-
From: fangxiaozhi
1. Define a new macro for USB storage match rules:
matching with Vendor ID and interface descriptors.
Signed-off-by: fangxiaozhi
diff -uprN linux-3.8-rc6_orig/drivers/usb/storage/usb.c
linux-3.8-rc6/dr
On Friday 01 February 2013 03:48 PM, Peter De Schrijver wrote:
Signed-off-by: Peter De Schrijver
---
Reviewed-by: Prashant Gaikwad
drivers/clk/tegra/clk.c |1 +
drivers/clk/tegra/clk.h |7 +++
2 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/drivers/clk/tegra/c
i915 driver needs to do modeset when
1. system resumes from sleep
2. lid is opened
In PM_SUSPEND_MEM state, all the GPEs are cleared when system resumes,
thus it is the i915_resume code does the modeset rather than intel_lid_notify().
But in PM_SUSPEND_FREEZE state, this will be broken because
sy
Enable ACPI SCI during suspend so that SCI can be used
as wake events for PM_SUSPEND_FREEZE.
For S3/S4 transition,
We disable all GPEs in suspend_ops->prepare_late() to
fix a problem that GPEs may trigger SCI before
arch_suspend_disable_irqs() is run.
So it is safe to leave the SCI enabled until
PM_SUSPEND_FREEZE state is a general state that
does not need any platform specific support, it equals
frozen processes + suspended devices + idle processors.
Compared with PM_SUSPEND_MEMORY,
PM_SUSPEND_FREEZE saves less power
because the system is still in a running state.
PM_SUSPEND_FREEZE has l
On Friday 01 February 2013 03:48 PM, Peter De Schrijver wrote:
Implement most clocks for Tegra114. The super clocks for the CPU complex
are still missing and will be implemented in a future version.
Signed-off-by: Peter De Schrijver
---
drivers/clk/tegra/Makefile |1 +
drivers/clk/
Just a quick update: the previously posted patch *does* work;
the crash I was experiencing was pilot error.
My NTP server is running a 3.8.0-rc6-dirty kernel right now.
I'll research whether that race I talk about in pps_tty_dcd_change
is actually possible or not (can interrupts start arriving be
> +/**
> + * ticket_commit - commit a reservation with a new fence
> + * @ticket:[in]the reservation_ticket returned by
> + * ticket_reserve
> + * @entries: [in]a linked list of struct reservation_entry
> + * @fence: [in]the fence that indicates completion
> + *
> + * This fun
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
arch/x86/mm/numa.c between commit 07f4207a305c ("x86-32, mm: Remove
reference to alloc_remap()") from the tip tree and commit "x86: get
pg_data_t's memory from other node" from the akpm tree.
I fixed it up (see below) and can
* Ingo Molnar wrote:
>
> * Yinghai Lu wrote:
>
> > Please check attached.
>
> Almost good.
>
> This:
>
> > When some HP sytems boot without x2apic_phys, there will be
>
> Should mention the approximate models of the systems affected - is it
> just a specific line of systems, or a wider r
On 4 February 2013 05:19, Amit Daniel Kachhap wrote:
> This device tree support is added for PMIC block of S5m8767 multi
> function driver. The usage detail is added in the device tree
> documentation section. This change is tested on exynos5250 based
> arndale platform by regulator voltage set/ge
On Friday 01 February 2013 03:48 PM, Peter De Schrijver wrote:
Add references to tegra_car clocks for the basic device nodes.
Signed-off-by: Peter De Schrijver
---
Reviewed-by: Prashant Gaikwad
arch/arm/boot/dts/tegra114.dtsi |7 ++-
1 files changed, 6 insertions(+), 1 deletions
2013/2/4 13:56, Michael Ellerman:
On Mon, 2013-02-04 at 11:49 +0800, Mike Qiu wrote:
On Tue, 2013-01-15 at 15:38 +0800, Mike Qiu wrote:
Currently, multiple MSI feature hasn't been enabled in pSeries,
These patches try to enbale this feature.
Hi Mike,
These patches have been tested by using i
Signed-off-by: HATAYAMA Daisuke
---
arch/s390/kernel/setup.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/s390/kernel/setup.c b/arch/s390/kernel/setup.c
index a5360de..3357566 100644
--- a/arch/s390/kernel/setup.c
+++ b/arch/s390/kernel/setup.c
@@ -729,9 +729,
Signed-off-by: HATAYAMA Daisuke
---
drivers/char/mem.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/char/mem.c b/drivers/char/mem.c
index c6fa3bc..5da737c 100644
--- a/drivers/char/mem.c
+++ b/drivers/char/mem.c
@@ -369,7 +369,7 @@ static ssize_t read_oldmem(
Signed-off-by: HATAYAMA Daisuke
---
arch/mips/kernel/crash_dump.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/mips/kernel/crash_dump.c b/arch/mips/kernel/crash_dump.c
index 35bed0d..6621211 100644
--- a/arch/mips/kernel/crash_dump.c
+++ b/arch/mips/kernel/crash
Signed-off-by: HATAYAMA Daisuke
---
arch/powerpc/kernel/crash_dump.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/kernel/crash_dump.c b/arch/powerpc/kernel/crash_dump.c
index b3ba516..fa64170 100644
--- a/arch/powerpc/kernel/crash_dump.c
+++ b/arch/power
# I emailed to Vivek at old email address so resend. Please reply to
# this RESEND patch series. Sorry for this noise...
First, there are two kinds of notation to represent a map: inclusive
and exclusive. Here are the examples:
1) [mem 0x0001-0x00013fff]
2) [mem
>
>
> -Original Message-
> From: Abhilash Kesavan [mailto:kesavan.abhil...@gmail.com]
> Sent: Monday, February 04, 2013 12:48 AM
> To: myungjoo@samsung.com; linux-kernel@vger.kernel.org;
linux...@vger.kernel.org; kgene@samsung.com
> Cc: kyungmin.p...@samsung.com; r...@sisk.pl; jh
On Friday 01 February 2013 03:48 PM, Peter De Schrijver wrote:
Workaround a hardware bug in MSENC during clock enable.
Signed-off-by: Peter De Schrijver
---
drivers/clk/tegra/clk-periph-gate.c |9 +
drivers/clk/tegra/clk.h |1 +
2 files changed, 10 insertions(+),
Hi Wei,
> -Original Message-
> From: linux-pm-ow...@vger.kernel.org [mailto:linux-pm-
> ow...@vger.kernel.org] On Behalf Of Wei Ni
> Sent: Monday, February 04, 2013 11:10 AM
> To: R, Durgadoss
> Cc: Zhang, Rui; linux...@vger.kernel.org; linux-kernel@vger.kernel.org;
> eduardo.valen...@ti.c
Hi Al,
Today's linux-next merge of the signal tree got a conflict in
arch/mips/kernel/syscall.c between commit 7034228792cc ("MIPS: Whitespace
cleanup") from the mips tree and commit 50150d2bb903 ("mips: switch to
generic sys_fork() and sys_clone()") from the signal tree.
I fixed it up (the sys_c
On Saturday 02 February 2013 01:10 AM, Rhyland Klein wrote:
On 2/1/2013 5:18 AM, Peter De Schrijver wrote:
Tegra114 introduces new PLL types. This requires new clocktypes as well
as some new fields in the pll structure.
Signed-off-by: Peter De Schrijver
---
drivers/clk/tegra/clk-pll.c | 71
On Friday 01 February 2013 03:48 PM, Peter De Schrijver wrote:
We will need some tegra peripheral clocks with the CLK_IGNORE_UNUSED flag,
most notably mselect, which is a bridge between AXI and most peripherals.
Signed-off-by: Peter De Schrijver
---
Looks good to me.
Reviewed-by: Prashant Ga
On Friday 01 February 2013 03:48 PM, Peter De Schrijver wrote:
Some PLLs in Tegra114 don't use a power of 2 mapping for the post divider.
Introduce a table based approach and switch PLLU to it.
Signed-off-by: Peter De Schrijver
---
Looks good to me.
Reviewed-by: Prashant Gaikwad
drivers
On Tue, 2013-01-29 at 11:10 +0100, Daniel Vetter wrote:
> On Mon, Jan 28, 2013 at 06:06:38PM +0800, Zhang Rui wrote:
> > On Mon, 2013-01-28 at 09:31 +0100, Daniel Vetter wrote:
> > > On Mon, Jan 28, 2013 at 3:36 AM, Zhang Rui wrote:
> > > >> Given that this essentially requires users to manually s
Signed-off-by: HATAYAMA Daisuke
---
arch/s390/kernel/setup.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/s390/kernel/setup.c b/arch/s390/kernel/setup.c
index a5360de..3357566 100644
--- a/arch/s390/kernel/setup.c
+++ b/arch/s390/kernel/setup.c
@@ -729,9 +729,
First, there are two kinds of notation to represent a map: inclusive
and exclusive. Here are the examples:
1) [mem 0x0001-0x00013fff]
2) [mem 0x0001-0x00014000]
1) is inclusive and 2) is exclusive. In case of 1), the pfn calculated
from the en
Convert tmpfs do_shmem_file_read() to shmem_file_read_iter().
Make file_read_iter_actor() global so tmpfs can use it too: delete
file_read_actor(), which was made global in 2.4.4 for use by tmpfs.
Replace tmpfs generic_file_aio_write() by generic_file_write_iter().
Signed-off-by: Hugh Dickins
---
On Friday 01 February 2013 03:48 PM, Peter De Schrijver wrote:
Not all PLLs in Tegra114 have a bypass bit. Adapt the common code to only use
this bit when available.
Signed-off-by: Peter De Schrijver
---
Looks good to me.
Reviewed-by: Prashant Gaikwad
drivers/clk/tegra/clk-pll.c | 15
Cong Wang writes:
> Hello, Rusty, Jesse,
>
> I met an interesting problem when I compile openvswitch module as a
> built-in (actually I compile ALL kernel modules as built-in), there is
> no /sys/module/openvswitch/ directory created by the kernel in this
> case.
...
> What's worse, the user-space
On Friday 01 February 2013 03:48 PM, Peter De Schrijver wrote:
Refactor the PLL programming code to make it useable by the new PLL types
introduced by Tegra114.
The following changes were done:
* Split programming the PLL into updating m,n,p and updating cpcon
* Move locking from _update_pll_cp
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in
drivers/mfd/db8500-prcmu.c between commit 5073e7b57041 ("mfd:
db8500-prcmu: Add ux500_wdt mfd_cell") from the mfd tree and commit
520f7bd73354 ("irqchip: Move ARM gic.h to
include/linux/irqchip/arm-gic.h") from the arm-soc tree
On Mon, 2013-02-04 at 11:49 +0800, Mike Qiu wrote:
> > On Tue, 2013-01-15 at 15:38 +0800, Mike Qiu wrote:
> > > Currently, multiple MSI feature hasn't been enabled in pSeries,
> > > These patches try to enbale this feature.
> > Hi Mike,
> >
> > > These patches have been tested by using ipr driver,
On Sun, Feb 3, 2013 at 3:07 PM, Ric Mason wrote:
> Hi Konrad,
> On Fri, 2013-02-01 at 15:22 -0500, Konrad Rzeszutek Wilk wrote:
>> From: Dan Magenheimer
>>
>> With the goal of allowing tmem backends (zcache, ramster, Xen tmem) to be
>> built/loaded as modules rather than built-in and enabled by a
boot_cpu_data is ok for things that are indeed universally valid across. That
does not include CPUID level, for one.
Borislav Petkov wrote:
>On Sun, Feb 03, 2013 at 03:44:29PM -0800, H. Peter Anvin wrote:
>> On 02/03/2013 08:14 AM, Borislav Petkov wrote:
>> >From: Borislav Petkov
>> >
>> >We
On Friday, February 01, 2013 11:42 PM, Anatolij Gustschin wrote
CC'ed Andrew Morton
>
> From: Stefano Babic
>
> Add LCD driver for Ilitek ILI9221/ILI9222 controller.
>
> Signed-off-by: Stefano Babic
> Signed-off-by: Anatolij Gustschin
> Cc: Richard Purdie
> Cc: Florian Tobias Schandinat
>
Hi Linus,
Today's linux-next merge of the pinctrl tree got a conflict in
include/linux/mfd/abx500/ab8500.h between commit 0ed5107fa860
("ab8500-charger: Do not touch VBUSOVV bits") from the battery tree and
commit 56813f798e8c ("mfd: ab8500: update header file and version
detection") from the pinc
On 01/07/2013 03:13 PM, Durgadoss R wrote:
> This patch set is a v2 of the previous versions submitted here:
> [v1]: https://lkml.org/lkml/2012/12/18/108
> [RFC]: https://patchwork.kernel.org/patch/1758921/
>
> This patch set is based on Rui's -thermal tree, and is
> tested on a Core-i5 and an A
On Sun, Feb 3, 2013 at 9:05 PM, Al Viro wrote:
> On Sun, Feb 03, 2013 at 08:52:18PM -0800, H?vard Skinnemoen wrote:
>
>> You're right on -- in this case, the compiler will skip r10, and do
>> (r12, r11, r8:r9, stack). We pass the syscall number in r8, but we
>> also unconditionally move r7 to r8 i
On 2/3/2013 6:15 PM, Sekhar Nori wrote:
> On 1/28/2013 7:17 PM, Prabhakar Lad wrote:
>> From: Lad, Prabhakar
> There are couple of issues with this implementation.
>
> 1) da8xx_config_emac() is specific to DA850 EVM, but masquerades as
>generic for da8xx. Looks like you need two functions, o
On Sun, Feb 03, 2013 at 03:44:29PM -0800, H. Peter Anvin wrote:
> On 02/03/2013 08:14 AM, Borislav Petkov wrote:
> >From: Borislav Petkov
> >
> >We copy it to boot_cpu_data anyway so use boot_cpu_data from the get-go.
> >
>
> Hmm... this is the only part of this patchset I feel skeptical
> toward
Hi Greg,
On 1 February 2013 15:37, Sachin Kamat wrote:
> Use the newly introduced devm_ioremap_resource() instead of
> devm_request_and_ioremap() which provides more consistent error handling.
>
> devm_ioremap_resource() provides its own error messages; so all explicit
> error messages can be rem
Hi all,
Today's linux-next merge of the char-misc tree got a conflict in
drivers/mfd/wm5102-tables.c between commit d078377faf5f ("mfd: wm5102:
Refresh register defaults") from the mfd tree and commit 689557d3c704
("mfd: wm5102: Add microphone clamp control registers") from the
char-misc tree.
I
On Wed, 30 Jan 2013, Shaohua Li wrote:
> On Sun, Jan 27, 2013 at 01:40:40PM -0800, Hugh Dickins wrote:
> >
> > I'm glad Minchan has now pointed you to Rik's posting of two years ago:
> > I think there are more important changes to be made in that direction.
>
> Not sure how others use multiple sw
Hi,
similar to what I reported earlier [0] for 3.8.0-rc1, this happens during
"ifup wlan0" (which in effect starts wpa_supplicant to bring up a Broadcom
b43 wifi network interface). The interface is working though and continues
to work over several ifup/ifdown iterations.
The backtrace looks a
Sekhar ,
On Sun, Feb 3, 2013 at 5:33 PM, Sekhar Nori wrote:
> On 1/28/2013 7:17 PM, Prabhakar Lad wrote:
>> From: Lad, Prabhakar
>>
>> Add eth0 device tree node information and pinmux for mii to da850 by
>> providing interrupt details and local mac address of eth0.
>>
>> Signed-off-by: Lad, Prab
On Sun, Feb 03, 2013 at 08:52:18PM -0800, H?vard Skinnemoen wrote:
> You're right on -- in this case, the compiler will skip r10, and do
> (r12, r11, r8:r9, stack). We pass the syscall number in r8, but we
> also unconditionally move r7 to r8 in the syscall path, so it
> shouldn't matter (libc doe
Sekhar ,
On Sun, Feb 3, 2013 at 6:15 PM, Sekhar Nori wrote:
> On 1/28/2013 7:17 PM, Prabhakar Lad wrote:
>> From: Lad, Prabhakar
>>
>> The system configuration chip CFGCHIP3, controls the emac module.
>> This patch appropriately configures this register for emac and
>> sets DA850_MII_MDIO_CLKEN_
Support mmap() on /dev/oldmem to improve performance of reading
/proc/vmcore. Currently, read to /proc/vmcore is done by read_oldmem()
that uses ioremap and iounmap per a single page; for example, if
memory is 1GB, ioremap/iounmap is called (1GB / 4KB)-times, that is,
262144 times. This causes big
On Mon, Feb 04, 2013 at 03:38:31PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the driver-core tree got a conflict in
> drivers/net/wan/Kconfig between commit a786a7c0ad44 ("wanrouter: completely
> decouple obsolete code from kernel") from the net-next tree and comm
On 02/03/2013 08:04 PM, Cliff Wickman wrote:
From: Cliff Wickman
The crash kernel is not able to find its root device if that device is not
on PCI 0.
This is because it is booted with the command line option memmap=exactmap
which currently clears the e820 table. So ACPI processing does not
fi
On Sun, Feb 3, 2013 at 7:02 PM, Al Viro wrote:
> On Mon, Feb 04, 2013 at 01:31:11AM +, Al Viro wrote:
>
>> Unless I'm misreading ocavr32.pdf, that should be (R12, R10:R11, R9, R8) and
>> (R12, R10:R11, R9:R8, stack) resp., so fadvise64 doesn't need a wrapper, but
>> fadvise64_64 does. And som
On Mon, 2013-02-04 at 10:36 +0800, Shaohua Li wrote:
> On Fri, Feb 01, 2013 at 10:02:33PM -0700, Stephen Warren wrote:
> > Shaohua,
> >
> > In next-20130128, commit 174f064 "swap: make each swap partition have
> > one address_space" (from the mm/akpm tree) appears causes a hang/RCU
> > stall for m
Hi Greg,
Today's linux-next merge of the driver-core tree got a conflict in
drivers/net/wan/Kconfig between commit a786a7c0ad44 ("wanrouter: completely
decouple obsolete code from kernel") from the net-next tree and commit
c9f1b39aee74 ("drivers/net/wan: remove depends on CONFIG_EXPERIMENTAL")
Hi Greg,
Today's linux-next merge of the driver-core tree got a conflict in
net/wanrouter/Kconfig between commit 6fcdf4facb85 ("wanrouter: delete now
orphaned header content, files/drivers") from the net-next tree and
commit 1ed42403e764 ("net/wanrouter: remove depends on
CONFIG_EXPERIMENTAL") fro
I'm announcing the release of the 3.7.6 kernel.
All users of the 3.7 kernel series must upgrade.
The updated 3.7.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.7.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 8ccebba..23bcb1a 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 4
-SUBLEVEL = 28
+SUBLEVEL = 29
EXTRAVERSION =
NAME = Saber-toothed Squirrel
diff --git a/arch/arm/mach-at91/setup.c b/arch/arm/mach-at91/setup.c
index 582142
I'm announcing the release of the 3.4.29 kernel.
All users of the 3.4 kernel series must upgrade.
The updated 3.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.4.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 2d64957..20f4902 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 0
-SUBLEVEL = 61
+SUBLEVEL = 62
EXTRAVERSION =
NAME = Sneaky Weasel
diff --git a/arch/arm/mm/dma-mapping.c b/arch/arm/mm/dma-mapping.c
index f96d2c7..5663650
I'm announcing the release of the 3.0.62 kernel.
All users of the 3.0 kernel series must upgrade.
The updated 3.0.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.0.y
and can be browsed at the normal kernel.org git web browser:
> -Original Message-
> From: Alan Stern [mailto:st...@rowland.harvard.edu]
> Sent: Monday, February 04, 2013 11:16 AM
> To: Li, Fei
> Cc: Rafael J. Wysocki; a...@linux-foundation.org;
> linux-kernel@vger.kernel.org; linux...@vger.kernel.org; Liu, Chuansheng
> Subject: RE: [PATCH V4] suspe
Whilst I run the risk of a flogging for disloyalty to the Lord of Sealand,
I do have CONFIG_MEMCG=y CONFIG_MEMCG_KMEM not set, and grow tired of the
"mm/memcontrol.c:4972:12: warning: `memcg_propagate_kmem' defined but not
used [-Wunused-function]" seen in 3.8-rc: move the #ifdef outwards.
Signed-
Hi Linus !
Just so that you don't get too bored on your Island here's a patch for
3.8 fixing a nasty bug that affects the new 64T support that was merged
in 3.7. Please apply whenever you have a chance (and an internet
connection !)
Cheers,
Ben.
The following changes since commit 689dfa894c57842
Just FYI, here is the (ugly and appears to crash) sort of patch
I was contemplating.
You may consider this Signed-off-by: in the narrow technical sense that I
can certify the origin of the code, but obviously I do not consider it
a candidate for upstream merging. It is posted here in the hopes th
Hi Konrad,
After merging the xen-two tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/xen/mmu.c: In function 'xen_init_mmu_ops':
arch/x86/xen/mmu.c:2213:10: error: 'struct x86_init_ops' has no member named
'mapping'
arch/x86/xen/mmu.c:2213:39: error: 'xen_mapping_p
From: Cliff Wickman
The crash kernel is not able to find its root device if that device is not
on PCI 0.
This is because it is booted with the command line option memmap=exactmap
which currently clears the e820 table. So ACPI processing does not
find reserved i/o spaces.
This works for a devi
On Sun, Feb 03, 2013 at 07:50:13PM -0800, Greg Kroah-Hartman wrote:
> On Mon, Feb 04, 2013 at 12:42:08PM +0900, Minchan Kim wrote:
> > Hi Greg,
> >
> > On Sun, Feb 03, 2013 at 05:53:33PM -0800, Greg Kroah-Hartman wrote:
> > > On Wed, Jan 30, 2013 at 11:41:42AM +0900, Minchan Kim wrote:
> > > > Loc
On Mon, Feb 04, 2013 at 12:42:08PM +0900, Minchan Kim wrote:
> Hi Greg,
>
> On Sun, Feb 03, 2013 at 05:53:33PM -0800, Greg Kroah-Hartman wrote:
> > On Wed, Jan 30, 2013 at 11:41:42AM +0900, Minchan Kim wrote:
> > > Lockdep complains about recursive deadlock of zram->init_lock.
> > > [1] made it fa
alloc failures already get standardized OOM
messages and a dump_stack.
Convert kzalloc's with multiplies to kcalloc.
Convert kmalloc's with multiplies to kmalloc_array.
Fix a few whitespace defects.
Convert a constant 6 to ETH_ALEN.
Use parentheses around sizeof.
Convert vmalloc/memset to vzalloc.
On Monday 04 February 2013 04:03 AM, Samuel Ortiz wrote:
Hi Laxman,
On Sun, Feb 03, 2013 at 03:19:31PM +0100, Samuel Ortiz wrote:
Hi Laxman,
On Fri, Dec 28, 2012 at 02:59:37PM +0530, Laxman Dewangan wrote:
The patch series add DT support on TPS65090 device.
Also remove the suspend/resume imp
Hi Greg,
On Sun, Feb 03, 2013 at 05:53:33PM -0800, Greg Kroah-Hartman wrote:
> On Wed, Jan 30, 2013 at 11:41:42AM +0900, Minchan Kim wrote:
> > Lockdep complains about recursive deadlock of zram->init_lock.
> > [1] made it false positive because we can't request IO to zram
> > before setting disks
On 2013/2/3 7:10, Tejun Heo wrote:
> The iteration logic of idr_get_next() is borrowed mostly verbatim from
> idr_for_each(). It walks down the tree looking for the slot matching
> the current ID. If the matching slot is not found, the ID is
> incremented by the distance of single slot at the giv
On Sat, 2 Feb 2013, Konstantin Khlebnikov wrote:
> Johannes Weiner wrote:
> > In shmem_find_get_pages_and_swap, use the faster radix tree iterator
> > construct from 78c1d78 "radix-tree: introduce bit-optimized iterator".
> >
> > Signed-off-by: Johannes Weiner
>
> Hmm, ACK. shmem_unuse_inode() al
alloc failures already get standardized OOM
messages and a dump_stack.
Signed-off-by: Joe Perches
---
drivers/net/hamradio/dmascc.c | 7 +--
drivers/net/phy/spi_ks8995.c | 4 +---
drivers/net/virtio_net.c | 4 +---
3 files changed, 3 insertions(+), 12 deletions(-)
diff --git a/drivers
alloc failures already get standardized OOM
messages and a dump_stack.
Convert kzalloc's with multiplies to kcalloc.
Convert kmalloc's with multiplies to kmalloc_array.
Remove now unused variables.
Remove unnecessary memset after kzalloc->kcalloc.
Whitespace cleanups for these changes.
Signed-off
alloc failures already get standardized OOM
messages and a dump_stack.
Convert kzalloc's with multiplies to kcalloc.
Remove now unused size variables.
Signed-off-by: Joe Perches
---
drivers/net/wimax/i2400m/rx.c| 16 +---
drivers/net/wimax/i2400m/usb-notif.c | 1 -
2 files
alloc failures already get standardized OOM
messages and a dump_stack.
Hoist assigns from if tests.
Signed-off-by: Joe Perches
---
drivers/net/wan/cosa.c| 9 -
drivers/net/wan/farsync.c | 6 ++
drivers/net/wan/hdlc.c| 9 -
drivers/net/wan/x25_asy.c | 1 -
4 files cha
alloc failures already get standardized OOM
messages and a dump_stack.
Signed-off-by: Joe Perches
---
drivers/net/usb/ax88172a.c | 6 ++
drivers/net/usb/hso.c| 25 +++--
drivers/net/usb/sierra_net.c | 10 +++---
drivers/net/usb/smsc75xx.c | 6 ++
dri
alloc failures already get standardized OOM
messages and a dump_stack.
Signed-off-by: Joe Perches
---
drivers/net/can/sja1000/ems_pci.c| 1 -
drivers/net/can/sja1000/peak_pci.c | 5 +
drivers/net/can/sja1000/peak_pcmcia.c| 1 -
drivers/net/can/sja1000/plx_pci.c
alloc failures already get standardized OOM
messages and a dump_stack.
Signed-off-by: Joe Perches
---
drivers/net/caif/caif_shmcore.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/net/caif/caif_shmcore.c b/drivers/net/caif/caif_shmcore.c
index bc497d7..bce8bac 100644
--- a/dri
Remove all the OOM messages that follow kernel alloc
failures as there is already a generic equivalent to
these messages in the mm subsystem.
Joe Perches (8):
caif: Remove unnecessary alloc/OOM messages
can: Remove unnecessary alloc/OOM messages
ethernet: Remove unnecessary alloc/OOM message
1 - 100 of 478 matches
Mail list logo
