On Thu, Jul 19, 2012 at 02:04:11PM -0700, da...@lang.hm wrote:
> On Thu, 19 Jul 2012, Josh Boyer wrote:
>
> >On Thu, Jul 19, 2012 at 02:13:40PM -0400, Steven Rostedt wrote:
> >>On Thu, 2012-07-19 at 13:56 -0400, Josh Boyer wrote:
> >>
> >>>Distros aren't stationary things.
> >>
> >>Exactly my
Hi Linus,
Please pull these last minute fixes for Ceph from:
git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git for-linus
The important one fixes a bug in the socket failure handling behavior that
was turned up in some recent failure injection testing. The other two are
On Thu, 2012-07-19 at 14:51 -0600, Toshi Kani wrote:
> If your concern is actually a performance bottleneck in acpi_get_name()
> you found in the code, you should report it to the ACPI CA team.
I have tried my best to get you to understand the problems in bigger
picture your patch set can
> -Original Message-
> From: Greg KH (gre...@linuxfoundation.org)
> [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, July 19, 2012 6:02 PM
> To: KY Srinivasan
> Cc: Paolo Bonzini; de...@linuxdriverproject.org; linux-kernel@vger.kernel.org;
> virtualizat...@lists.osdl.org
> Subject:
Hi,
I am trying to configure kexec/kdump on 2.6.35-14.
$> kexec --version
kexec-tools-testing 20080330 released 30th March 2007
I did manage to configure kdump to use raw device (/dev/sda7) for saving the
dump from within the initrd.
When the production kernel boots, it copies core from
> If users specify a number of that is too big, the message will be meaningless.
> I just couldn't decide the appropriate number by myself.
> Then, I make it tunable.
I think that 3 or 4 logs should be plenty to cover almost all situations. E.g.
with 3 logs you could capture 2 OOPS (and perhaps
These types of macros should not be used for either a
single statement nor should the macro end with a semi-colon.
Add tests for these conditions.
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 39 +++
1 files changed, 39 insertions(+), 0
On Thu, Jul 19, 2012 at 03:37:43PM -0500, Jonathan Nieder wrote:
> Mel Gorman wrote:
>
> > commit ad2b8e601099a23db53f91c18d874fe98854 upstream - WARNING: partial
> > backport only
> >
> > Stable note: Not tracked in Bugzilla. This patch is very controversial for
> > -stable. The
Mel Gorman wrote:
> On Thu, Jul 19, 2012 at 03:30:17PM -0500, Jonathan Nieder wrote:
>> It doesn't sound like it fixes a serious issue.
>
> You're right, it doesn't. There are a few patches in this series that
> were applied because they made other patches easier to apply and this is
> one of
On Thu, Jul 19, 2012 at 03:30:17PM -0500, Jonathan Nieder wrote:
> Mel Gorman wrote:
>
> > From: Dave Chinner
> >
> > commit 095760730c1047c69159ce88021a7fa3833502c8 upstream.
> >
> > Stable note: Not tracked in Bugzilla. This is a diagnostic patch that
> > was part of a series addressing
On Thu, Jul 19, 2012 at 09:22:53PM +, KY Srinivasan wrote:
>
>
> > -Original Message-
> > From: Greg KH (gre...@linuxfoundation.org)
> > [mailto:gre...@linuxfoundation.org]
> > Sent: Thursday, July 19, 2012 5:07 PM
> > To: KY Srinivasan
> > Cc: Paolo Bonzini;
Adding 5 more tests for new event group syntax. Tests are executed
within the 'perf test parse' test suite.
Signed-off-by: Jiri Olsa
---
tools/perf/util/parse-events-test.c | 303 ++-
1 file changed, 300 insertions(+), 3 deletions(-)
diff --git
Adding scanner/parser bits to parse event groups.
The grammar for group is:
groups: groups ',' group | group
group: group_name '{' events '}' group_mod
group_name: name | empty
group_mod: ':' group_mods | empty
group_mods: event_mod
It's possible to use standard event
This patch adds a functionality that allows to create event groups
based on the way they are specified on the command line. Adding
functionality to the '{}' group syntax introduced in earlier patch.
The current '--group/-g' option behaviour remains intact. If you
specify it for record/stat/top
hi,
adding support for creating event groups based on the way they
are specified on the command line.
This patchset adds the '{}' style grammar to express event group,
allowing so far only the 'event modifier' as group modifier.
v4 changes:
- group modifier updates events modifiers (not
Adding support to update already defined event's attribute with
event modifier. This change will allow to use group modifier as
an update to the existing event modifiers.
Adding 'add' parameter to the parse_events__modifier_event function.
Calling it with 'add' = false/true, the event modifier is
On Thu, Jul 19, 2012 at 03:25:44PM -0500, Jonathan Nieder wrote:
> Hi,
>
> Mel Gorman wrote:
>
> > From: Konstantin Khlebnikov
> >
> > Stable note: Not tracked in Bugzilla. [get|put]_mems_allowed() is extremely
> > expensive and severely impacted page allocator performance. This
> > is
Takes care of errors when running something like:
$ ./scripts/patch-kernel . .. 3.5
Current kernel version is 3.5.0-rc7 ( Saber-toothed Squirrel)
./scripts/patch-kernel: line 229: [: -lt: unary operator expected
./scripts/patch-kernel: line 252: [: -gt: unary operator expected
diff --git
> How big a value for efi_pstore_log_num have you tried? Did you see any
> problems with EFI running out of space? Do you get some
> helpful error message if you pick a number that is too big?
Please calm down... This is RFC patch.
If users specify a number of that is too big, the message will
On Thursday, July 19, 2012, Carsten Emde wrote:
> There are two cpuidle governors ladder and menu. While the ladder
> governor is always available, if CONFIG_CPU_IDLE is selected, the
> menu governor additionally requires CONFIG_NO_HZ.
>
> A particular C state can be disabled by writing to the
From: Jan Bannister
Fixed a coding style issue
Signed-off-by: Jan Bannister
---
kernel/acct.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/acct.c b/kernel/acct.c
index 02e6167..725d3a9 100644
--- a/kernel/acct.c
+++ b/kernel/acct.c
@@ -134,7 +134,7 @@
On Thu, Jul 19, 2012 at 8:22 PM, Josh Boyer wrote:
> On Thu, Jul 19, 2012 at 08:20:36PM +0200, Paul Bolle wrote:
>> On Thu, 2012-07-19 at 13:19 -0400, Josh Boyer wrote:
>> > kconfig already spits out warnings for symbols being selected that
>> > don't exist.
>>
>> Does it? Since when does it do
Obsoleted since commit 7c5763b8453a94871d356f20df30f350f8631e8b ("drivers:
misc: Remove MISC_DEVICES config option")
Signed-off-by: Geert Uytterhoeven
---
arch/arm/mach-davinci/Kconfig |6 --
arch/unicore32/Kconfig|1 -
2 files changed, 0 insertions(+), 7 deletions(-)
diff
> With this patch, efi_pstore can hold multiple logs with a new kernel
> parameter, efi_pstore_log_num.
How big a value for efi_pstore_log_num have you tried? Did you see any problems
with EFI running
out of space? Do you get some helpful error message if you pick a number that
is too big?
> -Original Message-
> From: Greg KH (gre...@linuxfoundation.org)
> [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, July 19, 2012 5:07 PM
> To: KY Srinivasan
> Cc: Paolo Bonzini; de...@linuxdriverproject.org; linux-kernel@vger.kernel.org;
> virtualizat...@lists.osdl.org
> Subject:
>From 06f9a06f4aeecdb9d07014713ab41b548ae219b5 Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Thu, 19 Jul 2012 13:52:53 -0700
kthread_worker provides minimalistic workqueue-like interface for
users which need a dedicated worker thread (e.g. for realtime
priority). It has basic queue,
>From c9bba34243a86fb3ac82d1bdd0ce4bf796b79559 Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Thu, 19 Jul 2012 13:52:53 -0700
Make the following two non-functional changes.
* Separate out insert_kthread_work() from queue_kthread_work().
* Relocate struct kthread_flush_work and
Hello,
kthread_worker was introduced together with concurrency managed
workqueue to serve workqueue users which need a special dedicated
worker - e.g. RT scheduling. This is minimal queue / flush / flush
all iterface on top of kthread and each provided interface matches the
workqueue counterpart
[Problem]
When efi_pstore holds just one log and it doesn't overwrite an exisiting entry,
we lose a critical message if kernel panics while system is rebooting.
[Solution]
If users decide that NVRAM size is not big enough to hold multiple logs,
efi_pstore has to handle just one log and
On Thu, Jul 19, 2012 at 06:30:47PM +0100, Alan Cox wrote:
>
> > Well, yes. I was thinking it would be more like:
> >
> > distro/Kconfig.fedora
> > menuconfig FEDORA
> > if FEDORA
> > config FEDORA_16
> >select WHATEVER
> > config FEDORA_17
>
> Nope you need
>
>
[Problem]
When efi_pstore holds just one log and it doesn't overwrite an exisiting entry,
we lose a critical message if kernel panics while system is rebooting.
[Solution]
With this patch, efi_pstore can hold multiple logs with a new kernel
parameter, efi_pstore_log_num.
We can simply
[Problem]
Currently, efi_pstore driver simply overwrites existing panic messages in
NVRAM.
So, in the following scenario, we will lose 1st panic messages.
1. kernel panics.
2. efi_pstore is kicked and write panic messages to NVRAM.
3. system reboots.
4. kernel panics again before a user
Thanks for the explanation. Given that we have the asm-generic version of
> kvm_para.h, I don't see why we can't just export linux/kvm_para.h
> unconditionally and fix the few remaining architectures by adding generic-y
> lines to their Kbuild files.
>
> Something like below (I also
This patchset avoids losing a critical message like panic in NVRAM.
[Problem]
Currently, efi_pstore driver simply overwrites existing panic messages in
NVRAM.
So, in the following scenario, we will lose 1st panic messages.
1. kernel panics.
2. efi_pstore is kicked and write
From: Jan Bannister
Fixed a coding style issue
Signed-off-by: Jan Bannister
---
kernel/acct.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/acct.c b/kernel/acct.c
index 02e6167..725d3a9 100644
--- a/kernel/acct.c
+++ b/kernel/acct.c
@@ -134,7 +134,7 @@
On Thu, Jul 19, 2012 at 02:11:47AM +, KY Srinivasan wrote:
>
>
> > -Original Message-
> > From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
> > Bonzini
> > Sent: Friday, July 13, 2012 6:23 AM
> > To: KY Srinivasan
> > Cc: Greg KH; de...@linuxdriverproject.org;
On Thu, 19 Jul 2012, Josh Boyer wrote:
On Thu, Jul 19, 2012 at 02:13:40PM -0400, Steven Rostedt wrote:
On Thu, 2012-07-19 at 13:56 -0400, Josh Boyer wrote:
Distros aren't stationary things.
Exactly my point.
I mean, some of them certainly aim
for that goal, but userspace and kernels
Hello Kent,
This patch keeps gcc 4.7.0 happy. The static function dump_bset() could be
moved, but that would have made a bigger patch. :-)
Thanks,
Daniel
diff --git a/drivers/md/bcache/debug.c b/drivers/md/bcache/debug.c
index 3c9c24d..4dc0ba5 100644
--- a/drivers/md/bcache/debug.c
+++
Hi!
On Mon, Jul 16, 2012 at 8:30 PM, Markus F.X.J. Oberhumer
wrote:
> I encourage all compression users to test and benchmark this new version,
> and I also would ask some official LZO maintainer to convert the updated
> source files into a GIT commit and possibly push it to Linus or linux-next.
John Stultz wrote...
> Attached is the test case I used to reproduce and test the solution
> to the hard-hang deadlock.
I was wondering whether anybody managed to crash a virtualbox guest
using your program. No avail, using version 4.1.18 on the host and the
guest kernel running several 3.0.x (x
On Thu, 2012-07-19 at 13:25 -0600, Shuah Khan wrote:
> On Thu, 2012-07-19 at 11:28 -0600, Toshi Kani wrote:
> > On Thu, 2012-07-19 at 10:15 -0600, Shuah Khan wrote:
> > > On Wed, 2012-07-18 at 18:38 -0600, Toshi Kani wrote:
> > >
> > > >
> > > > This interface is defined in acpi/acpi_bus.h,
There are two cpuidle governors ladder and menu. While the ladder
governor is always available, if CONFIG_CPU_IDLE is selected, the
menu governor additionally requires CONFIG_NO_HZ.
A particular C state can be disabled by writing to the sysfs file
Rafael,
> Your patch doesn't seem to take this linux-next commit:
> http://git.kernel.org/?p=linux/kernel/git/rafael/linux-pm.git;a=commit;h=dc7fd275ae60ef8edf952aff2a62462f5d892fd4
> into account, does it?
Hmm, oops, you're right. This one came in after I checked it last time.
Changes in v2:
From: Chris Metcalf
Date: Wed, 18 Jul 2012 15:22:12 -0400
> On 7/18/2012 2:36 PM, David Miller wrote:
>> From: Chris Metcalf
>> Date: Sun, 1 Jul 2012 14:43:47 -0400
>>
>>> The tree is at:
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/cmetcalf/linux-tile.git net
>>>
>>> Chris Metcalf
Mel Gorman wrote:
> commit ad2b8e601099a23db53f91c18d874fe98854 upstream - WARNING: partial
> backport only
>
> Stable note: Not tracked in Bugzilla. This patch is very controversial for
> -stable. The upstream patch is addressing a completely different
> issue but accidentally
Mel Gorman wrote:
> From: Dave Chinner
>
> commit 095760730c1047c69159ce88021a7fa3833502c8 upstream.
>
> Stable note: Not tracked in Bugzilla. This is a diagnostic patch that
> was part of a series addressing excessive slab shrinking after
> GFP_NOFS failures. There is detailed
Signed-off-by: Geert Uytterhoeven
---
arch/m68k/kernel/module.c |4 ++--
arch/x86/kernel/module.c |2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/m68k/kernel/module.c b/arch/m68k/kernel/module.c
index 34849c4..eb46fd6 100644
--- a/arch/m68k/kernel/module.c
+++
Hi,
Mel Gorman wrote:
> From: Konstantin Khlebnikov
>
> Stable note: Not tracked in Bugzilla. [get|put]_mems_allowed() is extremely
> expensive and severely impacted page allocator performance. This
> is part of a series of patches that reduce page allocator overhead.
>
> Fix a gcc
diff --git a/Makefile b/Makefile
index a2e69a0..5d0edcb 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 4
-SUBLEVEL = 5
+SUBLEVEL = 6
EXTRAVERSION =
NAME = Saber-toothed Squirrel
diff --git a/arch/arm/plat-samsung/adc.c b/arch/arm/plat-samsung/adc.c
index
I'm announcing the release of the 3.4.6 kernel.
All users of the 3.4 kernel series must upgrade.
The updated 3.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.4.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 009160e..5fdfaa8 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 0
-SUBLEVEL = 37
+SUBLEVEL = 38
EXTRAVERSION =
NAME = Sneaky Weasel
diff --git a/arch/arm/plat-samsung/adc.c b/arch/arm/plat-samsung/adc.c
index
I'm announcing the release of the 3.0.38 kernel.
All users of the 3.0 kernel series must upgrade.
The updated 3.0.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.0.y
and can be browsed at the normal kernel.org git web browser:
On Tue, Jul 17, 2012 at 05:32:25PM -0400, Theodore Ts'o wrote:
> With the changes in the random tree, IRQF_SAMPLE_RANDOM is now a
> no-op; interrupt randomness is now collected unconditionally in a very
> low-overhead fashion; see commit 775f4b297b. The IRQF_SAMPLE_RANDOM
> flag was scheduled to
New name reflects purpose (count mem used), verbose is just print
condition, and bytes is too generic.
Signed-off-by: Jim Cromie
---
lib/dynamic_debug.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lib/dynamic_debug.c b/lib/dynamic_debug.c
index 6bc34aa..0cc715c
dynamic_emit_prefix() currently separates modname, funcname, lineno
with ':'. This is complicates use of cut -d: , since the
field positions can change per callsite with dynamic-debug. So change
inter-field separator to '.' and keep the ':' prefix terminator.
This improves the situation, but
commit c4e00daaa96d3a0786f1f4fe6456281c60ef9a16 changed __dev_printk
in a way that broke dynamic-debug's ability to control the dynamic
prefix of dev_dbg(dev,..), but not dev_dbg(NULL,..) or pr_debug(..),
which is why it wasnt noticed sooner.
When dev==NULL, __dev_printk() just calls printk(),
commit c4e00daaa96d3a0786f1f4fe6456281c60ef9a16 changed __dev_printk
in a way that broke dynamic-debug's ability to control the dynamic
prefix of dev_dbg(dev,..), but not dev_dbg(NULL,..) or pr_debug(..),
which is why it wasnt noticed sooner.
When dev==NULL, __dev_printk() just calls printk(),
3 patches here, 1st is bugfix, others are trivial.
1- fix __dev_printk, which broke dev_dbg() prefix under CONFIG_DYNAMIC_DEBUG.
2- change dyndbg prefix interfield separator from ':' to '.'
for example (output from test-code, not submitted):
r8169 :02:00.0: r8169.rtl_init_one: set-drvdata
On Wed, Jul 18, 2012 at 8:28 PM, David Sterba wrote:
> On Fri, Jul 13, 2012 at 10:19:14AM -0500, Mitch Harder wrote:
>> I was testing the lz4(hc) patches, and I found the the compression
>> INCOMPAT flags are not being updated using the method in this patch.
>>
>> The compression INCOMPAT flags
On Thu, 2012-07-19 at 11:28 -0600, Toshi Kani wrote:
> On Thu, 2012-07-19 at 10:15 -0600, Shuah Khan wrote:
> > On Wed, 2012-07-18 at 18:38 -0600, Toshi Kani wrote:
> >
> > >
> > > This interface is defined in acpi/acpi_bus.h, which is intended for ACPI
> > > drivers which make many ACPI calls
On Thursday, July 19, 2012, Carsten Emde wrote:
> There are two cpuidle governors ladder and menu. While the ladder
> governor is always available, if CONFIG_CPU_IDLE is selected, the
> menu governor additionally requires CONFIG_NO_HZ.
>
> A particular C state can be disabled by writing to the
When an AER event occurs not all of the print notifications are at the
same log level. This can cause an incomplete AER log from the users
point of view when monitoring the console output.
The completion message in do_recovery() is currently set to KERN_DEBUG
(log level 7) while the starting
There are two cpuidle governors ladder and menu. While the ladder
governor is always available, if CONFIG_CPU_IDLE is selected, the
menu governor additionally requires CONFIG_NO_HZ.
A particular C state can be disabled by writing to the sysfs file
Rafael,
>> [..]
>> I could implement a sanitize mechanism of the ladder governor that
>> takes care the "disable" variables of all deeper states are set to 1,
>> if a state is disabled, and those of all lighter states are set to 0,
>> if a state is enabled. Do you wish me to
On Thu, 2012-07-19 at 12:56 -0600, Betty Dall wrote:
> Thanks for the comment Joe. It looks like Roland already accepted the
> trivial change.
No worries.
> On Thu, 2012-07-19 at 11:03 -0700, Joe Perches wrote:
> > On Thu, 2012-07-19 at 13:34 -0600, Betty Dall wrote:
[]
> > > diff --git
On Thu, 19 Jul 2012, Andreas Mohr wrote:
> Hi,
>
> On Thu, Jul 19, 2012 at 11:11:50AM -0400, Alan Stern wrote:
> > On Thu, 19 Jul 2012, Andreas Mohr wrote:
> >
> > > Hi,
> > >
> > > Yesterday I was surprised to see that with *another* external USB disk
> > > happening to be connected before
We will need some of these values in mce.c. Move them to the
appropriate header file so they are available.
Signed-off-by: Tony Luck
---
arch/x86/include/asm/mce.h| 8
arch/x86/kernel/cpu/mcheck/mce-severity.c | 7 ---
2 files changed, 8 insertions(+), 7
Sandy Bridge processors follow the SDM (Vol 3B, Table 15-20) and set
both the RIPV and EIPV bits in the MCG_STATUS register to zero for
machine checks during instruction fetch. This is more than a little
counter-intuitive and means that Linux cannot recover from these
errors. Rather than insert
This patch series adds a workaround for some strange
asymmetry between how machine checks are reported for
data and instruction fetches. For instruction fetch
error the processor does not set the EIPV bit in the
MCG_STATUS register on the affected processor, leading
us to believe that the cs/ip
On 19 July 2012 20:58, Jaehoon Chung wrote:
> Hi Thomas,
>
> I think not good that added the samsung specific code into dw_mmc-pltfm.c
> How about separating to dw-mmc-exynos.c?
I am not sure of this. The only samsung specific code in
dw_mmc-pltfm.c file is the data for of_device_id instances.
Hi Joe,
Thanks for the comment Joe. It looks like Roland already accepted the
trivial change.
On Thu, 2012-07-19 at 11:03 -0700, Joe Perches wrote:
> On Thu, 2012-07-19 at 13:34 -0600, Betty Dall wrote:
> > There is a cut and paste typo in the function qib_pci_slot_reset() where
> > it prints
On Thu, 2012-07-19 at 20:49 +0200, Geert Uytterhoeven wrote:
> > I believe Alan was more correct than me when he said it was 'make
> > oldconfig' that produced the warnings.
>
> Kconfig does spit out warnings for selecting things with unmet dependencies.
> But does anyone care?
>
> [...checking
On Thu, Jul 19, 2012 at 07:53:10PM +0200, Borislav Petkov wrote:
> On Thu, Jul 19, 2012 at 10:06:44AM -0700, Linus Torvalds wrote:
> > On Thu, Jul 19, 2012 at 9:48 AM, Borislav Petkov wrote:
> > >
> > > Seriously, this helps only in the cases where the stuff the distro
> > > actually needs is in
On Thu, Jul 19, 2012 at 8:22 PM, Josh Boyer wrote:
> On Thu, Jul 19, 2012 at 08:20:36PM +0200, Paul Bolle wrote:
>> On Thu, 2012-07-19 at 13:19 -0400, Josh Boyer wrote:
>> > kconfig already spits out warnings for symbols being selected that
>> > don't exist.
>
>> Does it? Since when does it do
On 19 July 2012 09:21, Seungwon Jeon wrote:
> Hi,
>
> This version does not seems to consider previous reviews fully.
> Could you check the comments below?
I did try to address all the comments. I will check again and resubmit
if I have missed anything.
>
> July 12, 2012, Thomas Abraham wrote:
On Thu, 2012-07-19 at 20:45 +0300, Michael S. Tsirkin wrote:
> On Thu, Jul 19, 2012 at 11:29:38AM -0600, Alex Williamson wrote:
> > On Thu, 2012-07-19 at 19:59 +0300, Michael S. Tsirkin wrote:
> > > On Mon, Jul 16, 2012 at 02:33:38PM -0600, Alex Williamson wrote:
> > > > v5:
> > > > - irqfds now
> I understand the usefulness of this functionality, but I also worry
> about proliferating the number of properties for devices (there are
> only 32 bits we can use, IIRC). I see four options off the top of my
> head:
>
> * Don't do anything, leave it as SEMI_MT. Obviously this would suck,
> but
Hi,
On Thursday, July 19, 2012, Carsten Emde wrote:
> Deepthi,
>
> >>> [..]
> I could implement a sanitize mechanism of the ladder governor that
> takes care the "disable" variables of all deeper states are set to 1,
> if a state is disabled, and those of all lighter states are
On Thu, Jul 19, 2012 at 02:13:40PM -0400, Steven Rostedt wrote:
> On Thu, 2012-07-19 at 13:56 -0400, Josh Boyer wrote:
>
> > Distros aren't stationary things.
>
> Exactly my point.
>
> > I mean, some of them certainly aim
> > for that goal, but userspace and kernels get upgraded all the time.
On Thu, 2012-07-19 at 08:52 -0400, Steven Rostedt wrote:
> On Thu, 2012-07-19 at 11:20 +0900, Masami Hiramatsu wrote:
> > (2012/07/19 0:59), Steven Rostedt wrote:
> > > On Fri, 2012-07-13 at 14:47 -0400, Steven Rostedt wrote:
> > >
> > > Masami, can you give your Reviewed-by tag for this version?
thanks, applied.
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Thu, Jul 19, 2012 at 08:20:36PM +0200, Paul Bolle wrote:
> On Thu, 2012-07-19 at 13:19 -0400, Josh Boyer wrote:
> > kconfig already spits out warnings for symbols being selected that
> > don't exist.
>
> Does it? Since when does it do that? Or do you mean select in a more
> general way (not
On Thu, 2012-07-19 at 13:19 -0400, Josh Boyer wrote:
> kconfig already spits out warnings for symbols being selected that
> don't exist.
Does it? Since when does it do that? Or do you mean select in a more
general way (not just meaning Kconfig's "select" statement)?
Paul Bolle
--
To
On Thu, Jul 19, 2012 at 11:28 AM, Attila Kinali wrote:
> Hi,
>
> I'm working on an embedded system based on a Freescale ARM9 processor i.mx23.
>
> While trying linux-next i stumpled over my login prompt getting broken.
> What exactly happens is that the kernel boots normally, but when my
> login
On 16.07.2012 18:14, Bjorn Helgaas wrote:
> [CC +tglx]
>
> On Sun, Jul 15, 2012 at 2:25 PM, Rafael J. Wysocki wrote:
>> CC-ing linux-pci and Bjorn.
>>
>> On Sunday, July 15, 2012, Malte Schröder wrote:
>>> Hello,
>>> this is yet another try to get someone to look at this ;)
>>>
>>> I can't get
On Thu, 2012-07-19 at 13:56 -0400, Josh Boyer wrote:
> Distros aren't stationary things.
Exactly my point.
> I mean, some of them certainly aim
> for that goal, but userspace and kernels get upgraded all the time. So
> if this distro-Kconfig file is provided by some package _other_ than the
On Thu, Jul 19, 2012 at 01:57:26PM -0400, Steven Rostedt wrote:
> Yes, I know you know this already, as we discussed it in a pub over a
> beer (choir practice). But this is a public forum on LKML (the church),
> where I now have an audience of heathens. Convert! Convert! You are all
> sinners!
On Thu, 2012-07-19 at 13:34 -0600, Betty Dall wrote:
> There is a cut and paste typo in the function qib_pci_slot_reset() where
> it prints that the "link_reset" function is called rather than the
> "slot_reset" function. This makes the message misleading.
Hi Betty.
> diff --git
On Thursday, July 19, 2012 5:42 AM, Ian Abbott wrote:
> On 2012-07-19 03:05, H Hartley Sweeten wrote:
>> Use the hw_dev pointer in the comedi_device struct to hold the
>> pci_dev instead of carrying it in the private data.
>
> My reply to patch 86 has a knock-on effect for this patch...
>
>>
On Thu, 2012-07-19 at 19:34 +0200, Borislav Petkov wrote:
> > I can pass the above to a allnoconfig, and the box will boot and allow
> > ssh. Note, the reason for the serial config, is that this ktest run uses
> > a serial port to see if the box booted. If the serial isn't there, then
> > it
On Thu, Jul 19, 2012 at 01:33:42PM -0400, Steven Rostedt wrote:
> On Thu, 2012-07-19 at 13:19 -0400, Josh Boyer wrote:
>
> > > What about older kernels? Say you installed Fedora 18 with an older
> > > kernel that doesn't know what to select? Having the distro tell the
> > > kernel what it needs
On Thu, Jul 19, 2012 at 10:06:44AM -0700, Linus Torvalds wrote:
> On Thu, Jul 19, 2012 at 9:48 AM, Borislav Petkov wrote:
> >
> > Seriously, this helps only in the cases where the stuff the distro
> > actually needs is in modules. So, there probably are obscure situations
> > where you need to
On 07/19/2012 07:50 AM, Mitsuo Hayasaka wrote:
> Add an explanation about the sysfs parameter to limit the
> maximum read/write request size.
>
> Signed-off-by: Mitsuo Hayasaka
> Cc: Rob Landley
> Cc: Miklos Szeredi
> Cc: Nikolaus Rath
> Cc: Liu Yuan
> Cc: Has-Wen Nienhuys
> ---
Acked-by:
The dma_map and dma_unmap should have same parameter
passed otherwise we get the below warn.
ks8851 spi1.0: DMA-API: device driver tries to free DMA memory it has not
allocated [device address=0x9f22]
[2.066925] Modules linked in:
[2.070312]
[2.071929] []
On Thu, Jul 19, 2012 at 11:29:38AM -0600, Alex Williamson wrote:
> On Thu, 2012-07-19 at 19:59 +0300, Michael S. Tsirkin wrote:
> > On Mon, Jul 16, 2012 at 02:33:38PM -0600, Alex Williamson wrote:
> > > v5:
> > > - irqfds now have a one-to-one mapping with eoifds to prevent users
> > >from
Introduce a wrapper for to_pci_dev() to allow the comedi_pci_drivers
to store the pci_dev pointer in the comedi_device hw_dev variable and
retrieve it easily.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbot
Cc: Greg Kroah-Hartman
---
v2: Ian Abbott pointed out that the dev->hw_dev needs to be
On Thu, Jul 19, 2012 at 06:30:47PM +0100, Alan Cox wrote:
>
> > Well, yes. I was thinking it would be more like:
> >
> > distro/Kconfig.fedora
> > menuconfig FEDORA
> > if FEDORA
> > config FEDORA_16
> >select WHATEVER
> > config FEDORA_17
>
> Nope you need
>
>
> > kconfig already spits out warnings for symbols being selected that
> > don't exist.
>
> We can make these even bigger :-) Add lots of stars (*) around them!
Make oldconfig already handles this just fine
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
There is a cut and paste typo in the function qib_pci_slot_reset() where
it prints that the "link_reset" function is called rather than the
"slot_reset" function. This makes the message misleading.
Signed-off-by: Betty Dall
---
drivers/infiniband/hw/qib/qib_pcie.c |2 +-
1 files changed, 1
Hi,
I'm working on an embedded system based on a Freescale ARM9 processor i.mx23.
While trying linux-next i stumpled over my login prompt getting broken.
What exactly happens is that the kernel boots normally, but when my
login prompt should appear it suddenly stops. I bisected it back to
the
101 - 200 of 952 matches
Mail list logo
