Just one minor issue. Check below.
On 12/21/2012 07:39 PM, Terje Bergstrom wrote:
> Add support for host1x client modules, and host1x channels to submit
> work to the clients. The work is submitted in GEM CMA buffers, so
> this patch adds support for them.
>
> Signed-off-by: Terje Bergstrom
>
On Wed, 2 Jan 2013, Tony Prisk wrote:
On Wed, 2013-01-02 at 08:10 +0300, Dan Carpenter wrote:
clk_get() returns NULL if CONFIG_HAVE_CLK is disabled.
I told Tony about this but everyone has been gone with end of year
holidays so it hasn't been addressed.
Tony, please fix it so people don't
On Wed, 2013-01-02 at 10:45 +0800, joeyli wrote:
> I didn't find the EFI RTC problem on Asus from google.
> Could you please share what's the situation on ASUS hardware?
It's mentioned in the following commit (which has since been reverted in
Linus' tree),
commit
On Tuesday 13 November 2012 01:59 AM, Thomas Gleixner wrote:
> On Wed, 7 Nov 2012, Vineet Gupta wrote:
>> +void cpu_idle(void)
>> +{
>> +/* Since we SLEEP in idle loop, TIF_POLLING_NRFLAG can't be set */
>> +
>> +/* endless idle loop with no priority at all */
>> +while (1) {
>> +
Does anyone know if the Tyan Thunder K8W (s2885) has a BMC controller
for IPMI management on board? If it does, what do I have to enable in
the kernel to use it?
Cheers,
James
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Haven't had a chance to benchmark it yet due to system troubles in the
wake of a botched emerge, but from what I can tell the "write a
promise" logic seems to be much smoother than btrfs's recursive
cow'ing.
>From what I can tell on the design, tux3 is "fsync satiating" with a
single disk write.
On Wed, Jan 2, 2013 at 1:30 AM, Kim, Milo wrote:
> TI LP8788 PMU supports regulators, battery charger, RTC, ADC, backlight driver
> and current sinks.
> This patch enables LP8788 rtc module.
>
> Patch v4.
> when alarm IRQ number is not specified, RTC_AIE_ON ioctl returns as -EIO
> remove
TI LP8788 PMU supports regulators, battery charger, RTC, ADC, backlight driver
and current sinks.
This patch enables LP8788 rtc module.
Patch v4.
when alarm IRQ number is not specified, RTC_AIE_ON ioctl returns as -EIO
remove unnecessary platform data check routine
fix wrong parent device
On 16 December 2012 19:07, Viresh Kumar wrote:
> On 16 December 2012 18:34, Rafael J. Wysocki wrote:
>> Well, this series makes sense to me, but I'd like to hear what the other
>> people
>> think.
>
> That sounds great :)
>
> Some more information for others about how i reached to these issues
Signed-off-by: Lad, Prabhakar
Cc: Sylwester Nawrocki
Cc: Kyungmin Park
---
Documentation/video4linux/fimc.txt |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/video4linux/fimc.txt
b/Documentation/video4linux/fimc.txt
index fd02d9a..25f4d34 100644
---
On 8 November 2012 13:33, Viresh Kumar wrote:
> We are first storing the new vruntime in a variable and then storing it in
> se->vruntime. Simply update se->vruntime directly.
>
> Signed-off-by: Viresh Kumar
> ---
> kernel/sched/fair.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
On 21.12.2012 23:19, Stephen Warren wrote:
> * There's host1x hardware.
>
> * There's a low-level driver just for host1x itself; the host1x driver.
>
> * There's a high-level driver for the entire host1x complex of devices.
> That is tegradrm. There may be more high-level drivers in the future
>
On Wed, 2013-01-02 at 08:10 +0300, Dan Carpenter wrote:
> clk_get() returns NULL if CONFIG_HAVE_CLK is disabled.
>
> I told Tony about this but everyone has been gone with end of year
> holidays so it hasn't been addressed.
>
> Tony, please fix it so people don't apply these patches until
>
Larry Finger wrote:
> My only counter argument is that none of the other paths that get to
> ath9k_htc_txcompletion_cb() leak the skb. It only happens for the path that
> goes
> through htc_connect_service().
Sure, but the TX completion handler would be invoked for every skb that is
passed
to
The ->disksize variable stores values in units of bytes,
print the correct size in Kb
Signed-off-by: Davidlohr Bueso
---
drivers/staging/zram/zram_drv.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/zram/zram_drv.c b/drivers/staging/zram/zram_drv.c
index
It seems like an overkill to have adding and subtracting
1 functions from the 32bit counters. Just do it directly.
Signed-off-by: Davidlohr Bueso
---
drivers/staging/zram/zram_drv.c | 26 --
1 file changed, 8 insertions(+), 18 deletions(-)
diff --git
Simplify dealing with num_devices when initializing zram.
Also cleanup some of the output messages.
Signed-off-by: Davidlohr Bueso
---
drivers/staging/zram/zram_drv.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git a/drivers/staging/zram/zram_drv.c
On Wednesday 02 January 2013 06:19 AM, Rusty Russell wrote:
> Sam Ravnborg writes:
>
>> On Thu, Dec 27, 2012 at 04:17:20PM +0530, Vineet Gupta wrote:
>>> ARC relocatable object files contain one/more .gnu.linkonce.arcextmap.*
>>> sections (collated by kernel/vmlinux.lds into .arcextmap in final
clk_get() returns NULL if CONFIG_HAVE_CLK is disabled.
I told Tony about this but everyone has been gone with end of year
holidays so it hasn't been addressed.
Tony, please fix it so people don't apply these patches until
clk_get() is updated to not return NULL. It sucks to have to revert
Paolo Bonzini writes:
> The virtqueue_add_buf function has two limitations:
>
> 1) it requires the caller to provide all the buffers in a single call;
>
> 2) it does not support chained scatterlists: the buffers must be
> provided as an array of struct scatterlist;
Chained scatterlists are a
Sam Ravnborg writes:
> On Thu, Dec 27, 2012 at 04:17:20PM +0530, Vineet Gupta wrote:
>> ARC relocatable object files contain one/more .gnu.linkonce.arcextmap.*
>> sections (collated by kernel/vmlinux.lds into .arcextmap in final link).
>> This section is used by debuggers to display the
Tejun Heo writes:
> (cc'ing Rusty, hi!)
>
> Hello, Li.
>
> On Wed, Dec 26, 2012 at 06:20:11PM +0800, Li Zefan wrote:
>> On 2012/11/29 5:34, Tejun Heo wrote:
>> > cpuset_can_attach() prepare global variables cpus_attach and
>> > cpuset_attach_nodemask_{to|from} which are used by cpuset_attach().
On 01/01/2013 10:30 PM, Sujith Manoharan wrote:
Larry Finger wrote:
diff --git a/drivers/net/wireless/ath/ath9k/htc_hst.c
b/drivers/net/wireless/ath/ath9k/htc_hst.c
index 4a9570d..a304748 100644
--- a/drivers/net/wireless/ath/ath9k/htc_hst.c
+++ b/drivers/net/wireless/ath/ath9k/htc_hst.c
@@
Larry Finger wrote:
> diff --git a/drivers/net/wireless/ath/ath9k/htc_hst.c
> b/drivers/net/wireless/ath/ath9k/htc_hst.c
> index 4a9570d..a304748 100644
> --- a/drivers/net/wireless/ath/ath9k/htc_hst.c
> +++ b/drivers/net/wireless/ath/ath9k/htc_hst.c
> @@ -278,10 +278,12 @@ int
Hi everyone,
I have been looking at how different workloads react when the per entity
load tracking metric is integrated into the load balancer and what are
the possible reasons for it.
I had posted the integration patch earlier:
https://lkml.org/lkml/2012/11/15/391
Essentially what I am doing
On 2 January 2013 09:40, Larry Finger wrote:
>>> Index: wireless-testing-new/drivers/cpufreq/cpufreq_governor.c
>>
>>
>> How are you creating these patches? wireless-testing-new (linux directory
>> names)
>> aren't supposed to be present here.
You Missed this one?
> I was not adding myself - my
Hi all,
Changes since 20121224:
The driver-core.current tree gained a conflict against Linus' tree.
The s390 tree gained a conflict against the driver-core.current tree.
The v4l-dvb tree gained a conflict against the driver-core.current tree.
The drivers-x86 tree gained conflicts against the
On 01/01/2013 09:56 PM, Viresh Kumar wrote:
I know, V4 is already accepted, but i had an small comment with one
of your earlier change, which doesn't exist anymore :)
On Sat, Dec 29, 2012 at 5:51 AM, Larry Finger wrote:
Index: wireless-testing-new/drivers/cpufreq/cpufreq_governor.c
How are
I know, V4 is already accepted, but i had an small comment with one
of your earlier change, which doesn't exist anymore :)
On Sat, Dec 29, 2012 at 5:51 AM, Larry Finger wrote:
> Index: wireless-testing-new/drivers/cpufreq/cpufreq_governor.c
How are you creating these patches?
On Sat, Dec 29, 2012 at 6:57 PM, Rafael J. Wysocki wrote:
> On Friday, December 28, 2012 07:55:20 PM Larry Finger wrote:
>> V3 changes only Kconfig and Makefile and avoids creating a new module.
>
> OK, thanks for the patch!
>
> If you don't mind, I'll rename CONFIG_CPU_FREQ_GOVERNOR to
>
Running with kmemleak shows that this driver leaks every skb allocated in
routine htc_connect_service() whether the service connection succeeds or
fails.
Signed-off-by: Larry Finger
Cc: Stable
Cc: "Luis R. Rodriguez"
Cc: Vasanthakumar Thiagarajan
Cc: Senthil Balasubramanian
Cc:
Hi Al,
Today's linux-next merge of the signal tree got a conflict in
arch/mips/kernel/syscall.c between commit 12890d0f61fc ("MIPS: sysmips:
Rewrite to use SYSCALL_DEFINE3()") from the mips tree and commit
cc524ca3714b ("mips: kill sysmips() wrapper, switch to SYSCALL_DEFINE")
from the signal
Hi hpa,
於 五，2012-12-28 於 15:44 -0800，H. Peter Anvin 提到：
> On 12/28/2012 12:49 PM, Matthew Garrett wrote:
> > On Fri, 2012-12-28 at 12:40 -0800, H. Peter Anvin wrote:
> >
> >>> I suspect that what we *should* do looks like:
> >>>
> >>> 1. If ACPI exports a Time and Alarm Device (ACPI000E) the
Hi Matthew,
Today's linux-next merge of the drivers-x86 tree got conflicts in
drivers/platform/x86/apple-gmux.c, drivers/platform/x86/compal-laptop.c,
drivers/platform/x86/fujitsu-tablet.c,
drivers/platform/x86/ideapad-laptop.c,
drivers/platform/x86/intel_oaktrail.c and
NAK, we don't need to do this.
There is no relationship between kmem_cache_* and free_nid_list_lock.
Moreover, IMO, it would be better unlock free_nid_list_lock as quickly
as possible in order to reduce lock contention.
2012-12-30 (일), 14:52 +0900, Namjae Jeon:
> From: Namjae Jeon
>
> Cache
On Tue, Jan 1, 2013 at 11:56 PM, Toralf Förster wrote:
> I found this in the syslog (sry for the big unnecessary JPEG in the previous
> message,
> I wasn't aware, that the syslogd was still working):
>
> 2013-01-01T12:15:28.000+01:00 n22 ntpd[3095]: Listen normally on 5 ppp0
> 80.171.221.184
On Wed, Jan 02, 2013 at 02:38:18AM +0100, Samuel Thibault wrote:
> Greg Kroah-Hartman, le Tue 01 Jan 2013 17:17:22 -0800, a écrit :
> > On Tue, Jan 01, 2013 at 11:52:57PM +0100, Samuel Thibault wrote:
> > > This prefixes all externally-visible symbols of speakup with "spk_".
> > > (or makes static
On 12/25/2012 06:50 AM, Shuah Khan wrote:
On Sun, Dec 23, 2012 at 6:31 AM, Borislav Petkov wrote:
On Sun, Dec 23, 2012 at 01:22:12PM +0100, Borislav Petkov wrote:
Right, let me try that and report back.
Yep, looks like reverting the above commit fixes it - the boston.com
website loads just
Greg Kroah-Hartman, le Tue 01 Jan 2013 17:17:22 -0800, a écrit :
> On Tue, Jan 01, 2013 at 11:52:57PM +0100, Samuel Thibault wrote:
> > This prefixes all externally-visible symbols of speakup with "spk_".
> > (or makes static some of them which do not actually need to be
> > externally-visible)
>
Turn static some symbols which do not actually need to be
externally-visible
Signed-off-by: Samuel Thibault
diff -ur linux/drivers/staging/speakup-orig/fakekey.c
linux/drivers/staging/speakup/fakekey.c
--- linux/drivers/staging/speakup-orig/fakekey.c2011-10-24
09:10:05.0 +0200
On Tue, Jan 01, 2013 at 11:52:57PM +0100, Samuel Thibault wrote:
> This prefixes all externally-visible symbols of speakup with "spk_".
> (or makes static some of them which do not actually need to be
> externally-visible)
Care to break this up into smaller pieces? Like one for the variables
Hi Mauro,
Today's linux-next merge of the v4l-dvb tree got a conflict in
drivers/media/pci/dm1105/dm1105.c between commit 598759dec35a ("Drivers:
media: remove __dev* attributes") from the driver-core.current tree and
commit 73f0af44a913 ("[media] make the other drivers take use of the new
ts2020
Simple fixed value proportional backoff for ticket spinlocks.
By pounding on the cacheline with the spin lock less often,
bus traffic is reduced. In cases of a data structure with
embedded spinlock, the lock holder has a better chance of
making progress.
Note that when a thread notices that it's
Just cosmetic - avoid an unnecessary goto construct
Signed-off-by: Michel Lespinasse
---
arch/x86/include/asm/spinlock.h |7 ++-
1 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/arch/x86/include/asm/spinlock.h b/arch/x86/include/asm/spinlock.h
index
On Fri, Dec 21, 2012 at 3:49 PM, Rik van Riel wrote:
> Many spinlocks are embedded in data structures; having many CPUs
> pounce on the cache line the lock is in will slow down the lock
> holder, and can cause system performance to fall off a cliff.
>
> The paper "Non-scalable locks are
On Tuesday 01 January 2013 23:44:38 Alexey Khoroshilov wrote:
> On 01/02/2013 01:45 AM, Christian Lamparter wrote:
> > On Tuesday 01 January 2013 22:11:01 Alexey Khoroshilov wrote:
> >> If pci_set_dma_mask() or pci_set_consistent_dma_mask() fails in
> >> p54p_probe(),
> >> it breaks off
Linus Torvalds wrote:
> Please document the barrier that this mb() pairs with, and then give
> an explanation for the fix in the commit message, and I'll happily
> take it. Even if it's just duplicating the comments above the
> wq_has_sleeper() function, except modified for the ep_modify() case.
Hi all,
Today's linux-next merge of the s390 tree got a conflict in
arch/s390/kernel/smp.c between commit c8925a6e95b2 ("ARCH: drivers remove
__dev* attributes") from the driver-core.current tree and commit
5059e4342f93 ("s390/smp: fix section mismatch for smp_add_present_cpu()")
from the s390
Hi Greg,
Today's linux-next merge of the driver-core.current tree got a conflict
in drivers/i2c/busses/i2c-au1550.c between commit 0b255e927d47 ("i2c:
remove __dev* attributes from subsystem") from Linus' tree and commit
eeb30d064414 ("Drivers: i2c: remove __dev* attributes") from the
Hi all,
The alternate patch from Eric works well too. Even though I didn't see
a performance boost compared with the old version, this one is clearer
to me. Thanks your guys.
Cheers!
--Jason
On Tue, Jan 1, 2013 at 5:53 PM, Linus Torvalds
wrote:
> On Tue, Jan 1, 2013 at 1:17 PM, Eric Wong
Throughout compiler*.h, many version checks are made. These can be
simplified by using the macro that gcc's documentation recommends.
However, my primary reason for adding this is that I need bug-check
macros that are enabled at certain gcc versions and it's cleaner to use
this macro than the
Using GCC_VERSION reduces complexity, is easier to read and is GCC's
recommended mechanism for doing version checks. (Just don't ask me why
they didn't define it in the first place.) This also makes it easy to
merge compiler-gcc{,3,4}.h should somebody want to.
Signed-off-by: Daniel Santos
Well, it looks like my new version of git properly handles the
--in-reply-to switch now, so this patch set shouldn't be oddly threaded
like the last version.
include/linux/bug.h | 47 ++--
include/linux/compiler-gcc.h |3 ++
When calling BUILD_BUG_ON in an optimized build using gcc 4.3 and later,
the condition will be evaulated twice, possibily with side-effects.
This patch eliminates that error.
Signed-off-by: Daniel Santos
---
include/linux/bug.h |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
Prior to the introduction of __attribute__((error("msg"))) in gcc 4.3,
creating compile-time errors required a little trickery.
BUILD_BUG{,_ON} uses this attribute when available to generate
compile-time errors, but also uses the negative-sized array trick for
older compilers, resulting in two
__linktime_error() does the same thing as __compiletime_error() and is
only used in bug.h. Since the macro defines a function attribute that
will cause a failure at compile-time (not link-time), it makes more
sense to keep __compiletime_error(), which is also neatly mated with
Introduce compiletime_assert to compiler.h, which moves the details of
how to break a build and emit an error message for a specific compiler
to the headers where these details should be. Following in the tradition
of the POSIX assert macro, compiletime_assert creates a build-time error
when the
When __CHECKER__ is defined, we disable all of the BUILD_BUG.* macros.
However, both BUILD_BUG_ON_NOT_POWER_OF_2 and BUILD_BUG_ON was
evaluating to nothing in this case, and we want (0) since this is a
function-like macro that will be followed by a semicolon.
Signed-off-by: Daniel Santos
Negative sized arrays wont create a compile-time error in some cases
starting with gcc 4.4 (e.g., inlined functions), but gcc 4.3 introduced
the error function attribute that will. This patch modifies
BUILD_BUG_ON to behave like BUILD_BUG already does, using the error
function attribute so that
This helps to keep the file from getting confusing, removes one
duplicate version check and should encourage future editors to put new
macros where they belong.
Signed-off-by: Daniel Santos
Acked-by: David Rientjes
Acked-by: Borislav Petkov
---
include/linux/compiler-gcc4.h | 20
On Tue, Jan 1, 2013 at 1:17 PM, Eric Wong wrote:
>>
>> An alternate version (limited to epoll) would be:
>>
>> diff --git a/fs/eventpoll.c b/fs/eventpoll.c
>> index cd96649..ca5f3d0 100644
>> --- a/fs/eventpoll.c
>> +++ b/fs/eventpoll.c
>> @@ -1299,6 +1299,7 @@ static int ep_modify(struct
On Wed 2012-12-12 20:10:16, NeilBrown wrote:
> On Wed, 12 Dec 2012 09:58:16 +0100 Ondřej Bílka wrote:
>
> > On Wed, Dec 12, 2012 at 01:08:26PM +1100, NeilBrown wrote:
> > > On Wed, 12 Dec 2012 03:03:54 +0100 Ondřej Bílka wrote:
> > >
> > > > I consider to speed-up /dev/urandom on recent intel
On 01/02/2013 01:45 AM, Christian Lamparter wrote:
On Tuesday 01 January 2013 22:11:01 Alexey Khoroshilov wrote:
If pci_set_dma_mask() or pci_set_consistent_dma_mask() fails in p54p_probe(),
it breaks off initialization, deallocates all resources, but returns zero.
The patch implements proper
Hi Martin,
Thanks for the "tux3 howto". Obviously tux3.org needs refresh, but you hit the
main points.
On Tuesday, January 01, 2013 03:37:08 PM you wrote:
> Writing a file with
>
> ./tux3 write tux3.img /etc/fstab
>
> also seemed to work, but I gave up holding down the enter key at:
>
>
On Tuesday 01 January 2013 22:11:01 Alexey Khoroshilov wrote:
> If pci_set_dma_mask() or pci_set_consistent_dma_mask() fails in p54p_probe(),
> it breaks off initialization, deallocates all resources, but returns zero.
>
> The patch implements proper error code propagation.
Uh, Thanks!
But
On 01/01/2013 03:09 PM, danielfsan...@att.net wrote:
#ifdef CONFIG_ARCH_USE_BUILTIN_BSWAP
-#if __GNUC_MINOR__>= 4
+#if GCC_VERSION>= 40400
#define __HAVE_BUILTIN_BSWAP32__
#define __HAVE_BUILTIN_BSWAP64__
#endif
-#if __GNUC_MINOR__>= 8 || (defined(__powerpc__)&& __GNUC_MINOR__>= 6)
Eric Wong wrote:
> Eric Dumazet wrote:
> > commit 626cf236608505d376e4799adb4f7eb00a8594af should not have this
> > side effect, at least for poll()/select() functions. The epoll() changes
> > I am not yet very confident.
>
> I have a better explanation of the epoll problem below.
>
> An
Using GCC_VERSION reduces complexity, is easier to read and is GCC's
recommended mechanism for doing version checks. (Just don't ask me why
they didn't define it in the first place.) This also makes it easy to
merge compiler-gcc{,3,4}.h should somebody want to.
Signed-off-by: Daniel Santos
Throughout compiler*.h, many version checks are made. These can be
simplified by using the macro that gcc's documentation recommends.
However, my primary reason for adding this is that I need bug-check
macros that are enabled at certain gcc versions and it's cleaner to use
this macro than the
When calling BUILD_BUG_ON in an optimized build using gcc 4.3 and later,
the condition will be evaulated twice, possibily with side-effects.
This patch eliminates that error.
Signed-off-by: Daniel Santos
---
include/linux/bug.h |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
Introduce compiletime_assert to compiler.h, which moves the details of
how to break a build and emit an error message for a specific compiler
to the headers where these details should be. Following in the tradition
of the POSIX assert macro, compiletime_assert creates a build-time error
when the
__linktime_error() does the same thing as __compiletime_error() and is
only used in bug.h. Since the macro defines a function attribute that
will cause a failure at compile-time (not link-time), it makes more
sense to keep __compiletime_error(), which is also neatly mated with
If pci_set_dma_mask() or pci_set_consistent_dma_mask() fails in p54p_probe(),
it breaks off initialization, deallocates all resources, but returns zero.
The patch implements proper error code propagation.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey
Negative sized arrays wont create a compile-time error in some cases
starting with gcc 4.4 (e.g., inlined functions), but gcc 4.3 introduced
the error function attribute that will. This patch modifies
BUILD_BUG_ON to behave like BUILD_BUG already does, using the error
function attribute so that
Prior to the introduction of __attribute__((error("msg"))) in gcc 4.3,
creating compile-time errors required a little trickery.
BUILD_BUG{,_ON} uses this attribute when available to generate
compile-time errors, but also uses the negative-sized array trick for
older compilers, resulting in two
When __CHECKER__ is defined, we disable all of the BUILD_BUG.* macros.
However, both BUILD_BUG_ON_NOT_POWER_OF_2 and BUILD_BUG_ON was
evaluating to nothing in this case, and we want (0) since this is a
function-like macro that will be followed by a semicolon.
Signed-off-by: Daniel Santos
This helps to keep the file from getting confusing, removes one
duplicate version check and should encourage future editors to put new
macros where they belong.
Signed-off-by: Daniel Santos
Acked-by: David Rientjes
Acked-by: Borislav Petkov
---
include/linux/compiler-gcc4.h | 26
include/linux/bug.h | 47 ++--
include/linux/compiler-gcc.h |3 ++
include/linux/compiler-gcc3.h |8 +++---
include/linux/compiler-gcc4.h | 36 +++---
include/linux/compiler.h | 32
Eric Dumazet wrote:
> On Mon, 2012-12-31 at 13:21 +, Eric Wong wrote:
> > This patch seems to fix my issue with ppoll() being stuck on my
> > SMP machine: http://article.gmane.org/gmane.linux.file-systems/70414
> >
> > The change to sock_poll_wait() in
> > commit
On Tue, Jan 1, 2013 at 3:17 PM, Peter Senna Tschudin
wrote:
> I'm not sure if I'm emailing the right people. My problem is with
> dynamic clock and or power management.
>
> I'm using 3.6.10-2.fc17.x86_64 but the exact same problem happen with
> non Fedora Kernels like 3.7.1 and 3.6.11.
>
> I'm
On 12/18/2012 06:34 PM, Tony Prisk wrote:
Resend to include mailing lists.
In the future please put such comments after the --- tear line below.
Replace IS_ERR_OR_NULL with IS_ERR on clk_get results.
Signed-off-by: Tony Prisk
CC: Kyungmin Park
CC: Tomasz Stanislawski
CC:
On Sat, Dec 29, 2012 at 12:19:10AM -0800, john.wens...@gmail.com wrote:
> On Thursday, December 27, 2012 4:08:46 AM UTC+2, Kent Overstreet wrote:
> ...
>
> Great. Did you measure by how much your changes improve performance?
This particular patch? No. As for the whole series, Jens has done the
Konstantin Khlebnikov wrote:
Seems like it's unrelated to e1000e driver itself, because I tried to
revert all it's changes down to 3.6 one by one and it does not help.
Looks like regression somewhere in pci-bus irq or power-management.
because I see underflow of counter pci_dev->enable_cnt:
On Mon, 2012-12-31 at 13:21 +, Eric Wong wrote:
> This patch seems to fix my issue with ppoll() being stuck on my
> SMP machine: http://article.gmane.org/gmane.linux.file-systems/70414
>
> The change to sock_poll_wait() in
> commit 626cf236608505d376e4799adb4f7eb00a8594af
> (poll: add
On 12/22/2012 10:53 PM, Sergei Shtylyov wrote:
Hello.
On 18-12-2012 21:34, Tony Prisk wrote:
Resend to include mailing lists.
Such remarks should be placed under --- tear line, not in the changelog.
Replace IS_ERR_OR_NULL with IS_ERR on clk_get results.
Signed-off-by: Tony Prisk
CC:
On 12/31/2012 05:06 PM, Dan Magenheimer wrote:
>> From: Seth Jennings [mailto:sjenn...@linux.vnet.ibm.com]
>> Subject: [PATCH 7/8] zswap: add to mm/
>>
>> zswap is a thin compression backend for frontswap. It receives
>> pages from frontswap and attempts to store them in a compressed
>> memory
On 12/26/2012 12:00 AM, Borislav Petkov wrote:
> On Sat, Dec 22, 2012 at 11:23:25AM +0100, Stefan Hasko wrote:
>> Fixed different size cast warnings in function setup_efi_pci
>>
>> Signed-off-by: Stefan Hasko
>
> You might want to add the actual compiler warnings to the commit
> message:
>
>
On 01/01/2013 07:55 AM, Shea Levy wrote:
> Hi all,
>
> In March last year, I submitted a patch to enable the EFI boot stub to
> read its config arguments from a file on the ESP, both to help with
> booting from livecds and to avoid having to use efibootmgr every time
> you change your boottime
Hi Eric and list,
Thanks a lot. The patch solves our (Andreas and my) issue in using
epoll. Here's our test program
https://github.com/AndreasVoellmy/epollbug/blob/master/epollbug.c We
are using Linux 3.7.1 and a server with 80 cores.
Cheers!
--Jason
On Mon, Dec 31, 2012 at 6:24 PM, Eric Wong
I found this in the syslog (sry for the big unnecessary JPEG in the previous
message,
I wasn't aware, that the syslogd was still working):
2013-01-01T12:15:28.000+01:00 n22 ntpd[3095]: Listen normally on 5 ppp0
80.171.221.184 UDP 123
2013-01-01T12:15:28.000+01:00 n22 ntpd[3095]: peers refreshed
Hi all,
In March last year, I submitted a patch to enable the EFI boot stub to
read its config arguments from a file on the ESP, both to help with
booting from livecds and to avoid having to use efibootmgr every time
you change your boottime arguments. I ended up dropping the submission
Woody Suwalski wrote:
Greg Kroah-Hartman wrote:
On Sun, Dec 23, 2012 at 02:35:49PM -0800, Linus Torvalds wrote:
Woody,
Any chance you can bisect this? It's not going to be hugely pleasant
(with 11k+ commits in between 3.7 and 3.8-rc1 you'll have to compile
and test at least 14 kernels), but
Am Dienstag, 1. Januar 2013 schrieb Daniel Phillips:
> On Tuesday, January 01, 2013 02:06:19 PM Martin Steigerwald wrote:
> > Sounds all good and nice and interesting to test, but where to grab the
> > source?
> >
> > I found no obvious URL.
>
> Hi Martin,
>
> Sorry about that, I knew I forgot
On Tue, 2013-01-01 at 22:31 +0900, Satoru Takeuchi wrote:
> Hi Ben,
>
> At Fri, 28 Dec 2012 20:04:02 +0100,
> Ben Hutchings wrote:
> >
> > 3.2-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Tejun Heo
> >
> > commit
Hi Ben,
At Fri, 28 Dec 2012 20:04:02 +0100,
Ben Hutchings wrote:
>
> 3.2-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Tejun Heo
>
> commit 5edee61edeaaebafe584f8fb7074c1ef4658596b upstream.
>
> cgroup core has a bug which violates
On Tuesday, January 01, 2013 02:06:19 PM Martin Steigerwald wrote:
> Sounds all good and nice and interesting to test, but where to grab the
> source?
>
> I found no obvious URL.
Hi Martin,
Sorry about that, I knew I forgot something:
git://github.com/OGAWAHirofumi/tux3.git
Warning: the
Also fixes some whitespace inconsistency in Kconfig and w1_family.h
when DS2408 chip support was added.
Signed-off-by: Mariusz Bialonczyk
---
drivers/w1/slaves/Kconfig | 13 ++-
drivers/w1/slaves/Makefile|3 +-
drivers/w1/slaves/w1_ds2413.c | 177
H. Peter Anvin zytor.com> writes:
>
> On 06/21/2012 03:22 PM, Uros Vampl wrote:
> >
> > I advised the Arch user to join this discussion and provide the
> > requested info. I immediately went for kbd as the solution because
> > that's exactly what I need for my own Aspire One - that AOA110
Hi Daniel,
Happy new year to you and everyone else!
Am Dienstag, 1. Januar 2013 schrieb Daniel Phillips:
[… long description on Tux3 design and current state …]
> We have made plausible plans for all of the above, but indeed the devil
> is in the doing. So we are considering the merits of
Hi Federico,
Em Thu, 20 Dec 2012 16:37:50 +0100
Federico Vaga escreveu:
> > I can take a look at the dma coherent issues with that board, but I
> will
> > need some help as I don't have this hardware.
>
> I have the hardware, but I don't have the full knowledge of the
> boards. As I told
1 - 100 of 212 matches
Mail list logo
