On 03/15/13 14:56, Manolo Díaz wrote:
> Hi,
>
> It seems that the kernel loglevel is set to 7 ignoring the
> CONFIG_DEFAULT_MESSAGE_LOGLEVEL option (set to 4 in my config file)
>
> The /proc/sys/kernel/printk output is
>
> 7 4 1 7
>
> Passing the boot parameter "loglevel=4" or
On Friday 15 March 2013 09:46 PM, Paul Bolle wrote:
> There's no (Kconfig) macro CONFIG_BLOCK_DEV_RAM. (CONFIG_BLK_DEV_RAM
> does exist though.) But linux/blk.h got killed in 2005 anyway (in a
> patch titled "kill blk.h"), so these three lines can be removed.
>
> Signed-off-by: Paul Bolle
The of_device_id table is supposed to be zero-terminated.
Signed-off-by: Axel Lin
Acked-by: Grant Likely
---
This patch was sent on https://lkml.org/lkml/2012/12/9/135
Re-generate the patch against linux-next and resend.
drivers/gpio/gpio-samsung.c |1 +
1 file changed, 1 insertion(+)
On Fri, 2013-03-15 at 22:51 +, Abodunrin, Akeem G wrote:
> -Original Message-
> From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] On
> Behalf Of Joe Perches
[]
> Reduce the number of calls required to alloc a zeroed block of memory.
[]
> diff --git
On Tue, 2013-03-12 at 15:44 -0700, Greg Kroah-Hartman wrote:
> 3.0-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Mark Brown
>
> commit 3e78080f81481aa8340374d5a37ae033c1cf4272 upstream.
>
> Not having power is a pretty serious error
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Sat, Mar 16, 2013 at 01:22:31AM +, Liu, Chuansheng wrote:
> Hello Greg,
>
> Double checked, there is no your response before.
> Can you consider it again? Thanks.
Consider what? I get about
From: "zhangwei(Jovi)"
ppc64 has its own syscall prefix like ".SyS" or ".sys". Make the
comment in arch_syscall_match_sym_name() more understandable.
Link: http://lkml.kernel.org/r/513d842f.40...@huawei.com
Signed-off-by: zhangwei(Jovi)
Signed-off-by: Steven Rostedt
---
From: "zhangwei(Jovi)"
TRACE_MAX_PRINT macro is defined, but is not used.
Link: http://lkml.kernel.org/r/513d8421.4070...@huawei.com
Signed-off-by: zhangwei(Jovi)
Signed-off-by: Steven Rostedt
---
kernel/trace/trace.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
From: "zhangwei(Jovi)"
Use pr_warn_once, instead of making an open coded implementation.
Link: http://lkml.kernel.org/r/513d8419.20...@huawei.com
Signed-off-by: zhangwei(Jovi)
Signed-off-by: Steven Rostedt
---
kernel/trace/trace.c |9 ++---
1 file changed, 2 insertions(+), 7
From: "zhangwei(Jovi)"
By moving find_event_field() and trace_find_field() into trace_events.c,
the ftrace_common_fields list and trace_get_fields() can become local to
the trace_events.c file.
find_event_field() is renamed to trace_find_event_field() to conform to
the tracing global function
From: "zhangwei(Jovi)"
trace_destroy_fields() is not used outside of the file. It can be
a static function.
Link: http://lkml.kernel.org/r/513d842a.2000...@huawei.com
Signed-off-by: zhangwei(Jovi)
Signed-off-by: Steven Rostedt
---
kernel/trace/trace_events.c |2 +-
1 file changed, 1
From: "zhangwei(Jovi)"
trace_event_mutex is an rw semaphore now, not a mutex, change the name.
Link: http://lkml.kernel.org/r/513d843b.40...@huawei.com
Signed-off-by: zhangwei(Jovi)
[ Forward ported to my new code ]
Signed-off-by: Steven Rostedt
---
kernel/trace/trace_events.c | 22
From: "Steven Rostedt (Red Hat)"
Update the README file in debugfs/tracing to something more useful.
What's currently in the file is very old and what it shows doesn't
have much use. Heck, it tells you how to mount debugfs! But to read
this file you would have already needed to mount it.
On Sat, Mar 16, 2013 at 2:14 AM, Russell King - ARM Linux
wrote:
> We don't support different CPUs running at different frequencies with
> the delay loop. Sorry.
Does it means that a timer-based delay implementation must be used to
get an accurate delay in SMP. I think it should print a warning
From: "Steven Rostedt (Red Hat)"
ftrace_dump() had a lot of issues. What ftrace_dump() does, is when
ftrace_dump_on_oops is set (via a kernel parameter or sysctl), it
will dump out the ftrace buffers to the console when either a oops,
panic, or a sysrq-z occurs.
This was written a long time ago
From: "Steven Rostedt (Red Hat)"
When testing my large changes to the ftrace system, there was
a bug that looked like the ring buffer was dropping events.
I wrote up a quick integrity checker of the ring buffer to
see if it was.
Although the bug ended up being something stupid I did in ftrace,
One more linux-next patch series.
The first patch is a ring buffer boot time selftest. A bug in my development
code looked like the ring buffer was dropping events, and I wrote a test
to make sure that wasn't the case. The bug ended up being a stupid
mistake in my development code, but the ring
Hi Samuel,
On Fri, 15 Mar 2013 17:46:25 +0100 Samuel Ortiz wrote:
>
> On Thu, Mar 14, 2013 at 01:02:01AM +0100, Samuel Ortiz wrote:
> >
> > I am moving the MFD development from mfd-2.6.git/for-next to a new mfd-next
> > tree:
> >
> >
On Sat, 2013-03-16 at 01:09 +0800, Russell King - ARM Linux wrote:
> On Tue, Mar 12, 2013 at 10:40:04PM -0700, Bill Huang wrote:
> > That will be too bad, it looks like we deadlock in the mechanism, we
> > cannot change existing drivers behavior (that means some call
> > clk_disable/enable
On Fri, 2013-03-15 at 20:33 +0800, Ulf Hansson wrote:
> I guess you did not fully got what I meant with "dvfs clock type". It
> will not affect the clock API. But instead the dvfs is handled by
> implementing a specific clk hw type. So the same thing is accomplished
> as with clk notifiers, no
On 16/03/13 12:03, H Hartley Sweeten wrote:
> Remove the __init tag from ep93xxbl_probe() to fix the section
> mismatch warning.
>
> Signed-off-by: H Hartley Sweeten
> Cc: Ryan Mallon
> Cc: Richard Purdie
> Cc: Florian Tobias Schandinat
There is a patch for this already queued in Andrew
On Fri, 15 Mar 2013 23:29:53 +0800
Xiao Guangrong wrote:
> +/*
> + * The caller should protect concurrent access on
> + * kvm->arch.mmio_invalid_gen. Currently, it is used by
> + * kvm_arch_commit_memory_region and protected by kvm->slots_lock.
> + */
> +void kvm_mmu_invalid_mmio_spte(struct kvm
On Fri, 2013-03-15 at 15:41 +0800, Jason Wang wrote:
> Some drivers depends on transport_header to do packet transmission, but it was
> unset in some cases (one example is macvtap driver which build skbs from
> userspace and generate CHECKSUM_NONE packets). The driver may crash in those
> cases
On 14.03.2013 22:33, Alan Stern wrote:
Maybe a better way to go about this is, instead of printing out every
allocation and deallocation, to keep a running counter. You could have
the driver print out the value of this counter every minute or so. Any
time the device isn't in use, the counter
On Tue, 2013-03-12 at 15:44 -0700, Greg Kroah-Hartman wrote:
> 3.0-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Asias He
>
> commit 472b72f2db7831d7dbe22ffdff4adee3bd49b05d upstream.
>
> The page++ is wrong. It makes
On Fri, 15 Mar 2013 23:26:59 +0800
Xiao Guangrong wrote:
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index d3c4787..61a5bb6 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -6991,7 +6991,7 @@ void kvm_arch_commit_memory_region(struct kvm *kvm,
>* mmio sptes.
Still reading, but sounds great if this works!
I did not like the idea of mmio-rmap based approach so much, but this
would be really/perfectly scalable.
Thanks,
Takuya
On Fri, 15 Mar 2013 23:26:16 +0800
Xiao Guangrong wrote:
> The current way is holding hot mmu-lock and walking all
On Sat, 2013-03-16 at 01:22 +0800, Stephen Warren wrote:
> On 03/14/2013 11:51 PM, Bill Huang wrote:
> > On Fri, 2013-03-15 at 13:19 +0800, Stephen Warren wrote:
> >> On 03/14/2013 04:58 AM, Bill Huang wrote:
> >>> Hook up "pm_power_off" to palmas power off routine if there is DT
> >>> property
On Sat, 2013-03-16 at 03:51 +0800, Stephen Warren wrote:
> On 03/15/2013 11:45 AM, Russell King - ARM Linux wrote:
> > On Thu, Mar 14, 2013 at 02:31:04AM -0700, Bill Huang wrote:
> >> Add the below two notifier events so drivers which are interested in
> >> knowing the clock status can act
On Sat, 2013-03-16 at 03:38 +0800, Stephen Warren wrote:
> On 03/15/2013 06:33 AM, Ulf Hansson wrote:
> > On 15 March 2013 13:06, Bill Huang wrote:
> >> On Fri, 2013-03-15 at 18:08 +0800, Ulf Hansson wrote:
> ...
> >>> Some prerequisites; I think am in favor of using the clk API to
> >>> trigger
Hello Greg,
Double checked, there is no your response before.
Can you consider it again? Thanks.
Since we have printed the failure info, why not enhance it a bit:)
Example without this patch:
pm_op(): platform_pm_suspend+0x0/0x50 returns -11
PM: Device power.0 failed to suspend: error -11
And
Hi,
I was writing an application to ptrace a process which is dumping core
from inside the pipe application for core_pattern.
So for example you make core pattern equal to something like
"|/bin/corepipe_app" then the kernel runs that app prior to actually
killing the process that failed.
Before
[resend it for sytax error in Message-ID]
Sorry all.
I just found there is a syntax error of Message-ID in the mail sent from my
mutt. So all my reply maybe rejected by the mail server.
Hope this time the mail can be accepted by the mail server.
Sorry for the noise again.
On Thu, Mar 07,
Remove the __init tags from the ep93xxfb_calc_fbsize() and
ep93xxfb_alloc_videomem() functions to fix the section mismatch
warnings.
Use module_platform_driver() to remove the init/exit boilerplate.
Signed-off-by: H Hartley Sweeten
Cc: Ryan Mallon
Cc: Florian Tobias Schandinat
---
On 02/21/2013 01:29 AM, JA Magallón wrote:
On 02/20/2013 08:58 PM, JA Magallón wrote:
Hi all...
I have a strange problem with latest kernels. When I update my netbook
I get many "Installation failed, bad rpms:" mesages. First I thougt
that the oldie cheap ssd was failing (it is an Aspire
Fix a couple section mismatch warnings and convert two of the ep93xx
drivers to use module_platform_driver.
H Hartley Sweeten (3):
backlight: ep93xx_bl: fix section mismatch
video: ep93xx-fb.c: fix section mismatch and use module_platform_driver
misc: ep93xx_pwm.c: fix section mismatch and
Remove the __init tags from the ep93xx_pwm_probe() and
ep93xx_pwm_remove() functions to fix the section mismatch
warnings.
Use module_platform_driver() to remove the init/exit boilerplate.
Signed-off-by: H Hartley Sweeten
Cc: Ryan Mallon
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
---
Remove the __init tag from ep93xxbl_probe() to fix the section
mismatch warning.
Signed-off-by: H Hartley Sweeten
Cc: Ryan Mallon
Cc: Richard Purdie
Cc: Florian Tobias Schandinat
---
drivers/video/backlight/ep93xx_bl.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
This patch fixes a kernel crash when using precise sampling (PEBS)
after a suspend/resume. Turns out the CPU notifier code is not invoked
on CPU0 (BP). Therefore, the DS_AREA (used by PEBS) is not restored properly
by the kernel and keeps it power-on/resume value of 0 causing any PEBS
measurement
On Fri, Mar 15, 2013 at 2:56 PM, Stephane Eranian wrote:
> On Fri, Mar 15, 2013 at 9:53 PM, Shuah Khan wrote:
>> On Fri, Mar 15, 2013 at 2:31 PM, Greg KH wrote:
>>> On Fri, Mar 15, 2013 at 02:26:07PM +0100, Stephane Eranian wrote:
This patch fixes a kernel crash when using precise
El 15/03/13 21:29, Russell King - ARM Linux escribió:
> On Fri, Mar 15, 2013 at 09:15:11PM -0300, Emilio López wrote:
>> Hello Russell,
>>
>> El 15/03/13 19:39, Russell King - ARM Linux escribió:
>>> On Fri, Mar 15, 2013 at 09:06:23PM +0100, Maxime Ripard wrote:
+ /* clock got configured
On Fri, Mar 15, 2013 at 2:53 PM, Lars-Peter Clausen wrote:
> What exactly is the spinlock protecting against here? Concurrent runs of
> exynos_adc_isr? This is probably not issue in the first place.
>
> What you want to protect against is that completion is completed between the
> call to
On Fri, Mar 15, 2013 at 09:15:11PM -0300, Emilio López wrote:
> Hello Russell,
>
> El 15/03/13 19:39, Russell King - ARM Linux escribió:
> > On Fri, Mar 15, 2013 at 09:06:23PM +0100, Maxime Ripard wrote:
> >> + /* clock got configured through clk api, all done */
> >> + if (p->uartclk)
> >
> >
Hello Russell,
El 15/03/13 19:39, Russell King - ARM Linux escribió:
> On Fri, Mar 15, 2013 at 09:06:23PM +0100, Maxime Ripard wrote:
>> +/* clock got configured through clk api, all done */
>> +if (p->uartclk)
>
> if (IS_ERR(p->uartclk))
>
Isn't IS_ERR for pointers? p->uartclk
On Fri, Mar 15, 2013 at 10:06:19PM +, Chris Wilson wrote:
> On Fri, Mar 15, 2013 at 09:36:07AM -0700, Ben Widawsky wrote:
> > On Fri, Mar 15, 2013 at 08:24:03AM +, Chris Wilson wrote:
> > > That's what I thought too. Looking at the stack trace, the empirical
> > > evidence is that we need
Walking a bio's page mappings has proved problematic, so create a new bio flag
to indicate that a bio's data needs to be snapshotted in order to guarantee
stable pages during writeback. Next, for the one user (ext3/jbd) of
snapshotting, hook all the places where writes can be initiated without
-Original Message-
From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] On
Behalf Of Joe Perches
Sent: Friday, March 15, 2013 10:24 AM
To: net...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org; e1000-de...@lists.sourceforge.net;
linux-wirel...@vger.kernel.org;
Greg has blessed Linux v3.8.3 so we get to backport drivers for this
release for usage on older kernels through compat-drivers, you can
either visit the v3.8.3 release page [0] or the temporary release page
[1]. This release has been test compiled against vanilla Linux kernel
releases v2.6.24 -
On Tue, Mar 12, 2013 at 4:20 PM, Bjorn Helgaas wrote:
> On Sat, Mar 9, 2013 at 2:20 AM, Chris Clayton
> wrote:
>> On 03/08/13 22:57, Bjorn Helgaas wrote:
>>> Thanks. I opened this bug report:
>>> https://bugzilla.kernel.org/show_bug.cgi?id=54981 to keep track of
>>> your logs.
Hi Chris,
The
On Fri, Mar 15, 2013 at 09:06:23PM +0100, Maxime Ripard wrote:
> + /* clock got configured through clk api, all done */
> + if (p->uartclk)
if (IS_ERR(p->uartclk))
> + return 0;
> +
> + /* try to find out clock frequency from DT as fallback */
> if
Signed-off-by: Marek Belisko
---
arch/arm/mach-mvebu/irq-armada-370-xp.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-mvebu/irq-armada-370-xp.c
b/arch/arm/mach-mvebu/irq-armada-370-xp.c
index 274ff58..d8dbcc1 100644
---
On 16/03/13 09:20, H Hartley Sweeten wrote:
> commit be867814 "drivers/video/ep93xx-fb.c: use devm_ functions"
>
> Introduced a build error:
>
> drivers/video/ep93xx-fb.c: In function 'ep93xxfb_probe':
> drivers/video/ep93xx-fb.c:532: error: implicit declaration of function
> 'devm_ioremap'
>
commit be867814 "drivers/video/ep93xx-fb.c: use devm_ functions"
Introduced a build error:
drivers/video/ep93xx-fb.c: In function 'ep93xxfb_probe':
drivers/video/ep93xx-fb.c:532: error: implicit declaration of function
'devm_ioremap'
drivers/video/ep93xx-fb.c:533: warning: assignment makes
On Friday 15 March 2013, Nicolas Ferre wrote:
> This is a pull-request targeted to do some cleanup in AT91 Kconfig
> and board-dt-xxx.c files. It will prepare the coming introduction of
> our SAMA5D3 family (Atmel new Cortex-A5) that we will stack on top
> of these modifications soon.
>
Pulled
On Fri, Mar 15, 2013 at 2:56 PM, H. Peter Anvin wrote:
> On 03/15/2013 02:15 PM, Paul Moore wrote:
>> On Tuesday, February 26, 2013 03:58:23 PM Paul Moore wrote:
>>> On Friday, February 15, 2013 12:21:43 PM Paul Moore wrote:
Commit fca460f95e928bae373daa8295877b6905bc62b8 simplified the x32
On Friday 15 March 2013, Nicolas Ferre wrote:
> Arnd, Olof,
>
> Following our conversation about these framebuffer patches for
> Atmel LCD driver, here are the remaining three patches that can be
> pushed for 3.10. As suggested by Arnd, I have kept them on top of last
> commit concerning this
On Fri, 15 Mar 2013, Greg Kroah-Hartman wrote:
> > Add "lmk:" prefix to the debug print so it's easier to analyse LMK's
> > debug output:
> > dmesg | grep lmk
>
> Ick, no, please use the proper interface for this (i.e. pr_fmt).
>
And I'm sure that mysterious new "lmk:" messages appearing in
On Fri, Mar 15, 2013 at 09:36:07AM -0700, Ben Widawsky wrote:
> On Fri, Mar 15, 2013 at 08:24:03AM +, Chris Wilson wrote:
> > That's what I thought too. Looking at the stack trace, the empirical
> > evidence is that we need the check.
> > -Chris
>
> I think we need to investigate the issue
On Monday 11 March 2013, Rob Herring wrote:
> Please pull. This improves the clocksource init to avoid double matching
> to the DT device node. The clocksource init function changes are needed
> for any other clocksource conversions to CLKSRC_OF, so we need to make
> sure any other conversions use
On 03/15/2013 02:15 PM, Paul Moore wrote:
> On Tuesday, February 26, 2013 03:58:23 PM Paul Moore wrote:
>> On Friday, February 15, 2013 12:21:43 PM Paul Moore wrote:
>>> Commit fca460f95e928bae373daa8295877b6905bc62b8 simplified the x32
>>> implementation by creating a syscall bitmask, equal to
On Wed, Feb 20, 2013 at 1:29 AM, Kim, Milo wrote:
>> For this kind of patches you should really use the "-M" flag of "git
>> format-patch" to activate rename detection. The patch becomes much
>> more
>> readable. For example, the diffstat for this one using -M is:
>
> Thanks for useful tip!
>
Hi,
I'm running a new DELL PER420 with 2x Intel Xeon E5-2440 2,40 Ghz and
16GB of RAM with Kernel 3.7.9 and Linux vserver patch vs2.3.5.6 from
http://linux-vserver.org. Uptime was about 14 days, 8 hours.
Today evening the system has become not responsive and the netconsole
got me the
On 03/15/2013 05:26 PM, Naveen Krishna Chatradhi wrote:
> This patch does the following
> 1. Handle the return values of wait_for_completion_interruptible_timeout
> 2. Add spin locks to avoid race conditions during ISR.
>
> Signed-off-by: Naveen Krishna Chatradhi
> Cc: Doug Anderson
> Cc:
On Fri, Mar 15, 2013 at 2:01 PM, Jeff Layton wrote:
>
> On Thu, 14 Mar 2013 12:24:37 -0700
> Joe Perches wrote:
>
> > It's not obvious from reading the macro names that these macros
> > are for debugging. Convert the names to a single more typical
> > kernel style cifs_dbg macro.
> >
> >
Although there are no known cases of this being a problem (and it may
be technically impossible for the hardware to report more errors once
already in the error state), it seems unwise for us to be clearing
error interrupts that we didn't actually read.
Signed-off-by: Doug Anderson
---
acm_probe() ignores errors in tty_port_register_device()
and leaves intfdata pointing to freed memory on alloc_fail7
error path. The patch fixes the both issues.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/usb/class/cdc-acm.c |
On a flaky piece of hardware that seems good at generating CRC errors,
we have found that often times the CRC errors don't get reported
properly when using CONFIG_MMC_DW_IDMAC (they get reported OK when
using pio).
The flow that happens is:
1. dw_mci_interrupt() fires and status=80b8,
On Fri, Mar 15, 2013 at 8:30 PM, Greg Kroah-Hartman
wrote:
> On Mon, Mar 04, 2013 at 09:35:07AM +0800, Grant Likely wrote:
>> drivers/tty/serial/8250/8250.c: In function 'serial_unlink_irq_chain':
>> drivers/tty/serial/8250/8250.c:1676:19: warning: 'i' may be used
>> uninitialized in this
On Fri, Mar 15, 2013 at 08:59:57AM -0400, Eduardo Valentin wrote:
> Change the way the omap_bandgap_power is written so that it has only
> one exit entry (Documentation/CodingStyle).
>
It's only if there is an unlock or something that you should do
this. Otherwise the pointless bunny hop is
On Fri, Mar 15, 2013 at 04:53:51PM +, Mark Brown wrote:
> On Fri, Mar 15, 2013 at 11:16:02AM +, Dimitris Papastamos wrote:
>
> > On my system there was no benefit of using it, it just happens
> > that the struct is aligned properly and needs no padding.
>
> OK, so which system was that
On Mon, Mar 11, 2013 at 9:20 AM, Wei Yongjun wrote:
> From: Wei Yongjun
>
> Remove duplicated include.
HI Wei, thanks for the patch. I've already staged the same patch for
inclusion in the next pull request for TPM drivers here:
On Tue, Mar 12, 2013 at 03:02:36PM -0700, Andrew Morton wrote:
> On Mon, 11 Mar 2013 15:03:22 -0400 Peter Hurley
> wrote:
>
> > On Mon, 2013-03-11 at 14:26 -0400, Dave Jones wrote:
> > > > > {
> > >
> > > I just hit this again on rc2 which looks like it has the fixes that
> >
> You still need to add:
>
> From: Steven Rostedt
>
> Otherwise you get the authorship of this patch.
My apologies. I resend my patch 1/3 by adding it shortly.
Seiji
> -Original Message-
> From: Steven Rostedt [mailto:rost...@goodmis.org]
> Sent: Friday, March 15, 2013 5:10 PM
> To:
From: Steven Rostedt
Each TRACE_EVENT() adds several helper functions. If two or more trace events
share the same structure and print format, they can also share most of these
helper functions and save a lot of space from duplicate code. This is why the
DECLARE_EVENT_CLASS() and DEFINE_EVENT()
On Fri, Mar 15, 2013 at 08:50:45PM +, Moore, Robert wrote:
> Can you explain in a bit more detail what brings this up?
>
> I'm aware of the limitation of the generic address structure, but we are
> forced by the (current) ACPI specification to use it if it is present for a
> given register.
On Tuesday, February 26, 2013 03:58:23 PM Paul Moore wrote:
> On Friday, February 15, 2013 12:21:43 PM Paul Moore wrote:
> > Commit fca460f95e928bae373daa8295877b6905bc62b8 simplified the x32
> > implementation by creating a syscall bitmask, equal to 0x4000, that
> > could be applied to x32
On 3/15/2013 1:35 PM, Vivek Goyal wrote:
> Create a new capability CAP_SIGNED which can be given to signed executables.
This would drive anyone who is trying to use
capabilities as the privilege mechanism it is
intended to be absolutely crazy.
Capabilities aren't just random attribute bits. They
You still need to add:
From: Steven Rostedt
Otherwise you get the authorship of this patch.
-- Steve
On Fri, 2013-03-15 at 20:35 +, Seiji Aguchi wrote:
> Each TRACE_EVENT() adds several helper functions. If two or more trace events
> share the same structure and print format, they can
On Fri, Mar 15, 2013 at 08:59:55AM -0400, Eduardo Valentin wrote:
> This patch introduce a macro to read, update, write bitfields.
> It will be specific to bandgap data structures.
>
> Signed-off-by: Eduardo Valentin
> ---
> drivers/staging/omap-thermal/omap-bandgap.c | 178
>
On Fri, Mar 15, 2013 at 1:09 PM, Florian Vaussard
wrote:
> Hi,
>
>
> On 03/15/2013 07:59 PM, Thierry Reding wrote:
>>>
>>>
>>> Hi Florian and Thierry,
>>>
>>> Sorry, guys. My bad! I'm using GMAIL filtering my emails. This email
>>> goes into my arm-linux mail list archive and I totally missed it.
Le 15/03/2013 21:50, Maxime Ripard a écrit :
> From: Stefan Roese
>
> The Allwinner A10 has an ethernet controller that is advertised as
> coming from Davicom.
>
> The exact feature set of this controller is unknown, since there is no
> public documentation for this IP, and this driver is
Hello.
On 03/15/2013 11:06 PM, Maxime Ripard wrote:
Both A10 and A13 Allwinner SoCs have a Synopsys APB uart3 device
available, so add it to the sunxi.dtsi file
Signed-off-by: Maxime Ripard
Acked-by: Emilio López
---
arch/arm/boot/dts/sunxi.dtsi | 10 ++
1 file changed, 10
On Fri, Mar 15, 2013 at 09:49:00PM +0100, Stephane Eranian wrote:
> On Fri, Mar 15, 2013 at 9:31 PM, Greg KH wrote:
> >
> > On Fri, Mar 15, 2013 at 02:26:07PM +0100, Stephane Eranian wrote:
> > >
> > > This patch fixes a kernel crash when using precise sampling (PEBS)
> > > after a
On Fri, Mar 15, 2013 at 9:53 PM, Shuah Khan wrote:
> On Fri, Mar 15, 2013 at 2:31 PM, Greg KH wrote:
>> On Fri, Mar 15, 2013 at 02:26:07PM +0100, Stephane Eranian wrote:
>>>
>>> This patch fixes a kernel crash when using precise sampling (PEBS)
>>> after a suspend/resume. Turns out the CPU
On 03/15/2013 05:07 AM, Linus Walleij wrote:
> From: Linus Walleij
>
> Recently as adoption of the pinctrl framework is reaching
> niches where the pins are reconfigured during system sleep
> and datasheets often talk about something called "GPIO mode",
> some engineers become confused by this,
On Fri, Mar 15, 2013 at 2:31 PM, Greg KH wrote:
> On Fri, Mar 15, 2013 at 02:26:07PM +0100, Stephane Eranian wrote:
>>
>> This patch fixes a kernel crash when using precise sampling (PEBS)
>> after a suspend/resume. Turns out the CPU notifier code is not invoked
>> on CPU0 (BP). Therefore, the
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun4i-a10.dtsi |7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/sun4i-a10.dtsi b/arch/arm/boot/dts/sun4i-a10.dtsi
index 03d2b53..f3c2158 100644
--- a/arch/arm/boot/dts/sun4i-a10.dtsi
+++
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun4i-a10.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/sun4i-a10.dtsi b/arch/arm/boot/dts/sun4i-a10.dtsi
index f3c2158..fc4ce45 100644
--- a/arch/arm/boot/dts/sun4i-a10.dtsi
+++
From: Stefan Roese
The Allwinner A10 has an ethernet controller that is advertised as
coming from Davicom.
The exact feature set of this controller is unknown, since there is no
public documentation for this IP, and this driver is mostly the one
published by Allwinner that has been heavily
On Fri, Mar 15, 2013 at 04:32:51PM -0400, Jason Cooper wrote:
> On Fri, Mar 15, 2013 at 01:24:52PM -0700, Greg Kroah-Hartman wrote:
> > On Thu, Feb 28, 2013 at 02:34:21PM +0200, Heikki Krogerus wrote:
> > > Hi,
> > >
> > > On Thu, Feb 28, 2013 at 12:42:06PM +0100, Gregory CLEMENT wrote:
> > > >
Linn,
Can you explain in a bit more detail what brings this up?
I'm aware of the limitation of the generic address structure, but we are forced
by the (current) ACPI specification to use it if it is present for a given
register.
Thanks,
Bob
> -Original Message-
> From: Linn Crosetto
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun4i-a10-hackberry.dts | 19 +++
1 file changed, 19 insertions(+)
diff --git a/arch/arm/boot/dts/sun4i-a10-hackberry.dts
b/arch/arm/boot/dts/sun4i-a10-hackberry.dts
index f84549a..3808c1a 100644
---
From: Stefan Roese
Signed-off-by: Stefan Roese
---
arch/arm/boot/dts/sun4i-a10-cubieboard.dts |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/sun4i-a10-cubieboard.dts
b/arch/arm/boot/dts/sun4i-a10-cubieboard.dts
index 88e2dc1..7a3872d 100644
---
On Fri, 15 Mar 2013, Linus Torvalds wrote:
> On Fri, Mar 15, 2013 at 6:26 AM, Stephane Eranian wrote:
> >
> > This patch fixes a kernel crash when using precise sampling (PEBS)
> > after a suspend/resume.
>
> Yup, works. Applied.
>
> Can we please get rid of the crazy CPU notifier crap from
On Fri, Mar 15, 2013 at 9:31 PM, Greg KH wrote:
>
> On Fri, Mar 15, 2013 at 02:26:07PM +0100, Stephane Eranian wrote:
> >
> > This patch fixes a kernel crash when using precise sampling (PEBS)
> > after a suspend/resume. Turns out the CPU notifier code is not invoked
> > on CPU0 (BP). Therefore,
On Fri, 2013-03-15 at 11:45 -0700, Kees Cook wrote:
> On Fri, Mar 15, 2013 at 11:28 AM, Nicolas Schichan
> wrote:
> > diff --git a/include/linux/seccomp.h b/include/linux/seccomp.h
> > index 6f19cfd..af27494 100644
> > --- a/include/linux/seccomp.h
> > +++ b/include/linux/seccomp.h
> > @@ -6,6
On Fri, 2013-03-15 at 15:16 -0500, Steve French wrote:
> I would like to merge the three we have (one still has to be put in
> for-next - the one from Jeff) for for-next in the next three or fouir
> days - but I can create another temporary branch for the ones for 3.10
> - but ... I would like to
Currently there seem to be two types of digital signatures. Old one and
that is RSA and new one which is being called asymmetric. Right now they
both fall in the categorty of EVM_IMA_XATTR_DIGSIG and one differentiates
between two using signature version. Version 1 is old type and version 2
is new
Each TRACE_EVENT() adds several helper functions. If two or more trace events
share the same structure and print format, they can also share most of these
helper functions and save a lot of space from duplicate code. This is why the
DECLARE_EVENT_CLASS() and DEFINE_EVENT() were created.
Some
Change log
v10 -> v11
- Rebase to 3.9-rc2
- Add a modification for hyperv_callback vector. (patch 2/3)
- Change a way to switch idt to check the table in use instead of
saving/restoring it,
because saving/restoring functions will break if we have to add another one.
(patch 2/3)
v9 ->
1 - 100 of 1244 matches
Mail list logo
