On Wed, Aug 15, 2012 at 5:48 PM, Miklos Szeredi wrote:
> From: Miklos Szeredi
>
> We need to be able to check inode permissions (but not filesystem implied
> permissions) for stackable filesystems. Expose this interface for overlayfs.
>
This patch can go through Al's vfs tree?
It's an addendum
On Wed, Aug 15, 2012 at 5:48 PM, Miklos Szeredi wrote:
> From: Miklos Szeredi
>
> Add a simple read-only counter to super_block that indicates deep this
> is in the stack of filesystems. Previously ecryptfs was the only
> stackable filesystem and it explicitly disallowed multiple layers of
> its
On Thu, Aug 16, 2012 at 10:02 AM, Sedat Dilek wrote:
> On Wed, Aug 15, 2012 at 5:48 PM, Miklos Szeredi wrote:
>> From: Miklos Szeredi
>>
>> Add a simple read-only counter to super_block that indicates deep this
>> is in the stack of filesystems. Previously ecryptf
On Fri, Aug 17, 2012 at 3:05 AM, Andrew Watts wrote:
>> Might be easier to collect/extract commits listed in [1]?
>>
>> If you are on Ubuntu: Check mainline kernels in [2] (quantal) and [3]
>> (precise).
>>
>> - Sedat -
>>
>
> That indeed was much easier and I have it working great on 3.5.2. Many
On Mon, Aug 20, 2012 at 12:38 PM, J. R. Okajima wrote:
>
> Sedat Dilek:
>> The other part to run a Linux live-system is a "Union FileSystem" -
>> this part is missing (speaking of upstream).
>>
>> Since years AUFS seems to be the choice #1 in a lot of distr
On Tue, Aug 21, 2012 at 8:04 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20120820:
>
> The rr tree gained a conflict against Linus' tree.
>
> The tip tree still has its build failure so I used the version from
> next-20120814.
>
> The workqueues tree gained a conflict against the hid t
On Tue, Aug 21, 2012 at 1:02 PM, Sedat Dilek wrote:
> On Tue, Aug 21, 2012 at 8:04 AM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> Changes since 20120820:
>>
>> The rr tree gained a conflict against Linus' tree.
>>
>> The tip tree still has
On Tue, Aug 21, 2012 at 1:03 PM, Sedat Dilek wrote:
> On Tue, Aug 21, 2012 at 1:02 PM, Sedat Dilek wrote:
>> On Tue, Aug 21, 2012 at 8:04 AM, Stephen Rothwell
>> wrote:
>>> Hi all,
>>>
>>> Changes since 20120820:
>>>
>>> The rr tree
On Tue, Aug 21, 2012 at 1:53 PM, Daniel Vetter wrote:
> On Tue, Aug 21, 2012 at 1:14 PM, Sedat Dilek wrote:
>> On Tue, Aug 21, 2012 at 1:03 PM, Sedat Dilek wrote:
>>> On Tue, Aug 21, 2012 at 1:02 PM, Sedat Dilek wrote:
>>>> On Tue, Aug 21, 2012 at 8:04 AM,
On Tue, Aug 21, 2012 at 6:39 PM, Daniel Vetter wrote:
> On Tue, Aug 21, 2012 at 3:24 PM, Sedat Dilek wrote:
>> On Tue, Aug 21, 2012 at 1:53 PM, Daniel Vetter wrote:
>>> On Tue, Aug 21, 2012 at 1:14 PM, Sedat Dilek wrote:
>>>> On Tue, Aug 21, 2012 at 1:03 PM, Se
On Tue, Aug 21, 2012 at 8:33 PM, Daniel Vetter wrote:
> On Tue, Aug 21, 2012 at 08:20:35PM +0200, Sedat Dilek wrote:
>> On Tue, Aug 21, 2012 at 6:39 PM, Daniel Vetter wrote:
>> > On Tue, Aug 21, 2012 at 3:24 PM, Sedat Dilek wrote:
>> >> On Tue, Aug 21, 2012 at
Hi,
I see the same build-error as Randy in latest linux.git
(055c9fa8874fa7261eec7a268366565db84af474).
Where is this patch queued up (see original posting)?
I do not see any patch in [2].
And please please please rename your repo... "linux-2.6" died many
months ago :-).
I also do not see any pa
On Wed, Jul 11, 2012 at 6:39 PM, Linus Walleij wrote:
> On Wed, Jul 11, 2012 at 2:29 PM, Sedat Dilek wrote:
>
>> I see the same build-error as Randy in latest linux.git
>> (055c9fa8874fa7261eec7a268366565db84af474).
>
> Yes, it is there.
>
>> Where is this patc
On Thu, Jul 12, 2012 at 12:39 PM, Linus Walleij
wrote:
> On Wed, Jul 11, 2012 at 9:01 PM, Sedat Dilek wrote:
>
>> BTW, didn't see your tree in linux-next [1].
>>
>> [1]
>> http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=blob;f=Next/Trees#l184
Hi,
looks like [1] is fixing my suspend/resume problem with v3.5-rc6+
(attached call-trace is with a v3.5-rc6 kernel before the commit got
upstream).
Thanks for the fix!
I am wondering if those new-lines are intended (see attachment)?
- Sedat -
P.S.: Commit details
commit dc332fdf9f373a87b1e2f
: Sedat Dilek
Kind Regards,
- Sedat (dileks on IRC) -
[1] http://marc.info/?l=linux-kernel&m=134216822724119&w=2
--
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.ke
On Fri, Jul 13, 2012 at 11:47 AM, Sedat Dilek wrote:
> Hi,
>
> while dealing with [1], I saw this mei-related infos in dmesg when
> doing a suspend + resume (see [1] for more logs):
>
> [17046.348467] [] mei_pci_suspend+0x78/0xd0 [mei]
> [17047.460315] mei :00:16.0:
On Fri, Jul 13, 2012 at 12:15 PM, Winkler, Tomas
wrote:
>
>
>> -Original Message-----
>> From: Sedat Dilek [mailto:sedat.di...@gmail.com]
>> Sent: Friday, July 13, 2012 12:48 PM
>> To: Winkler, Tomas
>> Cc: Thomas Gleixner; LKML; Greg Kroah-Hartman; Rola
On Fri, Jul 13, 2012 at 12:29 PM, Sedat Dilek wrote:
> On Fri, Jul 13, 2012 at 12:15 PM, Winkler, Tomas
> wrote:
>>
>>
>>> -Original Message-
>>> From: Sedat Dilek [mailto:sedat.di...@gmail.com]
>>> Sent: Friday, July 13, 2012 12:48 PM
>>
On Sat, Jan 19, 2013 at 3:01 PM, Rafael J. Wysocki wrote:
> On Saturday, January 19, 2013 02:50:17 PM Sedat Dilek wrote:
>> On Sat, Jan 19, 2013 at 2:45 PM, Rafael J. Wysocki wrote:
>> > On Friday, January 18, 2013 05:42:20 PM Randy Dunlap wrote:
>> >> On 01/17/13
On Sat, Jan 19, 2013 at 3:22 PM, Sedat Dilek wrote:
> On Sat, Jan 19, 2013 at 3:01 PM, Rafael J. Wysocki wrote:
>> On Saturday, January 19, 2013 02:50:17 PM Sedat Dilek wrote:
>>> On Sat, Jan 19, 2013 at 2:45 PM, Rafael J. Wysocki wrote:
>>> > On Friday, Janu
On Sat, Jan 19, 2013 at 4:12 PM, Sedat Dilek wrote:
> On Sat, Jan 19, 2013 at 3:16 PM, Ilya Zykov wrote:
>> The root of problem is carelessly zeroing pointer(in function
>> __tty_buffer_flush()),
>> when another thread can use it. It can be cause of "NULL pointer
On Sat, Jan 19, 2013 at 7:28 PM, Sedat Dilek wrote:
> Hi,
>
> I am still stepping in the dark how track this problem down.
> If you have useful (debug) help, you are welcome.
>
> Regards,
> - Sedat -
>
> # ANALYZING CALL-TRACES SEEN IN LINUX-NEXT-20130118 #
On Sat, Jan 19, 2013 at 9:48 PM, Sedat Dilek wrote:
> On Sat, Jan 19, 2013 at 7:28 PM, Sedat Dilek wrote:
>> Hi,
>>
>> I am still stepping in the dark how track this problem down.
>> If you have useful (debug) help, you are welcome.
>>
>> Regards,
>>
On Sat, Jan 19, 2013 at 11:43 PM, Ilya Zykov wrote:
> Hello!
> I don't expert, but
> maybe it can help.
>
> I test with:
> while echo mem > /sys/power/state; do sleep 2; done
> in one X-terminal, in other I trying playing with keyboard.
> (Without playing all right I use ext3.)
Can you test wit
On Sat, Jan 19, 2013 at 11:51 PM, Eric Sandeen wrote:
> On 1/19/13 4:44 PM, Sedat Dilek wrote:
>> Hi Dave,
>>
>> I suspected after initial testing a problem in TTY and applied two patches.
>> After more testing the root cause was a problem in JBD2.
>> A patch fr
On Sat, Jan 19, 2013 at 11:56 PM, Ilya Zykov wrote:
> On 20.01.2013 2:51, Sedat Dilek wrote:
>> On Sat, Jan 19, 2013 at 11:43 PM, Ilya Zykov wrote:
>>> Hello!
>>> I don't expert, but
>>> maybe it can help.
>>>
>>> I test with:
>>&
On Sat, Jan 19, 2013 at 11:59 PM, Sedat Dilek wrote:
> On Sat, Jan 19, 2013 at 11:56 PM, Ilya Zykov wrote:
>> On 20.01.2013 2:51, Sedat Dilek wrote:
>>> On Sat, Jan 19, 2013 at 11:43 PM, Ilya Zykov wrote:
>>>> Hello!
>>>> I don't expert, bu
Hi,
I and some others hit a similiar problem in Linux-Next
(next-20130118), please see [1] and [2].
[3] has a interim analyze of my problems.
After suspecting the problem was caused by TTY-NEXT, it turned out to
be a JBD2 problem finally.
The freezer/pm_test was helpful to hit the issue (Thanks
On Sun, Jan 20, 2013 at 12:44 AM, Sedat Dilek wrote:
> Hi,
>
> I and some others hit a similiar problem in Linux-Next
> (next-20130118), please see [1] and [2].
>
> [3] has a interim analyze of my problems.
>
> After suspecting the problem was caused by TTY-NEXT, it t
On Sat, Jan 19, 2013 at 11:44 PM, Sedat Dilek wrote:
> Hi Dave,
>
> I suspected after initial testing a problem in TTY and applied two patches.
> After more testing the root cause was a problem in JBD2.
> A patch from Eric helped!
> Follow the thread in [1] for more details.
On Sun, Jan 20, 2013 at 1:06 AM, Sedat Dilek wrote:
> On Sun, Jan 20, 2013 at 12:44 AM, Sedat Dilek wrote:
>> Hi,
>>
>> I and some others hit a similiar problem in Linux-Next
>> (next-20130118), please see [1] and [2].
>>
>> [3] has a interim analyze of
On Sun, Jan 20, 2013 at 1:35 AM, Sedat Dilek wrote:
> On Sun, Jan 20, 2013 at 1:06 AM, Sedat Dilek wrote:
>> On Sun, Jan 20, 2013 at 12:44 AM, Sedat Dilek wrote:
>>> Hi,
>>>
>>> I and some others hit a similiar problem in Linux-Next
>>> (next-2013011
On Sun, Jan 20, 2013 at 6:56 AM, Hugh Dickins wrote:
> After sending the first 2MB, scp over wireless becomes unbearably slow,
> with frequent stalls: on this ThinkPad T420s running 3.8-rc4 or 3.7.3.
> Not always, but often.
>
There is one pending iwlwifi-fixes, dunno if it will fix your issue.
On Sun, Jan 20, 2013 at 10:24 PM, Daniel Vetter wrote:
> On Sun, Jan 20, 2013 at 10:15 PM, Sedat Dilek wrote:
>> Hi Daniel,
>>
>> I am testing your patchset (original postings at [1]).
>> At a 1st look it seems to be OK.
>> Any tests you want me to run?
>
>
On Mon, Jan 21, 2013 at 12:40 PM, Sedat Dilek wrote:
> On Mon, Jan 21, 2013 at 11:47 AM, Jan Kara wrote:
>> On Sun 20-01-13 01:06:40, Sedat Dilek wrote:
>>> On Sun, Jan 20, 2013 at 12:44 AM, Sedat Dilek wrote:
>>> > Hi,
>>> >
>>> >
On Mon, Jan 21, 2013 at 3:07 PM, Jan Kara wrote:
> On Mon 21-01-13 13:30:26, Sedat Dilek wrote:
>> On Mon, Jan 21, 2013 at 12:40 PM, Sedat Dilek wrote:
>> > On Mon, Jan 21, 2013 at 11:47 AM, Jan Kara wrote:
>> >> The traces don't suggest an ext4/jbd2
On Mon, Jan 21, 2013 at 3:07 PM, Jan Kara wrote:
> On Mon 21-01-13 13:30:26, Sedat Dilek wrote:
>> On Mon, Jan 21, 2013 at 12:40 PM, Sedat Dilek wrote:
>> > On Mon, Jan 21, 2013 at 11:47 AM, Jan Kara wrote:
>> >> The traces don't suggest an ext4/jbd2
evel/msg61587.html
[2] https://github.com/kleikamp/linux-shaggy/commits/loop_2013_01_04
Cc: Dave Kleikamp
Cc: Jeff Moyer
Cc: Alexander Viro
Cc: linux-fsde...@vger.kernel.org
Signed-off-by: Sedat Dilek
---
fs/aio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/aio.c b/fs/aio
On Wed, Jan 23, 2013 at 12:19 PM, Sedat Dilek wrote:
> Hi Frederic,
>
> I wanted to 3.8-rc4-nohz3 [1] here on my Ubuntu/precise AMD64 system.
>
> Unfortunately, the build breaks like this:
>
> ERROR: "guest_enter" [arch/x86/kvm/kvm.ko] undefined!
> ERROR:
On Wed, Jan 23, 2013 at 1:11 PM, Frederic Weisbecker wrote:
> 2013/1/23 Sedat Dilek :
>> On Wed, Jan 23, 2013 at 12:19 PM, Sedat Dilek wrote:
>>> Hi Frederic,
>>>
>>> I wanted to 3.8-rc4-nohz3 [1] here on my Ubuntu/precise AMD64 system.
>>>
On Wed, Jan 23, 2013 at 1:14 PM, Sedat Dilek wrote:
> On Wed, Jan 23, 2013 at 1:11 PM, Frederic Weisbecker
> wrote:
>> 2013/1/23 Sedat Dilek :
>>> On Wed, Jan 23, 2013 at 12:19 PM, Sedat Dilek wrote:
>>>> Hi Frederic,
>>>>
>>>> I wa
With CONFIG_KVM=m my build with 3.8-rc4-nohz3 breaks like this:
ERROR: "guest_enter" [arch/x86/kvm/kvm.ko] undefined!
ERROR: "guest_exit" [arch/x86/kvm/kvm.ko] undefined!
Fix this by adding the missing EXPORT_SYMBOL_GPL for guest_enter()
and guest_exit() in kernel/context_tracking.c as suggested
With CONFIG_KVM=m my build with 3.8-rc4-nohz3 breaks like this:
ERROR: "guest_enter" [arch/x86/kvm/kvm.ko] undefined!
ERROR: "guest_exit" [arch/x86/kvm/kvm.ko] undefined!
Fix this by adding the missing EXPORT_SYMBOL_GPL for guest_enter() and
guest_exit() in kernel/context_tracking.c as suggested
cking.c as suggested by Frederic.
This issue was introduced with commit 8eebafe9be58 ("kvm: Prepare to
add generic guest entry/exit callbacks").
[ v2: Add reference to culprit commit. -dileks ]
[ v3: Forgot my S-o-b. -dileks ]
Signed-off-by: Sedat Dilek
---
kernel/context_tracki
On Wed, Jan 23, 2013 at 1:20 PM, Frederic Weisbecker wrote:
> 2013/1/23 Sedat Dilek :
>> On Wed, Jan 23, 2013 at 1:11 PM, Frederic Weisbecker
>> wrote:
>>> 2013/1/23 Sedat Dilek :
>>>> On Wed, Jan 23, 2013 at 12:19 PM, Sedat Dilek
>>>> wrote:
&g
ng.c as suggested by Frederic.
This issue was introduced with commit 8eebafe9be58 ("kvm: Prepare to
add generic guest entry/exit callbacks").
Signed-off-by: Sedat Dilek
---
kernel/context_tracking.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/kern
On Wed, Jan 23, 2013 at 2:17 PM, devendra.aaru wrote:
> On Wed, Jan 23, 2013 at 8:15 AM, Sedat Dilek wrote:
>> With CONFIG_KVM=m my build with 3.8-rc4-nohz3 breaks like this:
>>
>> ERROR: "guest_enter" [arch/x86/kvm/kvm.ko] undefined!
>> ERROR: "g
On Wed, Jan 23, 2013 at 3:02 PM, Frederic Weisbecker wrote:
> 2013/1/23 Steven Rostedt :
>> On Wed, 2013-01-23 at 14:46 +0100, Frederic Weisbecker wrote:
>>
>>> > Hmmm, yes, but why, clueless, CONFIG_KVM=y as a workaround!
>>>
>>> I believe he pointed out the "{i" to you. Typing mistake?
>>
>> In
On Wed, Jan 23, 2013 at 3:02 PM, Frederic Weisbecker wrote:
> 2013/1/23 Steven Rostedt :
>> On Wed, 2013-01-23 at 14:46 +0100, Frederic Weisbecker wrote:
>>
>>> > Hmmm, yes, but why, clueless, CONFIG_KVM=y as a workaround!
>>>
>>> I believe he pointed out the "{i" to you. Typing mistake?
>>
>> In
On Wed, Jan 23, 2013 at 4:03 PM, Frederic Weisbecker wrote:
> 2013/1/23 Sedat Dilek :
>> On Wed, Jan 23, 2013 at 3:02 PM, Frederic Weisbecker
>> wrote:
>>> 2013/1/23 Steven Rostedt :
>>>> On Wed, 2013-01-23 at 14:46 +0100, Frederic Weisbecker wrote:
>&
On Wed, Jan 23, 2013 at 4:20 PM, Sedat Dilek wrote:
> On Wed, Jan 23, 2013 at 4:03 PM, Frederic Weisbecker
> wrote:
>> 2013/1/23 Sedat Dilek :
>>> On Wed, Jan 23, 2013 at 3:02 PM, Frederic Weisbecker
>>> wrote:
>>>> 2013/1/23 Steven Rostedt :
>>
unny X86 hackerz!
Tested on a Ubuntu/precise AMD64 with 'CONFIG_KVM=m'.
[ vUNKNOWN: Without the magic "i" hack. -dileks ]
Signed-off-by: Sedat Dilek
---
include/linux/kvm_host.h | 1 +
kernel/context_tracking.c | 7 +++
kernel/sched/cputime.c| 4 ++--
3 files chan
!
Tested on a Ubuntu/precise AMD64 with 'CONFIG_KVM=m'.
[ vUNKNOWN: Without the magic "i" hack. -dileks ]
[ vUNKNOWN+1: Remove vtime.h from kvm_host.h. -dileks ]
Signed-off-by: Sedat Dilek
---
kernel/context_tracking.c | 7 +++
kernel/sched/cputime.c| 4 ++--
2 files c
On Wed, Jan 23, 2013 at 5:14 PM, Frederic Weisbecker wrote:
> 2013/1/23 Sedat Dilek :
>> When CONFIG_KVM=m my build with 3.8-rc4-nohz3 breaks like this:
>>
>> ERROR: "guest_enter" [arch/x86/kvm/kvm.ko] undefined!
>> ERROR: "guest_exit" [arch/x86/kv
!
Tested on a Ubuntu/precise AMD64 with 'CONFIG_KVM=m'.
[ vUNKNOWN: Without the magic "i" hack. -dileks ]
[ vUNKNOWN+1: Remove vtime.h from kvm_host.h. -dileks ]
[ vUNKNOWN+2: Re-add some removed empty lines. -dileks ]
Signed-off-by: Sedat Dilek
---
kernel/context_tracking.c |
On Wed, Feb 13, 2013 at 12:20 PM, James Hogan wrote:
> I get the following build error on next-20130213 due to the following
> commit:
>
> commit f05de73bf82fbbc00265c06d12efb7273f7dc54a ("skbuff: create
> skb_panic() function and its wrappers").
>
> It adds an argument called panic to a function
On Fri, Feb 15, 2013 at 8:42 AM, Stephen Rothwell wrote:
> Hi all,
>
> News: Yesterday was the 5th anniversary of linux-next! I can't believe I
> am still doing this :-)
>
So 5-times a happy Quentin Valentino day!
> Changes since 20130214:
>
> New tree: drm-intel
>
More black roses for integra
On Sat, Jan 12, 2013 at 3:29 AM, Joe Perches wrote:
> On Sat, 2013-01-12 at 13:17 +1100, Stephen Rothwell wrote:
>> On Fri, 11 Jan 2013 17:43:06 -0800 Randy Dunlap
>> wrote:
>> >
>> > b0rked.
>> >
>> > Some (randconfig?) causes this set of errors:
>
> I guess that's when CONFIG_HZ is not an even
On Fri, Jan 11, 2013 at 10:51 PM, Dave Kleikamp
wrote:
> On 01/10/2013 09:46 AM, Sedat Dilek wrote:
>
>> Hi Dave,
>>
>> I am using here Ubuntu/precise AMD64 as a WUBI-installed system.
>>
>> Not sure if WUBI [1] is a good test-candidate.
>>
>> [
On Sat, Jan 12, 2013 at 11:13 AM, Sedat Dilek wrote:
> On Sat, Jan 12, 2013 at 3:29 AM, Joe Perches wrote:
>> On Sat, 2013-01-12 at 13:17 +1100, Stephen Rothwell wrote:
>>> On Fri, 11 Jan 2013 17:43:06 -0800 Randy Dunlap
>>> wrote:
>>> >
>>> >
Hi Andrew,
your patch from [1] - as far as I followed - misses a lot of
Reported-by#s and Tested-by#s (Boris, Jiri, etc.).
Just one new R-b I have seen yesterday.
I have the original patch from Alan plus the two follow-ups from you
in my patch-series against v3.8-{rc2,rc3} for quite a while.
So,
Hi Thomas,
I read your original LKML posting in [1].
[ QUOTE ]
Currently, Daniel Lezcano seems to be working on an intrusive change of not
using the power_usage value at all for choosing a C-state:
[4] https://lkml.org/lkml/2012/12/14/155
As I could not find any of these patches in any git tree
0001: Refreshed 1-2 as v3 against Linux v3.8-rc3.
0002: v2 of 2-2 applied cleanly after 1-2 was refreshed!
Have fun!
- Sedat -
On Sun, Jan 13, 2013 at 8:30 PM, Sedat Dilek wrote:
> Hi Thomas,
>
> I read your original LKML posting in [1].
>
> [ QUOTE ]
> Currently, Daniel L
On Sun, Jan 13, 2013 at 9:44 PM, Daniel Lezcano
wrote:
> On 01/13/2013 09:36 PM, Sedat Dilek wrote:
>> 0001: Refreshed 1-2 as v3 against Linux v3.8-rc3.
>> 0002: v2 of 2-2 applied cleanly after 1-2 was refreshed!
>
> Hi Sedat,
>
> for the moment, you should use only th
On Mon, Jan 14, 2013 at 1:03 AM, Stephen Rothwell wrote:
> Hi Rafael,
>
> After merging the pm tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> In file included from init/main.c:25:0:
> include/linux/acpi.h:549:46: error: unknown type name 'acpi_handle'
> include/li
0
> [ 137.062218] [] ? flush_kthread_worker+0xb0/0xb0
> [ 137.06] [] ret_from_fork+0x7c/0xb0
> [ 137.062228] [] ? flush_kthread_worker+0xb0/0xb0
>
> Reported-by: Sedat Dilek
> Tested-by: Sedat Dilek
> Signed-off-by: Tomas Winkler
Can you please apply this patch to char-misc
On Mon, Jan 14, 2013 at 3:32 PM, Greg KH wrote:
> On Mon, Jan 14, 2013 at 03:14:50PM +0100, Sedat Dilek wrote:
>> On Thu, Jan 10, 2013 at 4:32 PM, Tomas Winkler
>> wrote:
>> > On systems where wd and amthif is not initialized
>> > we will hit cl->dev == NUL
On Mon, Jan 14, 2013 at 4:12 PM, Greg KH wrote:
> On Mon, Jan 14, 2013 at 03:55:44PM +0100, Sedat Dilek wrote:
>> On Mon, Jan 14, 2013 at 3:32 PM, Greg KH wrote:
>> > On Mon, Jan 14, 2013 at 03:14:50PM +0100, Sedat Dilek wrote:
>> >> On Thu, Jan 10, 2013 at 4:32 P
On Mon, Jan 14, 2013 at 7:56 PM, Jens Axboe wrote:
> On 2013-01-14 19:33, Sedat Dilek wrote:
>> Hi,
>>
>> while running LTP lite on my next-20130114 kernel I hit this
>> call-trace (file attached).
>>
>> Looks to me like problem in the block layer, but not
On Mon, Jan 14, 2013 at 8:28 PM, Sedat Dilek wrote:
> On Mon, Jan 14, 2013 at 7:56 PM, Jens Axboe wrote:
>> On 2013-01-14 19:33, Sedat Dilek wrote:
>>> Hi,
>>>
>>> while running LTP lite on my next-20130114 kernel I hit this
>>> call-trace (file attac
On Mon, Jan 14, 2013 at 10:29 PM, Sedat Dilek wrote:
> Hi,
>
> this patch is for Linux-Next - more exactly next-20130114.
> Can you please enhance the subject-line of your patch next time.
>
> Your patch fixes the issue I have reported a few hours ago in [1].
>
> [ TESTCAS
On Tue, Jan 15, 2013 at 12:44 AM, Sedat Dilek wrote:
> On Mon, Jan 14, 2013 at 10:29 PM, Sedat Dilek wrote:
>> Hi,
>>
>> this patch is for Linux-Next - more exactly next-20130114.
>> Can you please enhance the subject-line of your patch next time.
>>
>> You
On Tue, Jan 15, 2013 at 7:44 AM, Jens Axboe wrote:
> On Mon, Jan 14 2013, Sedat Dilek wrote:
>> On Mon, Jan 14, 2013 at 8:28 PM, Sedat Dilek wrote:
>> > On Mon, Jan 14, 2013 at 7:56 PM, Jens Axboe wrote:
>> >> On 2013-01-14 19:33, Sedat Dilek wrote:
>> >
On Tue, Jan 15, 2013 at 2:34 PM, Venu Byravarasu wrote:
>> -Original Message-
>> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
>> ow...@vger.kernel.org] On Behalf Of Sedat Dilek
>> Sent: Tuesday, January 15, 2013 6:51 PM
>> To: Stephen Ro
On Wed, Sep 26, 2012 at 9:51 PM, Hugh Dickins wrote:
> On Wed, 26 Sep 2012, Sedat Dilek wrote:
>>
>> on my Ubuntu/precise AMD64 today's Linux-Next runs into the following
>> call-trace (machine freezes):
>>
>> Sep 26 19:22:58 fambox kernel: [ 11.124739
On Fri, Sep 28, 2012 at 1:22 PM, Sedat Dilek wrote:
> On Fri, Sep 28, 2012 at 8:51 AM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> Changes since 201209027:
>>
>> The vfs tree lost its conflicts.
>>
>> The infiniband tree gained a conflict again
On Fri, Sep 28, 2012 at 1:51 PM, Sedat Dilek wrote:
> On Fri, Sep 28, 2012 at 1:22 PM, Sedat Dilek wrote:
>> On Fri, Sep 28, 2012 at 8:51 AM, Stephen Rothwell
>> wrote:
>>> Hi all,
>>>
>>> Changes since 201209027:
>>>
>>> The vfs t
On Fri, Sep 28, 2012 at 7:30 PM, Jan Ceuleers wrote:
> On 09/28/2012 07:23 PM, Mark Langsdorf wrote:
>> From: Mark Langsdorf
>
> Mark,
>
> This From: line is malformed: the bit between the angle brackets should
> contain an email address.
>
Randy sent a patch to linux-next ML and pinged again on
On Tue, Jan 15, 2013 at 4:11 AM, Stephen Rothwell wrote:
> Hi all,
>
> On Mon, 14 Jan 2013 22:09:18 +0100 Sedat Dilek wrote:
>>
>> Looks like this is the fix from Sasha [1].
>> Culprit commit is [2].
>> Testing...
>>
>> - Sedat -
>>
>>
On Tue, Jan 15, 2013 at 3:25 PM, Takashi Iwai wrote:
> At Sat, 5 Jan 2013 13:13:27 +0100,
> Sedat Dilek wrote:
>>
>> Hi Jiri,
>>
>> ...known issue (see thread in [1]), please feel free to test patches
>> from Alan and Andrew (see [1], [2] and [3]) and report.
On Wed, Jan 16, 2013 at 10:35 AM, Takashi Iwai wrote:
> At Wed, 16 Jan 2013 10:21:46 +0100,
> Sedat Dilek wrote:
>>
>> On Tue, Jan 15, 2013 at 3:25 PM, Takashi Iwai wrote:
>> > At Sat, 5 Jan 2013 13:13:27 +0100,
>> > Sedat Dilek wrote:
>> >>
>&
On Sat, Jan 5, 2013 at 3:20 AM, Huang, Shane wrote:
>> OK, I see the patch I mentioned to fix the problem was later reverted [1].
>> The real fix is "libata: replace sata_settings with devslp_timing" [2].
>
> Yes, please use [2] which can also be found in kernel bugzilla #51881
> and is pending on
On Wed, Jan 16, 2013 at 12:07 PM, Sedat Dilek wrote:
> On Wed, Jan 16, 2013 at 10:59 AM, Sedat Dilek wrote:
>> On Wed, Jan 16, 2013 at 10:52 AM, Sedat Dilek wrote:
>>> On Wed, Jan 16, 2013 at 10:35 AM, Takashi Iwai wrote:
>>>> At Wed, 16 Jan 2013 10:21:46
On Wed, Jan 16, 2013 at 5:32 PM, James Bottomley
wrote:
> On Wed, 2013-01-09 at 13:58 -0600, Dave Kleikamp wrote:
>> This patchset was begun by Zach Brown and was originally submitted for
>> review in October, 2009. Feedback was positive, and I have picked up
>> where he left off, porting his patc
On Thu, Jan 17, 2013 at 7:17 PM, Greg Kroah-Hartman
wrote:
> On Tue, Jan 08, 2013 at 09:48:16AM +0100, Sedat Dilek wrote:
>> This was introduced by:
>>
>> commit 438763f37eb9664b6372bdfee990f8c33acdc63c
>> "mei: drop redundant length parameter from mei_write_messa
Signed-off-by: Sedat Dilek
---
drivers/misc/mei/hw-me.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/misc/mei/hw-me.c b/drivers/misc/mei/hw-me.c
index 93a2a56..94b203e 100644
--- a/drivers/misc/mei/hw-me.c
+++ b/drivers/misc/mei/hw-me.c
@@ -236,7 +236,7
On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130117:
>
> Undropped tree: samung
>
> The powerpc tree still had a build failure.
>
> The driver-core tree gained a build failure for which I applied a merge
> fix patch.
>
> The gpio-lw tree gained a build fai
On Fri, Jan 18, 2013 at 10:43 PM, Sedat Dilek wrote:
> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> Changes since 20130117:
>>
>> Undropped tree: samung
>>
>> The powerpc tree still had a build failure.
>>
>
On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki wrote:
> On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
>> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell
>> wrote:
>> > Hi all,
>> >
>> > Changes since 20130117:
>> >
>>
On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek wrote:
> On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki wrote:
>> On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
>>> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell
>>> wrote:
>>> > Hi
On Fri, Jan 18, 2013 at 11:54 PM, David Howells wrote:
> Sedat Dilek wrote:
>
>> Culprit seems to be...
>>
>> commit d6941c0c6bd42c725e45240a86c4add92e9bfb3e
>> "KEYS: Separate the kernel signature checking keyring from module signing"
>
> Try upda
On Sat, Jan 19, 2013 at 12:04 AM, Sedat Dilek wrote:
> On Fri, Jan 18, 2013 at 11:54 PM, David Howells wrote:
>> Sedat Dilek wrote:
>>
>>> Culprit seems to be...
>>>
>>> commit d6941c0c6bd42c725e45240a86c4add92e9bfb3e
>>> "KEYS: Separate t
On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki wrote:
> On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
>> On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek wrote:
>> > On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki wrote:
>> >> On Friday, Janu
On Sat, Jan 19, 2013 at 12:39 AM, Rafael J. Wysocki wrote:
> On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
>> On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki wrote:
>> > On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
>> >> On Fri, J
On Sat, Jan 19, 2013 at 12:58 AM, Rafael J. Wysocki wrote:
> On Saturday, January 19, 2013 12:41:11 AM Sedat Dilek wrote:
>> On Sat, Jan 19, 2013 at 12:39 AM, Rafael J. Wysocki wrote:
>> > On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
>> >> On Sat, Ja
On Sat, Jan 19, 2013 at 1:00 AM, Sedat Dilek wrote:
> On Sat, Jan 19, 2013 at 12:58 AM, Rafael J. Wysocki wrote:
>> On Saturday, January 19, 2013 12:41:11 AM Sedat Dilek wrote:
>>> On Sat, Jan 19, 2013 at 12:39 AM, Rafael J. Wysocki wrote:
>>> > On Saturday, Janu
clared identifier is reported
only once for each function it appears in
Fix this by replacing "select" with "depends on" KEYS Kconfig.
For more details follow the thread in [1].
[1] http://marc.info/?t=13585454501&r=1&w=2
Tested against Linux-Next (next-20130118).
S
There exists no SYSTEM_TRUSTED_KEYS Kconfig option but
SYSTEM_TRUSTED_KEYRING.
Tested against Linux-Next (next-20130118).
Signed-off-by: Sedat Dilek
---
init/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/init/Kconfig b/init/Kconfig
index f7e1b32..7191ccf 100644
On Sat, Jan 19, 2013 at 12:58 AM, Rafael J. Wysocki wrote:
> On Saturday, January 19, 2013 12:41:11 AM Sedat Dilek wrote:
>> On Sat, Jan 19, 2013 at 12:39 AM, Rafael J. Wysocki wrote:
>> > On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
>> >> On Sat, Ja
401 - 500 of 1444 matches
Mail list logo
