On Fri, Apr 12, 2013 at 01:25:49PM +0100, Serban Constantinescu wrote:
> The patch set has been successfully tested with a 64bit Linux userspace and
> 64bit binder unit-tests.
>
> This patch set has been successfully tested on 32bit platforms(ARMv7 VExpress)
> and 64bit platforms(ARMv8 RTSM) runni
On Tue, Apr 30, 2013 at 08:41:52AM +0200, Jens Axboe wrote:
> On Mon, Apr 29 2013, Philippe De Muyter wrote:
> >
> > so sda is 8,0 and sdb is 8,16
> >
> > and if, while discovering partitions of /dev/sda, I try to make a
> > partition 16 or higher, it is silently discarded by 'put_partition'.
> >
On Mon, Apr 29 2013, Philippe De Muyter wrote:
> Hi Karel
>
> On Mon, Apr 29, 2013 at 02:36:51PM +0200, Karel Zak wrote:
> > On Mon, Apr 29, 2013 at 01:40:41PM +0200, Philippe De Muyter wrote:
> > > > why not memset(pps_found, )? I also see magical constant 16
> > >
> > > Actually 16 is the m
Andi Kleen writes:
> The FP registers are restored lazily, but the state for this is kept in
> the kernel.
I'm not sure if I understand "lazily" in this context: Do you mean that FP
registers _are_ restored within the kernel, but _not_ from a (possibly modified)
ucontext of a userspace signal han
Hi,
I'm just wondering why device nodes of some serial drivers (mostly
when arch != x86) are not always named "ttyS[:digit:]" ?
For example, I have a ARM based platform which has a serial device
node named "ttymxc0".
I don't see any advantages to do this but only require one to handle
special ca
On Mon, Apr 29 2013, Philippe De Muyter wrote:
> In alloc_read_gpt_entries and alloc_read_gpt_header, the kzalloc'ated
> zones are either totally overwritten by the following read_lba call,
> or freed. As kmalloc is cheaper than kzalloc, use kmalloc.
Applied, thanks.
--
Jens Axboe
--
To unsubs
Commit-ID: 6296ace467c8640317414ba589b124323806f7ce
Gitweb: http://git.kernel.org/tip/6296ace467c8640317414ba589b124323806f7ce
Author: Li Zhong
AuthorDate: Sun, 28 Apr 2013 11:25:58 +0800
Committer: Ingo Molnar
CommitDate: Mon, 29 Apr 2013 13:17:33 +0200
nohz: Protect smp_processor_id(
Hi,
On Mon, Apr 29, 2013 at 02:31:59PM -0700, Linus Torvalds wrote:
> On Mon, Apr 29, 2013 at 2:14 PM, Alan Stern wrote:
> >
> > What other things seemed odd about Greg's pull request?
>
> The only other thing I noticed was the new CONFIG_USB_PHY quesiton,
> which is not something that I think i
2013/4/29 Jan Kara :
> On Fri 26-04-13 10:53:27, Marco Stornelli wrote:
>> Replaced sb_start_write with sb_start_write_killable inside
>> mnt_want_write and mnt_want_write_file.
> The patch looks good. You can add:
> Reviewed-by: Jan Kara
>
Add support for the VIA Velocity network driver to be bound to a
OF created platform device.
Signed-off-by: Tony Prisk
---
.../devicetree/bindings/net/via-velocity.txt | 20 +
drivers/net/ethernet/via/Kconfig |3 +-
drivers/net/ethernet/via/via-velocity.c
Improve the clarity of the code in preparation for converting the
dma functions to generic versions, which require a struct device *.
This makes it possible to store a 'struct device *dev' in the
velocity_info structure.
Signed-off-by: Tony Prisk
---
drivers/net/ethernet/via/via-velocity.c |
Remove the pci_* dma functions and replace with the more generic
versions.
In preparation of adding platform support, a new struct device *dev
is added to struct velocity_info which can be used by both the pci
and platform code.
Signed-off-by: Tony Prisk
---
drivers/net/ethernet/via/via-velocit
v4 changes:
Code tidyup as requested by Francois Romieu
Removed '#ifdef PCI' around PCI code. Compile tested on (!)PCI and (!)PM.
v3 changes:
Rebased against net-next.
Fix errors in pm code.
v2 changes:
Drop patch #1 as requested by David Miller.
Correct the PHYID_ICPLUS_IP101A MII bits - should
Hi,
One more point for your devicetree conversions,
On Mon, Apr 29, 2013 at 01:30:01PM +0530, Prabhakar Lad wrote:
> From: Lad, Prabhakar
>
> add OF support for the mt9p031 sensor driver.
>
> +static struct mt9p031_platform_data
> + *mt9p031_get_pdata(struct i2c_client *client)
> +
> +{
>
On Tue, Apr 30 2013, remaper wrote:
> /*
> * We only want one ->make_request_fn to be active at a time,
> * else stack usage with stacked devices could be a problem.
> * So use current->bio_list to keep a list of requests
> * submited by a make_request_fn function.
> * current->bio_list is als
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
drivers/block/mtip32xx/mtip32xx.c between commit 2077d947260c ("mtip32xx:
Workaround for unaligned writes") from the block tree and commit
"mtip32xx: convert to batch completion" from the akpm tree.
I fixed it up (see below) a
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in ipc/util.c
between commit 823a5ed16606 ("ipc_schedule_free() can do vfree() now")
from the vfs tree and commit "ipc: make refcounter atomic" from the akpm
tree.
I fixed it up (I hope - see below) and can carry the fix as neces
/*
* We only want one ->make_request_fn to be active at a time,
* else stack usage with stacked devices could be a problem.
* So use current->bio_list to keep a list of requests
* submited by a make_request_fn function.
* current->bio_list is also used as a flag to say if
* generic_make_reque
On Tue, Apr 30, 2013 at 02:01:25PM +0900, Jingoo Han wrote:
> Use devm_*() functions to make cleanup paths simpler.
>
> Signed-off-by: Jingoo Han
> ---
> Changes since v1:
> - used sizeof(*nuc900_wdt) instead of sizeof(struct nuc900_wdt)
> - declared 'nuc900_wdt->res' variable as logical variable
Hello Linus,
Please pull battery-2.6 git tree to receive changes queued for v3.10. Here
are some highlights for this merge cycle:
- OpenFirmware/DeviceTree support for the Power Supply core: the core now
automatically populates supplied_from hierarchy from the device tree.
With these patches
On Fri, 2013-04-26 at 17:11 +0200, Mike Galbraith wrote:
> On Wed, 2013-04-17 at 17:53 -0400, Len Brown wrote:
> > On 04/12/2013 12:48 PM, Mike Galbraith wrote:
> > > On Fri, 2013-04-12 at 18:23 +0200, Borislav Petkov wrote:
> > >> On Fri, Apr 12, 2013 at 04:46:50PM +0800, Alex Shi wrote:
> > >>
On 4/29/2013 1:25 PM, Gupta, Pekon wrote:
> From: avinash philip
>
> NAND flash connected in am335x-evm on GPMC controller. This patch adds
> device tree node in am3355-evm with GPMC contoller timing for NAND flash
> interface, NAND partition table, ECC scheme, elm handle id.
>
> Signed-off-by:
On 4/29/2013 1:23 PM, Gupta, Pekon wrote:
> From: avinash philip
>
> From: "Philip, Avinash"
From: line is repeated twice.
>
> Add ELM data node to AM33XX device tree file.
>
> Signed-off-by: Philip Avinash
> Acked-by: Peter Korsgaard
> Tested-by: Pekon Gupta
You should add your sign-off
Use devm_*() functions to make cleanup paths simpler.
Signed-off-by: Jingoo Han
---
No changes since v1:
drivers/watchdog/ts72xx_wdt.c | 64 +++--
1 files changed, 11 insertions(+), 53 deletions(-)
diff --git a/drivers/watchdog/ts72xx_wdt.c b/drivers/watch
Use devm_kzalloc() to make cleanup paths simpler.
Reviewed-by: Guenter Roeck
Signed-off-by: Jingoo Han
---
No changes since v1:
drivers/watchdog/riowd.c |8 ++--
1 files changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/watchdog/riowd.c b/drivers/watchdog/riowd.c
index 004
Use devm_ioremap_nocache() functions to make cleanup paths simpler.
Reviewed-by: Guenter Roeck
Signed-off-by: Jingoo Han
---
No changes since v1:
drivers/watchdog/rc32434_wdt.c | 10 +++---
1 files changed, 3 insertions(+), 7 deletions(-)
diff --git a/drivers/watchdog/rc32434_wdt.c b/dr
Use devm_*() functions to make cleanup paths simpler.
Signed-off-by: Jingoo Han
---
Changes since v1:
- used sizeof(*nuc900_wdt) instead of sizeof(struct nuc900_wdt)
- declared 'nuc900_wdt->res' variable as logical variable
drivers/watchdog/nuc900_wdt.c | 50 +-
Use devm_ioremap() to make cleanup paths simpler.
Reviewed-by: Guenter Roeck
Signed-off-by: Jingoo Han
---
No changes since v1:
drivers/watchdog/mv64x60_wdt.c |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/drivers/watchdog/mv64x60_wdt.c b/drivers/watchdog/mv64x60_w
Use devm_ioremap_nocache() to make cleanup paths simpler.
Reviewed-by: Guenter Roeck
Signed-off-by: Jingoo Han
---
No changes since v1:
drivers/watchdog/bcm63xx_wdt.c |9 -
1 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/watchdog/bcm63xx_wdt.c b/drivers/watch
Use devm_*() functions to make cleanup paths simpler.
Acked-by: Guenter Roeck
Signed-off-by: Jingoo Han
---
No changes since v1:
drivers/watchdog/at32ap700x_wdt.c | 12
1 files changed, 4 insertions(+), 8 deletions(-)
diff --git a/drivers/watchdog/at32ap700x_wdt.c
b/drivers/wa
On Mon, 29 Apr 2013, Dave Jones wrote:
> When set to built-in, the dummy irq driver causes this trace when I boot..
>
> [3.996055] genirq: Flags mismatch irq 0. 0080 (dummy_irq) vs.
> 00015a20 (timer)
> [3.997055] Pid: 1, comm: swapper/0 Not tainted 3.9.0+ #29
> [3.997768] Call T
On Sat, Apr 27, 2013 at 4:10 AM, Artem S. Tashkinov wrote:
>>
>>Did this problem ever get resolved?
>>
>
> Hello,
>
> Unfortunately, no. Out of curiosity I've tried booting kernel
> 3.9-rc8 in EUFI mode but it exhibits the same problem.
>
> Right after the boot:
>
> [root@localhost ~]# dd if=/dev/
From: Benjamin Poirier
Date: Mon, 29 Apr 2013 17:42:14 -0400
> Currently, peeking on a unix stream socket with an offset larger than len of
> the data in the sk receive queue returns immediately with bogus data.
>
> This patch fixes this so that the behavior is the same as peeking with no
> offs
From: Benjamin Poirier
Date: Mon, 29 Apr 2013 17:42:13 -0400
> Currently, peeking on a unix datagram socket with an offset larger than len of
> the data in the sk receive queue returns immediately with bogus data. That's
> because *off is not reset between each skb_queue_walk().
>
> This patch f
From: Benjamin Poirier
Date: Mon, 29 Apr 2013 17:42:12 -0400
> "77c1090 net: fix infinite loop in __skb_recv_datagram()" (v3.8) introduced a
> regression:
> After that commit, recv can no longer peek beyond a 0-sized skb in the queue.
> __skb_recv_datagram() instead stops at the first skb with le
On 04/29/2013 01:36 AM, Matthias Schniedermeyer wrote:
> On 28.04.2013 17:56, Linus Torvalds wrote:
>
> I'm not sure if it is supported, but building with a O= -directory that
> was previously used to build a 3.8.9-kernel that was "clean"ed (but not
> "mrproper"ed) before building 3.9 results in
From: "John W. Linville"
Date: Mon, 29 Apr 2013 15:45:51 -0400
> For the Bluetooth bits, Gustavo says:
>
> "A few more patches intended for 3.10, the most important one is the support
> in
> btusb for fw loading for the Intel Bluetooth device. Other than that we have
> only fixes and clean ups.
Hm. I'm not sure why this path series start [patch 4/10]. maybe I need to
review my script again.
anyway, patch 1-3 don't exist. sorry for confusing.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo inf
On Mon, Apr 29, 2013 at 01:40:30PM -0700, Tim Chen wrote:
>
> If I allocate the transform under the mod init instead, how can I make
> sure that the fast version is already registered if I have it compiled
> in? It is not clear to me how that's done looking at the libcrc32c
> code.
This is only
From: Kishon Vijay Abraham I
Commit 92702df3570e ("ARM: OMAP4: PM: fix PM regression introduced by recent
clock cleanup") makes the 'ocp2scp_usb_phy_phy_48m' as optional
functional clock causing regression in MUSB. But this 48MHz clock is a
mandatory clock for usb phy attached to ocp2scp and henc
From: KOSAKI Motohiro
Now we have similar four timer related functions, cpu_clock_sample(),
cpu_clock_sample_group(), cpu_timer_sample() and cpu_timer_sample_group().
For readability, making do_cpu_clock_timer_sample() and thread_cputime()
helper functions and all *_sample functions use them.
S
From: KOSAKI Motohiro
rq lock in task_sched_runtime() is necessary for two reasons. 1)
accessing se.sum_exec_runtime is inatomic on 32bit and 2)
do_task_delta_exec() require it.
And then, 64bit can avoid holds rq lock when add_delta is false.
Signed-off-by: KOSAKI Motohiro
---
kernel/sched/co
From: KOSAKI Motohiro
A type of tsk->se.sum_exec_runtime is u64. Thus reading it is racy when
running 32bit. We should use task_sched_runtime().
Cc: Olivier Langlois
CC: Martin Schwidefsky
Cc: Steven Rostedt
Cc: Thomas Gleixner
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Peter Zijlstra
Si
From: KOSAKI Motohiro
Currently glibc's rt/tst-cputimer1 testcase is spradically fail because
a timer created by timer_create() may fire earlier than it's specified.
posix_cpu_timer_set() uses "val" as current time for three purpose. 1)
initialize sig->cputimer. 2) calculation "old" val. 3) calc
From: KOSAKI Motohiro
For process timer, we use cpu_clock_sample_group() and cpu_timer_sample_group()
correctly. However for thread timer, we always use cpu_clock_sample().
That's wrong becuase cpu_clock_sample() account uncommited delta_exec too. And
this is inconsistency against run_posix_cpu_t
From: KOSAKI Motohiro
Currently glibc rt/tst-cpuclock2 test(*) sporadically fail. Because
scheduler delta can be accounted twice from thread_group_cputimer()
and account_group_exec_runtime().
Finally, clock_nanosleep() wakes up before an argument. And that is
posix violation. This issue was intr
From: KOSAKI Motohiro
When tsk->signal->cputimer->running is 1, signal->cputimer and
tsk->sum_sched_runtime increase the same pace. update_curr() increase
both account.
However, there is one exeception. When thread exiting, __exit_signal()
turns over task's sum_shced_runtime to sig->sum_sched_ru
From: Paul E. McKenney
The following RCU splat indicates lack of RCU protection:
[ 953.267649] ===
[ 953.267652] [ INFO: suspicious RCU usage. ]
[ 953.267657] 3.9.0-0.rc6.git2.4.fc19.ppc64p7 #1 Not tainted
[ 953.267661] ---
[ 953.26766
From: Linus Torvalds
I think we could just move the full vm_iomap_memory() function into
util.h or similar, but I didn't get any reply from anybody actually
using nommu even to this trivial patch, so I'm not going to touch it any
more than required.
Here's the fairly minimal stub to make the nom
Glibc's posix timer testcase found a lot of bugs in posix timer code. This
series, hopefully,
fixes all of them. All patches are independent each other logically.
[PATCH 1/7] posix-cpu-timers: don't account cpu timer after stopped thread
runtime accounting
[PATCH 2/7] posix-cpu-timers: fix acou
Most architectures that define CONFIG_HAVE_DMA, have implementations for
both dma_alloc_attrs() and dma_free_attrs(). All achitectures that do
not define CONFIG_HAVE_DMA also have both of these definitions provided by
dma-mapping-broken.h.
Add default implementations for these functions on s390.
Most architectures that define CONFIG_HAVE_DMA, have implementations for
both dma_alloc_attrs() and dma_free_attrs(). All achitectures that do
not define CONFIG_HAVE_DMA also have both of these definitions provided by
dma-mapping-broken.h.
Add default implementations for these functions on parisc
Most architectures that define CONFIG_HAVE_DMA, have implementations for
both dma_alloc_attrs() and dma_free_attrs(). All achitectures that do
not define CONFIG_HAVE_DMA also have both of these definitions provided by
dma-mapping-broken.h.
Add default implementations for these functions on c6x.
Most architectures that define CONFIG_HAVE_DMA, have implementations for
both dma_alloc_attrs() and dma_free_attrs(). All achitectures that do
not define CONFIG_HAVE_DMA also have both of these definitions provided by
dma-mapping-broken.h.
Add default implementations for these functions on arm64.
Most architectures that define CONFIG_HAVE_DMA=y, have implementations for
both dma_alloc_attrs() and dma_free_attrs(). All achitectures that do
not define CONFIG_HAVE_DMA also have both of these definitions provided by
dma-mapping-broken.h.
Provide a default definition for the archs that define
change log from v1:
o found another deadlock case, so change the approach
From 145b6ee0b2523bad0e28c09f4ac5bb050cd22085 Mon Sep 17 00:00:00 2001
From: Jaegeuk Kim
Date: Tue, 30 Apr 2013 11:33:27 +0900
Subject: [PATCH] f2fs: avoid deadlock during evict after f2fs_gc
Cc: linux-fsde...@vger.kernel.
Hello Linus!
Here are the target pending changes for the v3.10-rc1 merge window.
Please go ahead and pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git
for-next-merge
The highlights this round include:
- Add fileio support for WRITE_SAME w/ UNMAP=1 discard (a
This is intended for use in loops which read data protected by RCU and may
have a large number of iterations. Such an example is dumping the list of
connections known to IPVS: ip_vs_conn_array() and ip_vs_conn_seq_next().
The call to cond_resched() is guarded by #ifndef CONFIG_PREEMPT_RCU as in
t
This avoids the situation where a dump of a large number of connections
may prevent scheduling for a long time while also avoiding excessive
calls to rcu_read_unlock() and rcu_read_lock().
Note that in the case of !CONFIG_PREEMPT_RCU this will
add a call to cond_resched().
Compile tested only.
C
Add a helper that for use in loops which read data protected by RCU and
may have a large number of iterations. Such an example is dumping the list
of connections known to IPVS: ip_vs_conn_array() and ip_vs_conn_seq_next().
This series also updates the two ip_vs functions mentioned above
to use th
On Fri, Apr 26, 2013 at 08:15:34AM +0200, Ingo Molnar wrote:
>
> * Simon Horman wrote:
>
> > This avoids the situation where a dump of a large number of connections
> > may prevent scheduling for a long time while also avoiding excessive
> > calls to rcu_read_unlock() and rcu_read_lock().
> >
>
This should have been Cc'd to the scheduler maintainers.
-- Steve
On Mon, Apr 29, 2013 at 06:20:28PM -0700, David VomLehn wrote:
> Msleep_interruptible() on a dual processor system may wait a long time.
>
> On some reboots, calling msleep_interruptible() from CPU 1 on a dual
> processor system w
On Mon, Apr 29, 2013 at 09:59:30AM -0700, Randy Dunlap wrote:
> On 04/29/13 09:54, Alex Williamson wrote:
> > Fix build with CONFIG_PCI unset by linking KVM_CAP_IOMMU to
> > device assignment config option. It has no purpose otherwise.
> >
> > Signed-off-by: Alex Williamson
>
> Reported-by: Ran
On Tue, Apr 30, 2013 at 10:58:40AM +0900, Simon Horman wrote:
> On Mon, Apr 29, 2013 at 04:49:07PM +0200, Arnd Bergmann wrote:
> > On Friday 26 April 2013, Simon Horman wrote:
> > > > diff --git a/arch/arm/mach-shmobile/intc-r8a7740.c
> > > > b/arch/arm/mach-shmobile/intc-r8a7740.c
> > > > index 8
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
net/mac802154/mac802154.h between commit 2c1bbbffa0b6 ("net: mac802154:
comparision issue of type cast, finding by EXTRA_CFLAGS=-W") from the net
tree and commit 7dd43d356e73 ("mac802154: Do not try to resend failed
packets")
On Mon, 2013-04-29 at 21:06 -0400, Steven Rostedt wrote:
> Dear RT Folks,
>
> I'm pleased to announce the 3.4.41-rt55-feat3 feature release.
>
> Note, I first uploaded -feat2 then realized I didn't add a compile fix by
> Mike Galbraith, and then created the -feat3 with that fix.
>
Because of th
On 04/27/2013 07:35 AM, Rafael J. Wysocki wrote:
> On Saturday, April 27, 2013 04:58:53 AM Artem S. Tashkinov wrote:
>> Hello,
>>
>> Just wanted to let everyone know that CONFIG_X86_INTEL_PSTATE wreaks
>> havoc with the CPU frequency subsystem in the Linux kernel.
>>
>> With this option enabled:
>>
Dear RT Folks,
I'm pleased to announce the 3.2.43-rt63-feat2 feature release.
Note, although this release adds the changes to use slub in -rt, I'm now
hitting a large latency using SLUB instead of SLAB. As this only seems
to happen in 3.2-rt and not 3.4-rt or 3.6-rt, I'm not really worried
about
On Tuesday, April 30, 2013 3:10 AM, Guenter Roeck wrote:
> On Mon, Apr 29, 2013 at 06:36:34PM +0900, Jingoo Han wrote:
> > Use devm_*() functions to make cleanup paths simpler.
> >
> > Signed-off-by: Jingoo Han
> > ---
> > drivers/watchdog/ts72xx_wdt.c | 64
> > +++-
> -Original Message-
> From: Guenter Roeck [mailto:li...@roeck-us.net]
> Sent: Tuesday, April 30, 2013 3:03 AM
> To: Jingoo Han
> Cc: 'Andrew Morton'; linux-kernel@vger.kernel.org; 'Wim Van Sebroeck';
> linux-watch...@vger.kernel.org
> Subject: Re: [PATCH RESEND 4/7] watchdog: nuc900_wdt
On Tue, Apr 30, 2013 at 01:54:37AM +, Shuah Khan wrote:
> On Mon, 2013-04-29 at 12:01 -0700, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.8.11 release.
> > There are 42 patches in this series, all will be posted as a response
> > to this one. If anyone h
On Mon, Apr 29, 2013 at 04:49:07PM +0200, Arnd Bergmann wrote:
> On Friday 26 April 2013, Simon Horman wrote:
> > > diff --git a/arch/arm/mach-shmobile/intc-r8a7740.c
> > > b/arch/arm/mach-shmobile/intc-r8a7740.c
> > > index 8871f77..5dc57f1 100644
> > > --- a/arch/arm/mach-shmobile/intc-r8a7740.c
On Tue, Apr 30, 2013 at 10:56:39AM +0900, Jingoo Han wrote:
> On Tuesday, April 30, 2013 2:55 AM, Guenter Roeck wrote:
> > On Mon, Apr 29, 2013 at 06:35:15PM +0900, Jingoo Han wrote:
> > > Use devm_ioremap() to make cleanup paths simpler.
> > >
> > > Signed-off-by: Jingoo Han
> >
> > This patch a
On Tue, Apr 30, 2013 at 10:54:03AM +0900, Jingoo Han wrote:
> On Tuesday, April 30, 2013 1:44 AM, Guenter Roeck wrote:
> > On Mon, Apr 29, 2013 at 06:30:43PM +0900, Jingoo Han wrote:
> > > Use devm_gpio_request_one() to make cleanup paths simpler.
> > >
> > > Signed-off-by: Jingoo Han
> >
> > Thi
On Tuesday, April 30, 2013 2:55 AM, Guenter Roeck wrote:
> On Mon, Apr 29, 2013 at 06:35:15PM +0900, Jingoo Han wrote:
> > Use devm_ioremap() to make cleanup paths simpler.
> >
> > Signed-off-by: Jingoo Han
>
> This patch also addresses the missing call to iounmap() if the call
> to misc_register
On Mon, 2013-04-29 at 12:01 -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.8.11 release.
> There are 42 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> R
On Tuesday, April 30, 2013 1:44 AM, Guenter Roeck wrote:
> On Mon, Apr 29, 2013 at 06:30:43PM +0900, Jingoo Han wrote:
> > Use devm_gpio_request_one() to make cleanup paths simpler.
> >
> > Signed-off-by: Jingoo Han
>
> This patch also addresses the missing gpio_free in the probe error path
> (if
On Mon, 2013-04-29 at 12:02 -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.4.43 release.
> There are 34 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> R
On Mon, 2013-04-29 at 12:02 -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.0.76 release.
> There are 30 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> R
On Mon, 2013-04-29 at 15:55 -0700, Tejun Heo wrote:
> Benjamin, can you please pick this up?
>
> Thanks a lot and sorry about the trouble.
Done.
Cheers,
Ben.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More ma
Msleep_interruptible() on a dual processor system may wait a long time.
On some reboots, calling msleep_interruptible() from CPU 1 on a dual
processor system will not return for seconds or even minutes. This happens
because ksoftirqd/1 migrates to CPU 0, which is allowed because its
cpus_allowed m
On Mon, Apr 29, 2013 at 05:36:40PM -0700, Simon Kirby wrote:
> On Mon, Apr 29, 2013 at 05:21:17PM -0700, Greg Kroah-Hartman wrote:
>
> > On Mon, Apr 29, 2013 at 05:14:45PM -0700, Simon Kirby wrote:
> > > On Mon, Apr 29, 2013 at 12:01:44PM -0700, Greg Kroah-Hartman wrote:
> > >
> > > > 3.8-stable
On 04/29/2013 05:48 PM, Rik van Riel wrote:
On 04/29/2013 06:03 PM, Linus Torvalds wrote:
Seriously, you can compile yourself a 64-bit kernel and continue to
use your 32-bit user-land. And you can complain to whatever distro you
used that it didn't do that in the first place. But we're not goin
On 04/25/2013 01:31 PM, Thomas Gleixner wrote:
With the module refcount held for the current clocksource there is no
way to unload the module.
Provide a sysfs interface which allows to unbind the clocksource. One
could argue that the clocksource override could be (ab)used to do so,
but the clock
Add pm_ops_ptr() macro that allows the .pm entry in the driver structures
to be assigned without having an #define xxx NULL for the case that PM is
not enabled.
Signed-off-by: Jingoo Han
---
drivers/i2c/busses/i2c-s3c2410.c |8 +---
include/linux/pm.h |2 ++
2 files cha
Dear RT Folks,
I'm pleased to announce the 3.4.41-rt55-feat3 feature release.
Note, I first uploaded -feat2 then realized I didn't add a compile fix by
Mike Galbraith, and then created the -feat3 with that fix.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/
Hello Cliff,
On Mon, Apr 29, 2013 at 04:25:53PM -0500, Cliff Wickman wrote:
>
> /proc//smaps should not be looking at VM_PFNMAP areas.
>
> Certain tests in show_smap() (especially for huge pages) assume that the
> mapped PFN's are backed with page structures. And this is not usually true
> for
On Mon, 2013-04-29 at 20:08 -0400, Steven Rostedt wrote:
> I'll also run my full ftrace test suite on your latest kernel, and see
> if it finds anything else.
>
With the fix I sent, everything passed.
Thanks,
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On 04/25/2013 01:31 PM, Thomas Gleixner wrote:
The unregister call can fail, if the clocksource is the current one
and there is no replacement clocksource available. It can also fail,
if the clocksource is the watchdog clocksource and I'm not going to
provide support for this.
Signed-off-by: Tho
On 04/25/2013 01:31 PM, Thomas Gleixner wrote:
Preparatory patch for clocksource unbind support.
Modify clocksource_select, so it skips the current clocksource on
request and tries to find a fallback clocksource. Convert all existing
users. No functional change.
Signed-off-by: Thomas Gleixner
-
On Monday, April 29, 2013 9:13 PM, Lars-Peter Clausen wrote:
> On 04/29/2013 07:41 AM, Jingoo Han wrote:
> > On Saturday, April 27, 2013 11:41 PM, Rafael J. Wysocki:
> >>
> >> On Saturday, April 27, 2013 11:54:50 AM Jingoo Han wrote:
> >>> Add pm_ops_ptr() macro that allows the .pm entry in the dri
Hello, Linus.
* Fixes and a lot of cleanups. Locking cleanup is finally complete.
cgroup_mutex is no longer exposed to individual controlelrs which
used to cause nasty deadlock issues. Li fixed and cleaned up quite
a bit including long standing ones like racy cgroup_path().
* device cgrou
On 04/25/2013 01:31 PM, Thomas Gleixner wrote:
Add a module refcount, so the current clocksource cannot be removed
unconditionally.
Signed-off-by: Thomas Gleixner
---
include/linux/clocksource.h |3 +++
kernel/time/timekeeping.c | 15 ++-
2 files changed, 13 insertions(+)
On Mon, 2013-04-29 at 17:42 -0400, Benjamin Poirier wrote:
> Currently, peeking on a unix stream socket with an offset larger than len of
> the data in the sk receive queue returns immediately with bogus data.
>
> This patch fixes this so that the behavior is the same as peeking with no
> offset o
On Mon, 2013-04-29 at 17:42 -0400, Benjamin Poirier wrote:
> Currently, peeking on a unix datagram socket with an offset larger than len of
> the data in the sk receive queue returns immediately with bogus data. That's
> because *off is not reset between each skb_queue_walk().
>
> This patch fixes
On 04/29/2013 06:03 PM, Linus Torvalds wrote:
Seriously, you can compile yourself a 64-bit kernel and continue to
use your 32-bit user-land. And you can complain to whatever distro you
used that it didn't do that in the first place. But we're not going to
bother with trying to tune PAE for some
On Mon, 2013-04-29 at 17:42 -0400, Benjamin Poirier wrote:
> "77c1090 net: fix infinite loop in __skb_recv_datagram()" (v3.8) introduced a
> regression:
> After that commit, recv can no longer peek beyond a 0-sized skb in the queue.
> __skb_recv_datagram() instead stops at the first skb with len ==
On 04/25/2013 01:31 PM, Thomas Gleixner wrote:
timekeeping_notify() can fail due cs->enable() failure. Though the
caller does not notice and happily keeps the wrong clocksource as the
current one.
Let the caller know about failure, so the current clocksource will be
shown correctly in sysfs.
Si
On Mon, Apr 29, 2013 at 05:21:17PM -0700, Greg Kroah-Hartman wrote:
> On Mon, Apr 29, 2013 at 05:14:45PM -0700, Simon Kirby wrote:
> > On Mon, Apr 29, 2013 at 12:01:44PM -0700, Greg Kroah-Hartman wrote:
> >
> > > 3.8-stable review patch. If anyone has any objections, please let me
> > > know.
>
On 04/25/2013 01:31 PM, Thomas Gleixner wrote:
If a clocksource has a (wrong) high rating, but can't be used as a
timebase for oneshot tick mode, it is unconditionally selected even
when the system is already in oneshot tick mode. This causes full
system failure.
Verify the clocksource selection
1 - 100 of 699 matches
Mail list logo
