On Thu, May 09, 2013 at 03:15:59PM -0700, Sarah Sharp wrote:
> On Tue, May 07, 2013 at 04:03:33PM +0200, Frantisek Hrbata wrote:
> > Hi,
>
> Hi Frantisek,
>
> > there is a NULL pointer dereference in xhci_free_dev if
> > xhci_alloc_dev timeouts while waiting for a slot. Fedora has several bugs
>
On 05/10/2013 02:28 AM, Olof Johansson wrote:
> This turns on a number of configs that are useful on the Chromebook, but also
> good to have on in general:
>
> * USB host and MMC drivers(!)
> * I2C GPIO arbitration driver
> * CYAPA trackpad driver
> * simplefb
> * CROS EC and keyboard drivers
> *
Hi Linus,
The following changes since commit c1be5a5b1b355d40e6cf79cc979eb66dafa24ad1:
Linux 3.9 (2013-04-28 17:36:01 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git
tags/ecryptfs-3.10-rc1-ablkcipher
for you to fetch change
Current MMC driver does not recognize the general error (bit19 of device
status) in write command sequence.
So the host might ignore the general error.
This patch adds the code which checks the response of CMD12/CMD13 in write
command sequence and retry the write command sequence if the error is
re
Commit c0114709ed ("irqchip: gic: Perform the gic_secondary_init()
call via CPU notifier") removed all platform calls to gic_secondary_init.
Since this file got merged after the removal of the above call, this
function got left out in the current file which is causing the following
build error:
arc
fix goto wrong tag in usb_hcd_nxp_probe
* Changelog from v1:
* instead of all these statement labels suggested by Alan Stern
Signed-off-by: Libo Chen
---
drivers/usb/host/ohci-nxp.c | 46 +-
1 files changed, 23 insertions(+), 23 deletions(-)
diff -
Several syscall-related commits that were missing from the original
pull request. Please, pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/signal for-linus
Shortlog:
Al Viro (3):
unify compat fanotify_mark(2), switch to COMPAT_SYSCALL_DEFINE
unicore32: just use mmap_pgoff()
On Tue, 2013-05-07 at 10:20 -0700, Greg KH wrote:
> > But yesterday, I got a message from a different user with screen
> > captures that showed failure of loading the firmware below.
> > Actually, one screen shot with the 7.0.23.0 and another with the
> > 7.0.29.0. Wasn't sure, so I had added a
Hi Linus,
please pull these changes to you tree.
Thanks,
Michal
The following changes since commit e0fd9affeb64088eff407dfc98bbd3a5c17ea479:
Merge tag 'rdma-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband (2013-05-08
15:29:48 -0700)
are available in the git r
Dave Chinner writes:
>> tux3:
>> Operation CountAvgLatMaxLat
>>
>> NTCreateX1477980 0.00312.944
>
>> ReadX2316653 0.002 0.499
>> LockX 4812 0.002 0.207
>> UnlockX
On Fri, May 10, 2013 at 5:40 AM, quickbooks office
wrote:
> On Wed, May 8, 2013 at 8:40 AM, Josh Boyer wrote:
>> On Wed, May 8, 2013 at 12:09 AM, quickbooks office
>> wrote:
>>> Please Merge VirtualBox Kernel Modules into the Kernel.
>>>
>>> --
Aloha hardcore coders
Thank you very much for working out the facts, Dave.
You proved why I had all the years such a special suspicious feeling by
reading between the lines of the Tux3 e-mails sent to the mailing-list,
which should not mean that I do not like the work around the Tux3 file
sys
On Fri, May 10, 2013 at 01:19:26PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the akpm tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/md/bcache/super.c:656:2: warning: initialization from incompatible
> pointer type [enabled by default]
On Tue, May 07, 2013 at 04:24:05PM -0700, Daniel Phillips wrote:
> When something sounds to good to be true, it usually is. But not always. Today
> Hirofumi posted some nigh on unbelievable dbench results that show Tux3
> beating tmpfs. To put this in perspective, we normally regard tmpfs as
> unbe
From: Lad, Prabhakar
The error path on failure was calling mutex_unlock(), but there was
no actuall call before for mutex_lock(). This patch fixes this issue
by pointing it to proper go label.
Reported-by: Jose Pablo Carballo
Signed-off-by: Lad, Prabhakar
---
drivers/media/platform/davinci/vp
The TD Size field in an XHCI TRB is calculated in two different ways,
depending on the XHCI version. The current code does this version check
in every caller, which makes it easy to forget (such as in the function
for control transfers, which still erroneously uses the old calculation
for its data
On Wed, 2013-05-08 at 11:36 +0100, Luis Henriques wrote:
> On Tue, Apr 30, 2013 at 05:44:01PM +0900, Jonghwan Choi wrote:
> > This patch looks like it should be in the 3.8-stable tree, should we apply
> > it?
>
> This commit seems to be applicable to other stable trees as well (3.0,
> 3.2, 3.5, ..
On 7 May 2013 at 10:20, Greg KH wrote:
Date sent: Tue, 7 May 2013 10:20:10 -0700
From: Greg KH
To: "Michael D. Setzer II"
Copies to: linux-kernel@vger.kernel.org
Subject:Re: Kernel Firmware Support
> On Tue, May 07,
On 05/10/2013 05:21 AM, Alexandre Courbot wrote:
>
> /me likes regexps. You should see my workaround to using the -i option.
>
> Thanks for the merge, it clears the path for more GPIO stuff. arch/arc
> introduced a new dangling definition of GENERIC_GPIO in -next that now
> appears in your tree, th
The hard-coded path of modprobe doesn't allow distros to put the binary
in another place without add links from one place to another. For
example, in recent versions of distros like Fedora, Arch and Suse, kmod
is the default tool to load modules and they have to create a link from
modprobe to kmod
Now that argv_split() leaves room for extra parameter, make
call_modprobe() use it.
Signed-off-by: Lucas De Marchi
---
kernel/kmod.c | 19 ---
1 file changed, 8 insertions(+), 11 deletions(-)
diff --git a/kernel/kmod.c b/kernel/kmod.c
index 166aff5..70df90b 100644
--- a/kernel/k
Add an argument allowing argv_split to leave room for parameters to be
filled by the caller. This is useful in situations we want to split the
command and add a options as the last arguments.
Signed-off-by: Lucas De Marchi
---
fs/coredump.c | 2 +-
include/linux/string.h
On Thu, 2013-05-02 at 14:52 +0200, Jiri Slaby wrote:
> On 04/26/2013 06:30 AM, Greg KH wrote:
> > Linus Torvalds (5): vm: add vm_iomap_memory() helper function
>
> Hi, this one breaks s390 on 3.0:
> mm/memory.c: In function 'vm_iomap_memory':
> mm/memory.c:2363: error: implicit declaration of func
Sergei Shtylyov :
>> Agreed. I just thought it's better to make it similar to the
>> rtl821x_ack_interrupt.
>
>Ah, then you may leave this code as is.
>
>> Then, may I make shorter the rtl821x_ack_interrupt as well as
>> rtl8201f_ack_interrupt?
>
>In a separate patch, if you wish.
>
Tha
Hi all,
Please do not add any v3.11 destined work to your linux-next included
branches until after v3.10-rc1 is released.
Changes since 20130509:
New tree: parisc-hd (currently empty)
The akpm tree lost a few patches that turned up elsewhere
On Wed, May 8, 2013 at 8:40 AM, Josh Boyer wrote:
> On Wed, May 8, 2013 at 12:09 AM, quickbooks office
> wrote:
>> Please Merge VirtualBox Kernel Modules into the Kernel.
>>
>> ---
>>
>> svn co
On 2013-05-08, Matthew Garrett wrote:
> On Tue, 2013-05-07 at 22:55 +0800, Qiaowei Ren wrote:
>
> > + * This module is expected to be a better tool to access below
> > + resources
>
> Expected to be or is? :)
"is" :)
> > + * Data is currently found below
>
> You're adding it to ABI, so it shou
Hi all,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/md/bcache/super.c:656:2: warning: initialization from incompatible
pointer type [enabled by default]
drivers/md/bcache/super.c:656:2: warning: (near initialization for
'bcache_ops.
Hi Andrew,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
drivers/block/nvme-core.c: In function 'nvme_bio_split':
/scratch/sfr/next/drivers/block/nvme-core.c:483:19: warning: assignment from
incompatible pointer type [enabled by default]
/sc
On Fri, May 10, 2013 at 8:27 AM, Stephen Rothwell wrote:
> On Thu, 9 May 2013 14:53:42 -0700 Linus Torvalds
> wrote:
>>
>> Hmm. I'm used to pull blackfin updates from Bob Liu. I see that he has
>> signed your gpg key, so this all looks fine, but quite frankly, Id'
>> much rather be told ahead of
Hi Linus,
On Fri, May 10, 2013 at 5:53 AM, Linus Torvalds
wrote:
> Hmm. I'm used to pull blackfin updates from Bob Liu. I see that he has
> signed your gpg key, so this all looks fine, but quite frankly, Id'
> much rather be told ahead of time that "oh, expect pulls from another
> person".
>
> I
Hi Stephen,
Yes, please update the current blackfin tree with:
https://github.com/realmz/blackfin-linux.git blackfin-linus
Thanks!
-steven
On Fri, May 10, 2013 at 8:27 AM, Stephen Rothwell wrote:
> On Thu, 9 May 2013 14:53:42 -0700 Linus Torvalds
> wrote:
>>
>> Hmm. I'm used to pull blac
On 08/05/13 10:44 -0700, Randy Dunlap wrote:
> On 05/08/13 08:23, Phil Carmody wrote:
> > I've got a tweaked version as well as the system default,
> > so make the sparse binary that's run user-selectable.
> >
>
> I'm confused about why this patch is necessary since I already do
>
> $ make O=bui
On Thu, May 9, 2013 at 8:23 PM, Eduardo Valentin
wrote:
> On 07-05-2013 09:01, Amit Daniel Kachhap wrote:
>> This patch adds support to handle multiple instances of the TMU controllers.
>> This is done by removing the static structure to register with the core
>> thermal
>> and creating it dynami
Hi Eduardo,
On Thu, May 9, 2013 at 8:17 PM, Eduardo Valentin
wrote:
> Hey Amit,
>
> On 07-05-2013 09:01, Amit Daniel Kachhap wrote:
>> This patch modifies TMU controller to add changes needed to work with
>> exynos5440 platform. Also register definitions and required configuration
>> data
>> are
Hi Eduardo,
On Thu, May 9, 2013 at 8:14 PM, Eduardo Valentin
wrote:
> On 07-05-2013 09:01, 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.
>>
>> Sign
Hi,
On Thu, May 9, 2013 at 8:03 PM, Eduardo Valentin
wrote:
> On 07-05-2013 09:01, Amit Daniel Kachhap wrote:
>> This patch uses the TMU status register to know the generated interrupts
>> and only clear them in the interrupt handler.
>>
>> Acked-by: Kukjin Kim
>> Signed-off-by: Amit Daniel Kach
On 2013-05-09, Matthew Garrett wrote:
> On Thu, 2013-05-09 at 08:19 +, Ren, Qiaowei wrote:
> > On 2013-05-08, Matthew Garrett wrote:
> > > On Tue, 2013-05-07 at 22:55 +0800, Qiaowei Ren wrote:
> > >> This module is expected to be a better tool to access below resources
> > >> - TXT config spa
Hi Eduardo,
On Thu, May 9, 2013 at 8:02 PM, Eduardo Valentin
wrote:
> Hey Amit,
>
> On 07-05-2013 09:00, Amit Daniel Kachhap wrote:
>> This patch migrates the TMU register definition/bitfields to data file. This
>> is needed to support SoC's which use the same TMU controller but register
>> valid
On Tue, 2013-04-23 at 14:52 -0700, Greg Kroah-Hartman wrote:
> 3.8-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: libin
>
> commit fd9b86d37a600488dbd80fe60cca46b822bff1cd upstream.
>
> Commit 201c373e8e ("sched/debug: Limit sd->*_idx r
Hi,
On Thu, May 9, 2013 at 7:22 PM, Eduardo Valentin
wrote:
> Amit,
>
> On 07-05-2013 09:00, 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 05/10/2013 04:11 AM, Andrew Morton wrote:
>> > But we need let 'rule->tree = NULL;' firstly, so can protect rule itself
>> > freed in kill_rules().
> I'll believe you ;) I turned this into a proper patch and added your
> (missed) Signed-off-by:.
>
Thanks.
At least, let 'rule->tree = NULL;' c
On Tue, 2013-04-23 at 11:56 +0100, Luis Henriques wrote:
> On Tue, Apr 23, 2013 at 11:57:51AM +0900, Jonghwan Choi wrote:
> > 3.8-stable review patch. If anyone has any objections, please let me know.
>
> Thanks, I believe this is also applicable to 3.2.y, 3.4.y and 3.5.y.
I agree; I've queued t
Hi Eduardo,
On Thu, May 9, 2013 at 7:09 PM, Eduardo Valentin
wrote:
> Hey Amit,
>
> On 07-05-2013 09:00, 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 to the same TMU controller.
>
> I lik
On Thu, 9 May 2013 15:32:23 +0200, Jiri Olsa wrote:
> Adding ABI documentation for newly added 'precise' sysfs
> attribute. It's added under the testing section.
>
> Signed-off-by: Jiri Olsa
> Cc: Corey Ashford
> Cc: Frederic Weisbecker
> Cc: Ingo Molnar
> Cc: Namhyung Kim
> Cc: Paul Mackerr
Hi, Girdwood
When I try to fix wm1811 standby issue for our customer, I find a strange
behavior in ASOC core.
here is my test code:
snd_soc_dapm_disable_pin(&dapm,"MICBIAS2");
snd_soc_dapm_disable_pin(&dapm,"CLK_SYS");
snd_soc_dapm_sync(&dapm);
and add debug info in dapm_pre_sequence_async()
Hi,
On Thu, May 9, 2013 at 6:58 PM, Eduardo Valentin
wrote:
> Hello Amit,
>
> On 07-05-2013 09:00, 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 a
On Thu, 9 May 2013 15:32:20 +0200, Jiri Olsa wrote:
> If single 'p' modifier is specified for event, set the
> system precise value for perf_events_attr::precise_ip.
>
> If more than a single 'p' is specified keep the intended
> value.
So there's no way to set precise=1 on a system suppports prec
On 2013/5/10 9:09, Libo Chen wrote:
> On 2013/5/10 2:02, Chris Metcalf wrote:
>> On 5/9/2013 2:08 AM, Libo Chen wrote:
>>> When usb_create_hcd fail, we should call gxio_usb_host_destroy
>>>
>>> Signed-off-by: Libo Chen
>>> ---
>>> drivers/usb/host/ohci-tilegx.c |7 +--
>>> 1 files changed
On Thu, May 09, 2013 at 05:53:08PM +0300, Felipe Balbi wrote:
> On Thu, May 09, 2013 at 06:29:51PM +0800, Dave Young wrote:
> > On Tue, May 07, 2013 at 03:25:58AM -0400, CAI Qian wrote:
> > > Never saw any of those messages were floating in any of the RC testing,
> > > but
> > > now happened in 3.
On 2013-05-09, Matthew Garrett wrote:
> On Thu, 2013-05-09 at 08:05 +, Ren, Qiaowei wrote:
> > On 2013-05-08, Matthew Garrett wrote:
> > > How different are these logs to the TPM measurements exported via
> > > securityfs?
> >
> > These logs come from tboot (Trusted Boot, an open source, pre-ke
On Thu, 9 May 2013 15:32:19 +0200, Jiri Olsa wrote:
> From: Andi Kleen
>
> Add a precise qualifier, like cpu/event=0x3c,precise=1/
>
> This is needed so that the kernel can request enabling PEBS
> for TSX events. The parser bails out on any sysfs parse errors,
> so this is needed in any case to h
On 5/9/13 7:10 PM, Namhyung Kim wrote:
I think we should not truncate file_size for this case. It was
decreased to data_offset + data_size in order not to read unrelated
metadata (additional header feature info). But in this case, since
data_size is 0 it'd have same value as data_offset, and i
(2013/05/10 2:08), Steven Rostedt wrote:
> On Thu, 2013-05-09 at 12:34 -0400, Steven Rostedt wrote:
>> On Thu, 2013-05-09 at 12:27 -0400, Steven Rostedt wrote:
>>
>>> We probably should have a better way to initialize this. As there are 26
>>> ftrace_ops currently in the kernel (and this patch does
Hi Jiri,
On Thu, 9 May 2013 15:32:17 +0200, Jiri Olsa wrote:
> Adding precise util object to get maximum value for
> perf_event_attr::precise_ip. The value is exported
> via sysfs file '/sys/devices/cpu/precise'.
>
> The interface is:
> int perf_precise__get(void)
I think Arnaldo wants to use
On Fri, May 10, 2013 at 1:04 AM, Takashi Iwai wrote:
> At Thu, 9 May 2013 16:43:28 +0800,
> Ming Lei wrote:
>>
>> On Thu, May 9, 2013 at 3:31 PM, Takashi Iwai wrote:
>> > At Thu, 9 May 2013 09:25:35 +0800,
>> > Ming Lei wrote:
>> >>
>> >> On Thu, May 9, 2013 at 1:51 AM, Takashi Iwai wrote:
>> >>
On Thu, May 9, 2013 at 4:44 PM, Jerome Glisse wrote:
> On Thu, May 9, 2013 at 3:46 PM, Andy Lutomirski wrote:
>> A fair number of drivers (mostly graphics) add write-combining MTRRs.
>> Most ignore errors and most add the MTRR even on PAT systems which don't
>> need to use MTRRs.
>
> This comment
Hi Ingo,
On Thu, 9 May 2013 11:30:25 +0200, Ingo Molnar wrote:
> * Ingo Molnar wrote:
>> Btw., would it make sense to emit a (once-only) warning and optimistically
>> fix page_offset up to 1 (or 4096) and let things continue with the next
>> set of data - can we recover most of the data in that
On 2013/5/10 2:02, Chris Metcalf wrote:
> On 5/9/2013 2:08 AM, Libo Chen wrote:
>> When usb_create_hcd fail, we should call gxio_usb_host_destroy
>>
>> Signed-off-by: Libo Chen
>> ---
>> drivers/usb/host/ohci-tilegx.c |7 +--
>> 1 files changed, 5 insertions(+), 2 deletions(-)
>
> Thanks
> the economics of market forces don't work that way.
> profit-maximising companies are pathologically and *LEGALLY* bound to
> enact the articles of incorporation. so you'd need to show them that
> it would hurt their profits to continue the way that they are going.
I think legally bound is a myth
> From: yuhongbao_...@hotmail.com
> To: l...@lkcl.net; hancock...@gmail.com
> CC: david.goodeno...@btconnect.com; debian-...@lists.debian.org;
> linux-kernel@vger.kernel.org; arm-netb...@lists.phcomp.co.uk
> Subject: RE: device tree not the answer in the AR
On 2013/5/9 16:33, Zhang, Sonic wrote:
> Hi Libo,
>
>> -Original Message-
>> From: Libo Chen [mailto:libo.c...@huawei.com]
>> Sent: Thursday, May 09, 2013 4:27 PM
>> To: Zhang, Sonic; w...@the-dreams.de
>> Cc: uclinux-dist-de...@blackfin.uclinux.org; linux-kernel@vger.kernel.org;
>> linux
> Can you give us the full crash message, (i.e., the panic, the BUG,
> WARN, the registers, etc.), and not the stack trace?
> - Ted
Hi, Ted
Actually i try to find the crash point. And i confirmed crash point is in
__journal_remove_journal_head() function.
I added some debu
On Thu, May 09, 2013 at 06:12:17PM +0200, Yann E. MORIN wrote:
> Wang, All,
>
> On Thu, May 09, 2013 at 11:27:31PM +0800, Wang YanQing wrote:
> > On Mon, May 06, 2013 at 11:15:31PM +0200, Yann E. MORIN wrote:
> > > From: "Yann E. MORIN"
> > >
> > > When searching for symbols, return the symbols
On Thu, 2013-05-09 at 20:47 -0400, Steven Rostedt wrote:
> >
> > > +
> > > + local_irq_enable();
> > > + __schedule();
> >
> > Are you sure it's fine to call __schedule() instead of schedule()?
> > I don't know much about the blk work to handle there but it may be
> > worth considering.
>
> Not
On Fri, 2013-05-10 at 02:22 +0200, Frederic Weisbecker wrote:
>
> > @@ -654,6 +653,7 @@ sysret_check:
> > LOCKDEP_SYS_EXIT
> > DISABLE_INTERRUPTS(CLBR_NONE)
> > TRACE_IRQS_OFF
> > +sysret_check_irqsoff:
> > movl TI_flags+THREAD_INFO(%rsp,RIP-ARGOFFSET),%edx
> > andl %edi,%edx
On 5/9/13 6:28 PM, Namhyung Kim wrote:
Hi David,
On Thu, 09 May 2013 07:54:26 -0600, David Ahern wrote:
On 5/9/13 2:51 AM, Ingo Molnar wrote:
2)
Another suggestion: it would be nice to allow a "--repeat " option as
well, for a limited number of iterations - similar to what the 'top' tool
allo
On Thu, May 09, 2013 at 02:29:18PM +0200, Jiri Kosina wrote:
> Hi,
>
> I just got the warning below when resuming from hibernation with kernel
> that has NO_HZ_FULL_ALL=y. This is with topmost commit e0fd9affeb640.
>
>
> [ ... snip ... ]
> PM: Hibernation mode set to 'shutdown'
> PM: Marking
Hi David,
On Thu, 09 May 2013 07:54:26 -0600, David Ahern wrote:
> On 5/9/13 2:51 AM, Ingo Molnar wrote:
>> 2)
>>
>> Another suggestion: it would be nice to allow a "--repeat " option as
>> well, for a limited number of iterations - similar to what the 'top' tool
>> allows:
>>
>>top -b -d -n
This patch looks like it should be in the 3.9-stable tree, should we apply
it?
--
From: "Inderpal Singh "
commit 088584618836b159947bc4ab5011a5cf1f081a62 upstream
The kernel crashes while resuming from AFTR idle mode. It happens
because L2 cache was not going into retention stat
On Thu, 9 May 2013 14:53:42 -0700 Linus Torvalds
wrote:
>
> Hmm. I'm used to pull blackfin updates from Bob Liu. I see that he has
> signed your gpg key, so this all looks fine, but quite frankly, Id'
> much rather be told ahead of time that "oh, expect pulls from another
> person".
>
> I do *no
Hi Jassi,
>
> On 9 May 2013 06:55, Suman Anna wrote:
>
>>> so it can't be driven by the controller. We could make it a Kconfig option.
>>> What do you suggest?
>>
>> I am saying controller/link because they are the ones that knows how the
>> physical transport is, and it may vary from one to anot
On Wed, May 08, 2013 at 09:21:20PM -0400, Steven Rostedt wrote:
> I started testing the new NOHZ_FULL in the kernel and had some issues,
> so I started function tracing and this bug report came out:
>
>
> [23446.458073] [ cut here ]
> [23446.461028] WARNING:
> at /home/ros
Hi Helge,
On Thu, 09 May 2013 22:31:04 +0200 Helge Deller wrote:
>
> On 05/08/2013 03:37 AM, Stephen Rothwell wrote:
> > On Wed, 8 May 2013 00:11:02 +0200 Helge Deller wrote:
> >>
> >> please pull the parisc architecture updates for v3.10 from:
> >>
> >> git://git.kernel.org/pub/scm/linux/kern
From: Anton Vorontsov
The FIQ debugger may be used to debug situations when the kernel stuck
in uninterruptable sections, e.g. the kernel infinitely loops or
deadlocked in an interrupt or with interrupts disabled.
By default KGDB FIQ is disabled in runtime, but can be enabled with
kgdb_fiq.enabl
From: Anton Vorontsov
If enabled, kernel will able to enter KGDB upon serial line activity on
UART ports.
Note that even with this patch and CONFIG_KGDB_FIQ is enabled, you still
need to pass kgdb_fiq.enable=1 kernel command line option, otherwise UART
will behave in a normal way.
By default UA
From: Anton Vorontsov
Just move the macros into header file as we would want to use them for
KGDB FIQ entry code.
The following macros were moved:
- svc_entry
- usr_entry
- kuser_cmpxchg_check
- vector_stub
To make kuser_cmpxchg_check actually work across different files, we
also have to m
Hey all,
Just wanted to try to revive Anton's KDB FIQ patches
which have been sent out a number of times since last October
and have gotten almost no response at all.
I've simply updated them to apply to Linus' current HEAD,
and figured I'd send them out again to try to spur some
interest.
On Thu, May 09, 2013 at 01:51:00PM -0700, Andrew Morton wrote:
> On Thu, 9 May 2013 14:23:18 -0500 Robin Holt wrote:
>
> > This patch is preparatory. It moves reboot related syscall, etc
> > functions from kernel/sys.c to kernel/reboot.c.
>
> This doesn't apply.
Weird, I just grabbed a recent
Hi
I have a pincontroller with different pin types
For example pin type A & B. (There are more but 2 is sufficient to
specify here).
Each pin type has its own register programming semantics
So each pin type is associated with its own programming vectors.
Of this lets say pin type A can support
On Fri, May 10, 2013 at 3:11 AM, Grant Likely wrote:
> On Thu, May 9, 2013 at 6:08 PM, Linus Torvalds
> wrote:
>> On Wed, May 8, 2013 at 6:48 AM, Grant Likely wrote:
>>>
>>> * "git grep '\bGENERIC_GPIO\b'" should return 1 hit in the Chinese
>>> documentation.
>>
>> That's the oddest command li
Jassi,
>>>
>>> Perhaps we should change the following
>>>
>>>void ipc_link_txdone(struct ipc_link *link, enum xfer_result r)
>>> to
>>>void ipc_link_txdone(struct ipc_link *link, enum xfer_result r, void
>>> *data)
>>>
>>> So that the API could pass that onto clients ?
>>
>> That's if the
On 05/09/2013 09:14 AM, Lianwei Wang wrote:
> Thank you very much. I have a quick updated patch based on your comments.
>
> diff --git a/drivers/cpuidle/cpuidle.c b/drivers/cpuidle/cpuidle.c
> index 2f0083a..cd1af4b 100644
> --- a/drivers/cpuidle/cpuidle.c
> +++ b/drivers/cpuidle/cpuidle.c
> @@ -1
On Thu, May 9, 2013 at 3:46 PM, Andy Lutomirski wrote:
> A fair number of drivers (mostly graphics) add write-combining MTRRs.
> Most ignore errors and most add the MTRR even on PAT systems which don't
> need to use MTRRs.
This comment is wrong, as i said we need MTRR on PAT system for VRAM.
Che
Doug Anderson wrote:
>
> Tomasz / Olof,
>
Hi Doug, Tomasz and Olof
> On Thu, May 9, 2013 at 2:45 AM, Tomasz Figa wrote:
> >> Nothing stops you from doing that on your own. I tend to push back
> >> onto the maintainers to get them engaged in their own housekeeping,
> >> but anyone is free to :)
If I boot a recent kernel (bb9055b) and run 'perf top' on my machine, it
hangs. It is 100% reproducible; it happens every single time. If I'm
lucky, I'll get some of the hardlockup detection messages on the console.
A little bit of digging showed that the reason it hangs is that we're
seeing an
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: David Jeffery
commit ce8a5dbdf9e709bdaf4618d7ef8cceb91e8adc69 upstream.
When checking if an autofs mount point is busy it isn't sufficient to
only check if it's a mount point.
For example, if
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Axel Lin
commit 563861cd633ae52932843477bb6ca3f1c9e2f78b upstream.
The logic to check return value of clk_enable() and clk_prepare() is reversed,
fix it.
Signed-off-by: Axel Lin
Acked-by: Vir
This is the start of the stable review cycle for the 3.9.2 release.
There are 73 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.
Responses should be made by Sat May 11 22:23:28 UTC 2013.
Anything received
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Suman Anna
commit b9777859ec015a78dae1476e317d04f851bfdd0d upstream.
Fix this:
warning: (VIRTIO_PCI && VIRTIO_MMIO && REMOTEPROC && RPMSG) selects VIRTIO
which has unmet direct dependencies (
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Stefano Stabellini
commit 2798ba7d19aed645663398a21ec4006bfdbb1ef3 upstream.
Signed-off-by: Stefano Stabellini
Reviewed-by: Ian Campbell
Signed-off-by: Greg Kroah-Hartman
---
arch/arm/xen/
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Suman Anna
commit 397944df3290ddc46dcc6a08cd71fb560700431b upstream.
Fix this:
warning: (VIRTIO_PCI && VIRTIO_MMIO && REMOTEPROC && RPMSG) selects VIRTIO
which has unmet direct dependencies (V
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Naoya Horiguchi
commit af73e4d9506d3b797509f3c030e7dcd554f7d9c4 upstream.
The current kernel returns -EINVAL unless a given mmap length is
"almost" hugepage aligned. This is because in sys_mma
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Neuling
commit c2fd22df89365df9451d5b91da3b7bfd48122ecd upstream.
Make sure that current->thread.reg exists before we deference it in
flush_hash_page.
Signed-off-by: Michael Neuling
R
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Benjamin Poirier
commit edb749f4390b3c1604233dc7c4fb0361f472e712 upstream.
Fixes the memory leak of struct jump_key allocated in get_prompt_str()
Signed-off-by: Benjamin Poirier
Tested-by: "Y
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Anton Blanchard
commit 73d2fb758e678c93bc76d40876c2359f0729b0ef upstream.
POWER8 allows read and write of the DSCR in userspace. We added
kernel emulation so applications could always use the i
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Benjamin Herrenschmidt
commit 13f85203e1060da83d9ec1c1c5a63343eaab8de4 upstream.
Some ancient pHyp versions used to create a 8 bytes local-mac-address
property in the device-tree instead of a 6
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Joerg Roedel
commit 197887f03daecdb3ae21bafeb4155412abad3497 upstream.
Fixes a lockdep warning.
Reviewed-by: Shuah Khan
Signed-off-by: Joerg Roedel
Signed-off-by: Greg Kroah-Hartman
---
d
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Vince Weaver
commit 9a6bc14350b130427725f33e371e86212fa56c85 upstream.
According to Intel Vol3b 18.9, the IvyBridge model 58 uncore is
the same as that of SandyBridge.
I've done some simple te
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Vaidyanathan Srinivasan
commit 7122b7bc1757682049780179d7c216dd1c83 upstream.
The following commit breaks numa distance setup for old powerpc
systems that use form0 encoding in device tree.
1 - 100 of 698 matches
Mail list logo