On Fri, 31 May 2013, Takashi Iwai wrote:
> > struct snd_card contains pointers to two different devices: dev and
> > card_dev. Some contexts might want to use one of them for log messages
> > while other contexts might want to use the other.
>
> Yes, there are some corner cases, indeed.
>
>
The SOC interrupt controller driver for the Abilis Systems TB10x series of
SOCs based on ARC700 CPUs.
This patch depends on commits eb76bdd407d8a90e59a06cb0158886df390e5d1c and
712bc93df9e7f14b8a163148d2aa7c778e151627 from branch irq/for-arm of
On Friday 31 May 2013 16:18:50 Lee Jones wrote:
> On Fri, 31 May 2013, Arnd Bergmann wrote:
>
> > On Friday 31 May 2013 15:24:32 Lee Jones wrote:
> > > In order to utilise all of the memory located on ux500 based devices
> > > we have to enable HIGHMEM. Without it the kernel truncates memory down
On Fri, May 31, 2013 at 07:22:24PM +0900, 김승우 wrote:
> Hello Daniel,
>
> Thanks for your comment.
>
> On 2013년 05월 31일 18:14, Daniel Vetter wrote:
> > On Fri, May 31, 2013 at 10:54 AM, Seung-Woo Kim
> > wrote:
> >> importer private data in dma-buf attachment can be used by importer to
> >>
At Fri, 31 May 2013 11:33:44 -0400 (EDT),
Alan Stern wrote:
>
> On Fri, 31 May 2013, Takashi Iwai wrote:
>
> > > struct snd_card contains pointers to two different devices: dev and
> > > card_dev. Some contexts might want to use one of them for log messages
> > > while other contexts might
On 15:57 Fri 31 May , Michal Simek wrote:
> On 05/31/2013 01:00 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 10:14 Fri 31 May , Michal Simek wrote:
> >> Hi Jean-Christophe,
> >>
> >> On 05/30/2013 10:17 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> >>> On 15:49 Thu 30 May ,
2013/5/31 Jean-Christophe PLAGNIOL-VILLARD :
> On 16:28 Fri 31 May , Richard Genoud wrote:
>> When removing atmel_lcdfb module, the backlight is unregistered but not
>> blanked. (only for CONFIG_BACKLIGHT_ATMEL_LCDC case).
>> This can result in the screen going full white depending on how the
On Fri, May 31, 2013 at 03:48:26PM +0100, Matthew Garrett wrote:
> On Fri, May 31, 2013 at 07:42:37AM -0700, James Bottomley wrote:
> > On Fri, 2013-05-31 at 15:34 +0100, Matthew Garrett wrote:
> > > I agree that a revert is probably the right thing to do here, but the
> > > original patch was
The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
are different.
A1-A3 = gpio_wk7
ES = gpio_110
There is no change to LED D2
Abstract away the pinmux and the LED definitions for the two boards into
the respective DTS files.
Signed-off-by: Dan Murphy
---
v10 - Update gpio
On Thu, May 30, 2013 at 08:51:00AM -0400, Vince Weaver wrote:
> On Thu, 30 May 2013, Peter Zijlstra wrote:
> > I'll go prod, thanks again!
>
> The bug looks related to hw breakpoints, not sure if the bugs Oleg
> Nesterov has been reporting in this area might be relevant or not.
Nah its not. I
Update the dt property ti,audpwron-gpio to use the
gpio macro definition for GPIO_ACTIVE_HIGH.
Signed-off-by: Dan Murphy
---
arch/arm/boot/dts/omap4-panda-common.dtsi |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/boot/dts/omap4-panda-common.dtsi
On Fri, May 31, 2013 at 04:21:04PM +0200, Stephane Eranian wrote:
> Hi,
>
> Any comment on this patch?
> It does really help with stack pressure and will help fix a PEBS-LL issue.
Yeah, its on my todo list, but I've been spending all of my time trying
to fix all the bugs Vince has been throwing
When removing atmel_lcdfb module, the backlight is unregistered but not
blanked. (only for CONFIG_BACKLIGHT_ATMEL_LCDC case).
This can result in the screen going full white depending on how the PWM
is wired.
Signed-off-by: Richard Genoud
---
drivers/video/atmel_lcdfb.c | 10 --
1 file
On Fri, May 24, 2013 at 11:32:19AM -0700, Rohit Vaswani wrote:
Could this series go through David's tree or is there a better way to do this?
It would be great if I can have you ack for the gpio patch.
Due to pending feedback, and compilation failures on ppc, I'll drop
this series from my
The dw_dmac driver is going to be split into multiple files. To make this more
convenient move it to an own directory.
Signed-off-by: Andy Shevchenko
---
MAINTAINERS | 3 +--
drivers/dma/Kconfig | 20 +---
drivers/dma/Makefile
This is first attempt to do split as suggested by Arnd et al.
First patch moves driver to its own folder.
Second one does the actual split.
During this files are renamed: mostly means that dw_dmac prefix is eliminated.
I hope to get it ready to be included in v3.11.
Andy Shevchenko (2):
dma:
To simplify the driver development let's split driver to library and platform
code parts. It helps us to add PCI driver in future.
Signed-off-by: Andy Shevchenko
---
drivers/dma/Makefile | 2 +-
drivers/dma/dw/Kconfig| 8 +-
drivers/dma/dw/Makefile
Commit 8d57470d cause a kernel panic while setting mem=2G.
[mem 0x-0x000f] page 4k
[mem 0x7fe0-0x7fff] page 1G
[mem 0x7c00-0x7fdf] page 1G
[mem 0x0010-0x001f] page 4k
[mem 0x0020-0x7bff] page 2M
for last entry is not what we
On Fri, May 31, 2013 at 01:26:49AM -0300, Henrique de Moraes Holschuh wrote:
> On Thu, 30 May 2013, Jacob Shin wrote:
> > mkdir initrd
> > cd initrd
> > -mkdir kernel
> > -mkdir kernel/x86
> > -mkdir kernel/x86/microcode
> > -cp ../microcode.bin kernel/x86/microcode/GenuineIntel.bin
> > -find
The following changes since commit e4aa937ec75df0eea0bee03bffa3303ad36c986b:
Linux 3.10-rc3 (2013-05-26 16:00:47 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git
tags/please-pull-aertracefix
for you to fetch changes up to
On Fri, May 31, 2013 at 5:48 PM, Peter Zijlstra wrote:
> On Fri, May 31, 2013 at 04:21:04PM +0200, Stephane Eranian wrote:
>> Hi,
>>
>> Any comment on this patch?
>> It does really help with stack pressure and will help fix a PEBS-LL issue.
>
> Yeah, its on my todo list, but I've been spending
On Thu, May 23, 2013 at 11:07:03AM -0700, Andrew Hunter wrote:
> schedule_events caches event constraints on the stack during
> scheduling. Given the number of possible events, this is 512 bytes of
> stack; since it can be invoked under schedule() under god-knows-what,
> this is causing stack
On Fri, May 31, 2013 at 04:23:20PM +0100, Stefano Stabellini wrote:
> On Fri, 31 May 2013, Stefano Stabellini wrote:
> > On Fri, 31 May 2013, Catalin Marinas wrote:
> > > On Fri, May 31, 2013 at 02:21:16PM +0100, Stefano Stabellini wrote:
> > > > On Fri, 31 May 2013, Catalin Marinas wrote:
> > > >
On Fri, May 31, 2013 at 11:18:48AM -0400, Steven Rostedt wrote:
> On Fri, 2013-05-31 at 15:43 +0200, Frederic Weisbecker wrote:
>
> > > +void __sched notrace preempt_schedule_context(void)
> > > +{
> > > + struct thread_info *ti = current_thread_info();
> > > + enum ctx_state prev_ctx;
> > > +
>
Convert drivers/rtc/class to use dev_pm_ops for power management and
remove Legacy PM ops hooks. With this change, rtc class registers
suspend/resume callbacks via class->pm (dev_pm_ops) instead of Legacy
class->suspend/resume. When __device_suspend() runs call-backs, it will
find class->pm ops
On Thu, May 30, 2013 at 02:34:20PM +0530, Kamalesh Babulal wrote:
> 78becc2709 "sched: Use an accessor to read the rq clock"
> introduces rq_clock(), which obsoletes use of "rq" in
> expire_cfs_rq_runtime() and triggers build warning:
>
> kernel/sched/fair.c: In function 'expire_cfs_rq_runtime':
On Fri, May 31, 2013 at 11:18:48AM -0400, Steven Rostedt wrote:
> I'll rewrite the patch and send it out for another review.
This is the only part I read in detail and marked the thread read!
Awaiting v2 :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On Fri, May 31, 2013 at 04:21:27PM +0200, Michael Holzheu wrote:
> On Thu, 30 May 2013 16:38:47 -0400
> Vivek Goyal wrote:
>
> > On Wed, May 29, 2013 at 01:51:44PM +0200, Michael Holzheu wrote:
> >
> > [..]
> > > >>> START QUOTE
> > >
> > > [PATCH v3 1/3] kdump: Introduce ELF header in new
On 05/31/2013 05:48 AM, Grant Likely wrote:
> On Fri, 31 May 2013 11:29:30 +0100, Ian Campbell
> wrote:
>> This affects arch/powerpc/boot/dts/virtex440-ml510.dts but I think it is
>> actually a more general issue:
>>
>> $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux- virtex440-ml510.dtb
Hi Michael,
could you please look at
https://bugzilla.kernel.org/show_bug.cgi?id=58711
?
This part of man 7 signal
3. Real-time signals are delivered in a guaranteed order. Multiple
real-time signals of the same type are delivered in the order they
On 05/31/2013 02:45 AM, Arnd Bergmann wrote:
> Can you check this part again:
>
> On Tuesday 21 May 2013 20:36:35 Stephen Warren wrote:
>> diff --git a/drivers/spi/spi-pxa2xx.c b/drivers/spi/spi-pxa2xx.c
...
>> @@ -1190,11 +1172,13 @@ static int pxa2xx_spi_probe(struct platform_device
>> *pdev)
On Fri, 2013-05-31 at 18:01 +0200, Peter Zijlstra wrote:
> On Fri, May 31, 2013 at 11:18:48AM -0400, Steven Rostedt wrote:
> > I'll rewrite the patch and send it out for another review.
>
> This is the only part I read in detail and marked the thread read!
>
> Awaiting v2 :-)
Yeah, it would be
Hello Dan,
On 05/31/2013 05:45 PM, Dan Murphy wrote:
Update the dt property ti,audpwron-gpio to use the
gpio macro definition for GPIO_ACTIVE_HIGH.
Signed-off-by: Dan Murphy
---
arch/arm/boot/dts/omap4-panda-common.dtsi |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff
Hi,
On Tue, Apr 30, 2013 at 05:21:17PM +0800, Tang Chen wrote:
> If all the memory ranges in SRAT are hotpluggable, we should not
> arrange them all in ZONE_MOVABLE. Otherwise the kernel won't have
> enough memory to boot.
>
> This patch introduce a global variable kernel_nodemask to mark
> all
On Fri, May 24, 2013 at 05:29:19PM +0800, Tang Chen wrote:
> We mark out movable memory ranges and reserve them with MEMBLK_HOTPLUGGABLE
> flag in
> memblock.reserved. This should be done after the memory mapping is initialized
> because the kernel now supports allocate pagetable pages on local
Fix various weird constructions of strncpy(dst, src, strlen(src)). Length
limits should be about the space available in the destination, not
repurposed as a method to either always include or always exclude
a trailing NULL byte. Either the NULL should always be copied
(using strlcpy), or it should
On Fri 31 May 2013 03:51:51 AM CST, Rafael J. Wysocki wrote:
> On Thursday, May 30, 2013 11:33:56 AM Bjorn Helgaas wrote:
>> On Tue, May 14, 2013 at 09:00:39PM +0800, Jiang Liu wrote:
>>> Use acpi_handle_print() and pr_xxx() to print messages in pci_root.c.
>>>
>>> Signed-off-by: Jiang Liu
>>>
Am Freitag, den 31.05.2013, 17:29 +0200 schrieb Daniel Vetter:
> On Fri, May 31, 2013 at 07:22:24PM +0900, 김승우 wrote:
> > Hello Daniel,
> >
> > Thanks for your comment.
> >
> > On 2013년 05월 31일 18:14, Daniel Vetter wrote:
> > > On Fri, May 31, 2013 at 10:54 AM, Seung-Woo Kim
> > > wrote:
> >
Hi,
On Fri, May 24, 2013 at 05:29:16PM +0800, Tang Chen wrote:
> If all the memory ranges in SRAT are hotpluggable, we should not
> arrange them all in ZONE_MOVABLE. Otherwise the kernel won't have
> enough memory to boot.
>
> This patch introduce a global variable kernel_nodemask to mark
> all
On Fri, May 31, 2013 at 03:02:29PM +0200, Stephane Eranian wrote:
> Hi,
>
> So looked at this patch again. There is nothing wrong with the code.
> But there is something bothering me with the usage model. I think
> the choice of having pebs->ip for precise=1 or pebs->real_ip for
> precise=2 is
> Hi,
sorry, I meant to reply to v3, not v2. Please continue discussion in v3 (i sent
the mail there as well)
- Vasilis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
(5/26/13 5:35 PM), kosaki.motoh...@gmail.com wrote:
> From: KOSAKI Motohiro
>
> 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.
>
> Changes from v4
> - [1/8] comments
On Fri, May 31, 2013 at 10:43:49AM -0500, Russ Anderson wrote:
> When did writing EFI variables to nvram become necessary to boot on
> UEFI? And if it is necessary, why is it that only linux boot loaders
> that use EFI stubs (generally grub2) need it? The current kernel
> boots using EFI/grub
Correct spelling typo in printk within various drivers.
Signed-off-by: Masanari Iida
---
drivers/acpi/acpica/utobject.c | 2 +-
drivers/cpufreq/s3c2416-cpufreq.c | 2 +-
drivers/net/ethernet/mellanox/mlx4/main.c | 2 +-
On Fri, May 31, 2013 at 5:04 PM, Stephen Warren wrote:
> On 05/31/2013 05:48 AM, Grant Likely wrote:
>> On Fri, 31 May 2013 11:29:30 +0100, Ian Campbell
>> wrote:
>>> This affects arch/powerpc/boot/dts/virtex440-ml510.dts but I think it is
>>> actually a more general issue:
>>>
>>> $
On 05/31/2013 05:29 PM, Arnd Bergmann wrote:
> On Friday 31 May 2013 10:06:43 Timur Tabi wrote:
>> On 05/31/2013 09:56 AM, Arnd Bergmann wrote:
>>> Yes, unfortunately, this is what all other frame buffer drivers do
>>> at the moment. It is technically not correct, but most architectures
>>> are
On 05/31/2013 11:51 AM, Viresh Kumar wrote:
>> ---
>> arch/x86/include/asm/processor.h | 29 --
>> drivers/cpufreq/Makefile | 2 +-
>> drivers/cpufreq/acpi-cpufreq.c | 5
>> drivers/cpufreq/cpufreq.c | 21
>>
On Fri, May 31, 2013 at 05:55:05PM +0200, Stephane Eranian wrote:
> On Fri, May 31, 2013 at 5:48 PM, Peter Zijlstra wrote:
> > On Fri, May 31, 2013 at 04:21:04PM +0200, Stephane Eranian wrote:
> >> Hi,
> >>
> >> Any comment on this patch?
> >> It does really help with stack pressure and will help
Eric, sorry for delay.
On 05/29, Eric W. Biederman wrote:
>
> Oleg Nesterov writes:
>
> > Why the empty "." + ".." dir is bad if the task(s) has gone away after
> > opendir?
>
> Because the definition of a deleted directory that you are in is that
> getdents will return -ENOENT.
>
> You can
On 05/31/2013 04:29 AM, Ian Campbell wrote:
> This affects arch/powerpc/boot/dts/virtex440-ml510.dts but I think it is
> actually a more general issue:
>
> $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux- virtex440-ml510.dtb
> CC scripts/mod/devicetable-offsets.s
>
On Fri, 31 May 2013, Will Deacon wrote:
> Hard to tell without context. You can take a look at my git tree if you
> like (I fixed it up based on Nico's comment):
>
>
> https://git.kernel.org/cgit/linux/kernel/git/will/linux.git/commit/?h=misc-patches
If you like, you may add "Reviewed-by:
Not sure if this is a big deal or not. I've got an old version of
trace-cmd. It was built from git on 2012-09-12 but sadly I didn't
stash away the exact commit hash. Anyway this version works fine on a
3.4 kernel but on a 3.10-rc3 kernel it no longer works. I just pulled
the latest trace-cmd
On 05/31/2013 05:16 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 15:57 Fri 31 May , Michal Simek wrote:
>> On 05/31/2013 01:00 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
>>> On 10:14 Fri 31 May , Michal Simek wrote:
Hi Jean-Christophe,
On 05/30/2013 10:17 PM,
On Fri, May 31, 2013 at 05:48:56PM +0100, Nicolas Pitre wrote:
> On Fri, 31 May 2013, Will Deacon wrote:
>
> > Hard to tell without context. You can take a look at my git tree if you
> > like (I fixed it up based on Nico's comment):
> >
> >
> >
On Fri, 2013-05-31 at 18:33 +0400, Sergei Shtylyov wrote:
> On 31-05-2013 9:20, Joe Perches wrote:
> > Don't use a standalone gcc compiled program to
> > determine what the kernel outputs.
[]
> > The kernel output is;
>
> > printk("0x%lx\n", 0x100ul) 0x100
> > printk("%p\n",
On 05/31/2013 09:58 AM, Shuah Khan wrote:
> Convert drivers/rtc/class to use dev_pm_ops for power management and
> remove Legacy PM ops hooks. With this change, rtc class registers
> suspend/resume callbacks via class->pm (dev_pm_ops) instead of Legacy
> class->suspend/resume. When
Hi Hebbar,
On Fri, May 31, 2013 at 03:43:00PM +0530, Hebbar Gururaja wrote:
> By optionally putting the pins into sleep state in the suspend [or in
> runtime_suspend] callback we can accomplish two things.
> - One is to minimize current leakage from pins and thus save power,
> - second, we can
On Fri, 2013-05-31 at 11:50 -0500, Shawn Bohrer wrote:
> Not sure if this is a big deal or not. I've got an old version of
> trace-cmd. It was built from git on 2012-09-12 but sadly I didn't
> stash away the exact commit hash. Anyway this version works fine on a
> 3.4 kernel but on a 3.10-rc3
On Fri, 2013-05-31 at 16:34 +0200, Takashi Iwai wrote:
> Also, another expected problem is that neither card->card_dev nor
> card->dev are set when snd_card_err() is called. Many drivers set the
> device pointers at the late stage just before the device
> registration. So, systematic
Convert drivers/rtc/class to use dev_pm_ops for power management and
remove Legacy PM ops hooks. With this change, rtc class registers
suspend/resume callbacks via class->pm (dev_pm_ops) instead of Legacy
class->suspend/resume. When __device_suspend() runs call-backs, it will
find class->pm ops
On Fri, May 31, 2013 at 01:05:35PM -0400, Steven Rostedt wrote:
> On Fri, 2013-05-31 at 11:50 -0500, Shawn Bohrer wrote:
> > Not sure if this is a big deal or not. I've got an old version of
> > trace-cmd. It was built from git on 2012-09-12 but sadly I didn't
> > stash away the exact commit
On Fri, May 31, 2013 at 09:18:07AM -0700, Kees Cook wrote:
> Fix various weird constructions of strncpy(dst, src, strlen(src)). Length
> limits should be about the space available in the destination, not
> repurposed as a method to either always include or always exclude
> a trailing NULL byte.
From: Stephen Warren
Previously, the #line parsing regex ended with ({WS}+[0-9]+)?. The {WS}
could match line-break characters. If the #line directive did not contain
the optional flags field at the end, this could cause any integer data on
the next line to be consumed as part of the #line
On 05/29, Andrew Morton wrote:
>
> On Fri, 24 May 2013 19:39:25 +0200 Oleg Nesterov wrote:
>
> > audit_log_start() does wait_for_auditd() in a loop until
> > audit_backlog_wait_time passes or audit_skb_queue has a room.
> >
> > If signal_pending() is true this becomes a busy-wait loop,
> >
Oleksandr Dmytryshyn writes:
> On 05/30/2013 07:46 PM, Kevin Hilman wrote:
>> Oleksandr Dmytryshyn writes:
>>
>>> If the i2c controller during suspend will generate an interrupt, it
>>> can lead to unpredictable behaviour in the kernel.
>>>
>>> Based on the logic of the kernel code interrupts
On 05/31/2013 04:14 AM, Ian Campbell wrote:
> Various temporary files used when building DTB files were not suffixed with
> .tmp and therefore were not cleaned up by "make clean".
Reviewed-by: Stephen Warren
Tested-by: Stephen Warren
--
To unsubscribe from this list: send the line "unsubscribe
On Fri, 31 May 2013, Christian Ruppert wrote:
> The SOC interrupt controller driver for the Abilis Systems TB10x series of
> SOCs based on ARC700 CPUs.
>
> This patch depends on commits eb76bdd407d8a90e59a06cb0158886df390e5d1c and
> 712bc93df9e7f14b8a163148d2aa7c778e151627 from branch
Hebbar Gururaja writes:
> Amend the I2C omap pin controller to optionally take a pin control
> handle and set the state of the pins to:
>
> - "default" on boot, resume and before performing an i2c transfer
> - "idle" after initial default, after resume default, and after each
> i2c xfer
> -
On Fri, 2013-05-31 at 17:28 +0100, Matthew Garrett wrote:
> On Fri, May 31, 2013 at 10:43:49AM -0500, Russ Anderson wrote:
>
> > When did writing EFI variables to nvram become necessary to boot on
> > UEFI? And if it is necessary, why is it that only linux boot loaders
> > that use EFI stubs
Stephen Warren writes:
> Fix this by replacing {WS} with [ \t] so that it can't match line-breaks.
I think the other uses of {WS} shouldn't span lines either.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now
Hebbar Gururaja writes:
> On some platforms (like AM33xx), a special register (RTC_IRQWAKEEN)
> is available to enable Wakeup feature for Alarm Events.
>
> Since new platforms/Boards are now added through DT only, this feature
> is supported via DT property only.
> Platforms using such IP
On 05/31/2013 11:38 AM, Andreas Schwab wrote:
> Stephen Warren writes:
>
>> Fix this by replacing {WS} with [ \t] so that it can't match line-breaks.
>
> I think the other uses of {WS} shouldn't span lines either.
That is true, but only the optional occurrence /should/ matter. Any
changes to
Add check for error pointers returned from get_node_page in order to
avoid dereferencing a bad address on the next use.
Signed-off-by: Jason Hrycay
---
fs/f2fs/xattr.c | 4
1 file changed, 4 insertions(+)
diff --git a/fs/f2fs/xattr.c b/fs/f2fs/xattr.c
index 0b02dce..ae61f35 100644
---
Hebbar Gururaja writes:
> Even though RTC-IP is wakeup capable, Not all Boards support it.
>
> For example
> The rtc alarm wakeup is available in rtc-ip since omap1 days but alarm
> was not wired properly in previous ompa1 boards.
>
> commit fa5b07820fe3a0fc06ac368516e71f10a59b9539
>
Hello.
On 05/31/2013 08:54 PM, Joe Perches wrote:
Don't use a standalone gcc compiled program to
determine what the kernel outputs.
[]
The kernel output is;
printk("0x%lx\n", 0x100ul)0x100
printk("%p\n", (void *)0x100ul) 0100
Comments have been light for this round so I think we're about
ready to merge. John/Thomas, can you pick up these patches or
shall I route them through arm-soc or something else?
On 05/13, Stephen Boyd wrote:
> In light of Mark Rutland's recent work on divorcing the ARM architected
> timers from
At Fri, 31 May 2013 17:32:16 +0200,
Alex Riesen wrote:
>
> On Fri, May 31, 2013 at 3:05 PM, Takashi Iwai wrote:
> > Below is a series of patches. For simplicity, I just attach them, not
> > inlining to the mail. They should be applicable cleanly to 3.9.4 as
> > well. Let me know if this
+ Linus W. (pinctrl maintainer)
Dmitry Torokhov writes:
> Hi Hebbar,
>
> On Fri, May 31, 2013 at 03:43:00PM +0530, Hebbar Gururaja wrote:
>> By optionally putting the pins into sleep state in the suspend [or in
>> runtime_suspend] callback we can accomplish two things.
>> - One is to minimize
On 05/31/2013 10:45 AM, Stephen Boyd wrote:
Comments have been light for this round so I think we're about
ready to merge. John/Thomas, can you pick up these patches or
shall I route them through arm-soc or something else?
So there looks to be a fair amount of additions in the ARM tree, do
It turns out, the bug I spent yesterday chasing in various 3.9 kernels is
apparently
fixed by the commit in the title (c9c390bb5535380d40614571894ef0c00bc026ff).
Fortunately, Joe Lawrence somehow saw my email to lkml and pointed me to the
bug report below, which mentions the commit...
Oleg Nesterov writes:
> Eric, sorry for delay.
>
> On 05/29, Eric W. Biederman wrote:
>>
>> Oleg Nesterov writes:
>>
>> > Why the empty "." + ".." dir is bad if the task(s) has gone away after
>> > opendir?
>>
>> Because the definition of a deleted directory that you are in is that
>> getdents
Tushar Behera writes:
> There are two definitions for low-level UART ports for Exynos platform.
> CONFIG_S3C_LOWLEVEL_UART_PORT is used for printing "Uncompressing
> Linux... done, booting the kernel." and CONFIG_S3C_UART for other
> low-level messages.
>
> The assumption for both the uart ports
From: Stephen Warren
Previously, the #line parsing regex ended with ({WS}+[0-9]+)?. The {WS}
could match line-break characters. If the #line directive did not contain
the optional flags field at the end, this could cause any integer data on
the next line to be consumed as part of the #line
Acked-by: Mike Frysinger
-mike
signature.asc
Description: This is a digitally signed message part.
On 05/31, Eric W. Biederman wrote:
>
> Oleg Nesterov writes:
>
> > OK. But this means that even 1/3 is not 100% right, exactly because
> > leader can be unhashed right before first_tid() takes rcu lock. Easy
> > to fix, we should simply factor out the "nr != 0" check.
> >
> > And this also means
On 05/13, Stephen Boyd wrote:
> Separate the marco local timers from the local timer API. This
> will allow us to remove ARM local timer support in the near future
> and gets us closer to moving this driver to drivers/clocksource.
>
> Cc: Barry Song
> Signed-off-by: Stephen Boyd
> ---
Barry,
From: Dave Hansen
changes for v2:
* remove batch_has_same_mapping() helper. A local varible makes
the check cheaper and cleaner
* Move batch draining later to where we already know
page_mapping(). This probably fixes a truncation race anyway
* rename batch_for_mapping_removal ->
From: Dave Hansen
This patch defers the destruction of swapcache-specific data in
'struct page'. This simplifies the code because we do not have
to keep extra copies of the data during the removal of a page
from the swap cache.
There are only two callers of swapcache_free() which actually
From: Dave Hansen
Our goal here is to eventually reduce the number of repetitive
acquire/release operations on mapping->tree_lock.
Logically, this patch has two steps:
1. rename __remove_mapping() to lock_remove_mapping() since
"__" usually means "this us the unlocked version.
2. Recreate
These are an update of Tim Chen's earlier work:
http://lkml.kernel.org/r/1347293960.9977.70.camel@schen9-DESK
I broke the patches up a bit more, and tried to incorporate some
changes based on some feedback from Mel and Andrew.
Changes for v4:
* generated on top of linux-next-20130530,
From: Dave Hansen
__remove_mapping() only deals with pages with mappings, meaning
page cache and swap cache.
At this point, the page has been removed from the mapping's radix
tree, and we need to ensure that any fs-specific (or swap-
specific) resources are freed up.
We will be using this
From: Dave Hansen
swapcache_free() takes two arguments:
void swapcache_free(swp_entry_t entry, struct page *page)
Most of its callers (5/7) are from error handling paths haven't even
instantiated a page, so they pass page=NULL. Both of the callers
that call in with a 'struct page'
From: Dave Hansen
This was a suggestion from Mel:
http://lkml.kernel.org/r/20120914085634.gm11...@csn.ul.ie
Any pages we collect on 'batch_for_mapping_removal' will have
their lock_page() held during the duration of their stay on the
list. If some other user is trying to get at them
On 05/31/2013 02:59 AM, Srinivas KANDAGATLA wrote:
From: Srinivas Kandagatla
This patch adds "Clocksource drivers" menu to clocksource drivers.
The reason to add this is because, some of the clocksource Kconfig
options like *SHED_CLK ones are selectable and they appear at random
places in the
Signed-off-by: Jan Luebbe
---
This patch depends on my two recent pps-gpio patches, which are currently
in Andrew Morton's mmotm. So it should probably also go via Andrew if it
is acceptable.
Documentation/devicetree/bindings/pps/pps-gpio.txt | 20 +++
drivers/pps/clients/pps-gpio.c
Hi Matthew,
A bug was opened that reports a regression that prevents a system from
booting[0]. After a kernel bisect, it was found that reverting the
following commit resolved this bug:
commit 68d929862e29a8b52a7f2f2f86a0600423b093cd
Author: Matthew Garrett
Date: Sat Mar 2 19:40:17 2013
Git bisect pointed me to the following commit as the first bad commit
> (linux-next tree of 20130531):
>
> commit 3d5272d9b289cd0930b2ea9984406d757a72f4dd
> Author: Chanho Min
> Date: Thu May 23 10:37:28 2013 +1000
> lib/bitmap.c: speed up bitmap_find_free_region
>
> R
The KDIV value is often listed as unsigned but it needs to be treated
as a 16-bit signed value when using it in calculations. Fix our rate
recalculation to do this correctly.
Before doing this, I tried setting EPLL on exynos5250 to:
rate, m, p, s, k = 8000, 107, 2, 4, 43691
This rate is
Hi,
we recently encountered some kernel panics when we compiled one of our
drivers as module and tested inserting/removing the module.
Trying to debug this issue, I could reproduce it on the mainline kernel
with a dummy module.
What happens is, that when on driver remove
On Friday 31 May 2013 20:46:55 Jan Luebbe wrote:
>
> +#ifdef CONFIG_OF
> +static const struct of_device_id pps_gpio_dt_ids[] = {
> + { .compatible = "pps-gpio", },
> + { /* sentinel */ }
> +};
> +MODULE_DEVICE_TABLE(of, pps_gpio_dt_ids);
> +
> +static struct pps_gpio_platform_data *
>
1101 - 1200 of 1386 matches
Mail list logo
