On Tue, Mar 19, 2013 at 6:54 AM, Stephen Rothwell wrote:
> Hi,
>
> On Tue, 19 Mar 2013 16:47:48 +1100 Stephen Rothwell
> wrote:
>>
>> On Tue, 19 Mar 2013 06:42:27 +0100 Sedat Dilek wrote:
>> >
>> > did forget to sent your email [1] to linux-nex
On Tue, Mar 19, 2013 at 6:47 AM, Stephen Rothwell wrote:
> Hi,
>
> On Tue, 19 Mar 2013 06:42:27 +0100 Sedat Dilek wrote:
>>
>> did forget to sent your email [1] to linux-next ML?
>
> No, and I even checked my mail server's logs and it was accepted by vger.
&g
On Tue, Feb 5, 2013 at 6:34 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130204:
>
> The powerpc tree still had a build failure.
>
> The nfsd tree lost its build.
>
> The sound-asoc tree gained a build failure so I used the version from
> next-20130204.
>
Several people ask for inclu
On Fri, Feb 1, 2013 at 9:42 AM, Daniel Vetter wrote:
> On Fri, Feb 1, 2013 at 9:21 AM, Sedat Dilek wrote:
>> people having the fbcon-locking-fixes [1] in their local GIT tree can
>> revert this change?
>
> Yeah, if you have all the fixes reverting this is fine and appr
On Tue, Feb 5, 2013 at 11:47 AM, Sedat Dilek wrote:
> On Fri, Feb 1, 2013 at 9:42 AM, Daniel Vetter wrote:
>> On Fri, Feb 1, 2013 at 9:21 AM, Sedat Dilek wrote:
>>> people having the fbcon-locking-fixes [1] in their local GIT tree can
>>> revert this change?
>
On Thu, Feb 7, 2013 at 7:37 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130206:
>
> Removed tree: kvmtool (still present via the tip tree)
>
> The block tree lost its build failure.
>
> The tip tree gained a conflict against the s390 tree.
>
> The kvm tree gained a conflict against L
On Thu, Feb 7, 2013 at 10:38 AM, Sedat Dilek wrote:
> On Thu, Feb 7, 2013 at 7:37 AM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> Changes since 20130206:
>>
>> Removed tree: kvmtool (still present via the tip tree)
>>
>> The block tree lost its bui
On Thu, Feb 7, 2013 at 11:20 AM, Sedat Dilek wrote:
> On Thu, Feb 7, 2013 at 10:38 AM, Sedat Dilek wrote:
>> On Thu, Feb 7, 2013 at 7:37 AM, Stephen Rothwell
>> wrote:
>>> Hi all,
>>>
>>> Changes since 20130206:
>>>
>>> Removed tree
On Thu, Feb 7, 2013 at 12:14 PM, Eric W. Biederman
wrote:
> Sedat Dilek writes:
>
>> On Thu, Feb 7, 2013 at 11:20 AM, Sedat Dilek wrote:
>>> On Thu, Feb 7, 2013 at 10:38 AM, Sedat Dilek wrote:
>>>> On Thu, Feb 7, 2013 at 7:37 AM, Stephen Rothwell
>>>
On Thu, Feb 7, 2013 at 2:39 PM, Sedat Dilek wrote:
> On Thu, Feb 7, 2013 at 12:52 PM, Sedat Dilek wrote:
>> On Thu, Feb 7, 2013 at 12:14 PM, Eric W. Biederman
>> wrote:
>>> Sedat Dilek writes:
>>>
>>>> On Thu, Feb 7, 2013 at 11:20 AM, Sedat Dilek
preloading
> itself anymore, there's no point in the error handling path.
> Simply remove the -ENOMEM path.
>
> Signed-off-by: Tejun Heo
> Reported-by: Sedat Dilek
> Cc: Stanislav Kinsbursky
> Cc: "Eric W. Biederman"
> Cc: James Morris
> ---
On Wed, Feb 6, 2013 at 9:49 AM, Sedat Dilek wrote:
> On Wed, Feb 6, 2013 at 9:23 AM, Sedat Dilek wrote:
>> On Wed, Feb 6, 2013 at 8:43 AM, Stephen Rothwell
>> wrote:
>>> Hi all,
>>>
>>> Changes since 20130204:
>>>
>>> The metag tr
On Fri, Feb 8, 2013 at 5:31 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130207:
>
> The sound-asoc tree gained a build failure so I used the version from
> next-20130207.
>
> The watchdog tree gained a conflict against the mfd tree.
>
> I applied a patch to restore some config defaul
On Fri, Feb 8, 2013 at 5:31 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130207:
>
> The sound-asoc tree gained a build failure so I used the version from
> next-20130207.
>
> The watchdog tree gained a conflict against the mfd tree.
>
> I applied a patch to restore some config defaul
On Fri, Feb 8, 2013 at 12:53 PM, Hillf Danton wrote:
> Hello Sedat
>
> On Fri, Feb 8, 2013 at 4:46 PM, Sedat Dilek wrote:
>> On Fri, Feb 8, 2013 at 5:31 AM, Stephen Rothwell
>> wrote:
>> With today's Linux-Next I see this warning:
>>
&g
On Fri, Feb 8, 2013 at 2:21 PM, Rafael J. Wysocki wrote:
> On Friday, February 08, 2013 01:47:44 PM Sedat Dilek wrote:
>> On Fri, Feb 8, 2013 at 12:53 PM, Hillf Danton wrote:
>> > Hello Sedat
>> >
>> > On Fri, Feb 8, 2013 at 4:46 PM, Sedat Dilek wrote:
On Fri, Feb 8, 2013 at 3:45 PM, Viresh Kumar wrote:
> On 8 February 2013 18:51, Rafael J. Wysocki wrote:
>> On Friday, February 08, 2013 01:47:44 PM Sedat Dilek wrote:
>>> >> [0.377473] [] warn_slowpath_common+0x7f/0xc0
>>> >> [0.377479
On Fri, Feb 8, 2013 at 3:50 PM, Viresh Kumar wrote:
> On Fri, Feb 8, 2013 at 7:45 PM, Sedat Dilek wrote:
>> "...some...changes..." is not very concrete :-).
>> Which commit(s) caused this trouble?
>>
>> Is current (meanwhile updated?) linux-pm.git#linux-next
On Fri, Feb 8, 2013 at 3:56 PM, Viresh Kumar wrote:
> On Fri, Feb 8, 2013 at 8:18 PM, Sedat Dilek wrote:
>> Nah, I pulled in latest pm-next where this commit is new...
>>
>> commit 8d5666f3456f2fd4a4e5dced228475b829851e53
>> "ACPI: Unbind ACPI drv when probe f
On Fri, Feb 8, 2013 at 4:21 PM, Sedat Dilek wrote:
> On Fri, Feb 8, 2013 at 3:56 PM, Viresh Kumar wrote:
>> On Fri, Feb 8, 2013 at 8:18 PM, Sedat Dilek wrote:
>>> Nah, I pulled in latest pm-next where this commit is new...
>>>
>>> commit 8d5666f3456f2f
On Fri, Feb 8, 2013 at 5:28 PM, Sedat Dilek wrote:
> On Fri, Feb 8, 2013 at 4:21 PM, Sedat Dilek wrote:
>> On Fri, Feb 8, 2013 at 3:56 PM, Viresh Kumar wrote:
>>> On Fri, Feb 8, 2013 at 8:18 PM, Sedat Dilek wrote:
>>>> Nah, I pulled in latest pm
On Mon, Feb 11, 2013 at 8:19 PM, Yinghai Lu wrote:
> On Mon, Feb 11, 2013 at 5:02 AM, Peter Hurley
> wrote:
>> On Sun, 2013-02-10 at 22:40 -0800, Yinghai Lu wrote:
>>> On Sun, Feb 10, 2013 at 12:33 PM, Yinghai Lu wrote:
>>> > On Sun, Feb 10, 2013 at 6:23 AM, Peter Hurley
>>> > wrote:
>>> >> O
On Tue, Feb 12, 2013 at 6:09 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130211:
>
> The acpi tree lost its build failure.
>
> The net-next tree gained a conflict against the net tree.
>
> The arm-soc tree gained conflicts against the usb and metag trees.
>
>
On Mon, Jan 28, 2013 at 8:28 PM, Tejun Heo wrote:
> Hello, guys.
>
> On Sun, Jan 27, 2013 at 02:01:50PM +0100, Sedat Dilek wrote:
>> OK, that bisecting ruined a bit my weekend and showed me again you
>> cannot really bisect Linux-Next.
>> Sometimes, it is better not to
On Mon, Jan 28, 2013 at 11:08 PM, Tejun Heo wrote:
> Hello, Sedat.
>
> On Mon, Jan 28, 2013 at 11:06:11PM +0100, Sedat Dilek wrote:
>> 1. People should sent their patches concerning especially Linux-Next
>> fixes not only to LKML but also to (if
>> this is not known,
On Mon, Jan 28, 2013 at 10:51 PM, Sedat Dilek wrote:
> On Mon, Jan 28, 2013 at 8:04 PM, Frederic Weisbecker
> wrote:
>> While remotely reading the cputime of a task running in a
>> full dynticks CPU, the values stored in utime/stime fields
>> of struct task_struct may
On Thu, Jan 31, 2013 at 1:38 AM, Frederic Weisbecker wrote:
> 2013/1/28 Sedat Dilek :
>> On Mon, Jan 28, 2013 at 8:04 PM, Frederic Weisbecker
>> wrote:
>>> While remotely reading the cputime of a task running in a
>>> full dynticks CPU, the values stored in
On Thu, Jan 31, 2013 at 11:12 AM, Frederic Weisbecker
wrote:
> 2013/1/31 Sedat Dilek :
>> On Thu, Jan 31, 2013 at 1:38 AM, Frederic Weisbecker
>> wrote:
>>> 2013/1/28 Sedat Dilek :
>>>> On Mon, Jan 28, 2013 at 8:04 PM, Frederic Weisbecker
>>>>
On Fri, Feb 1, 2013 at 9:42 AM, Daniel Vetter wrote:
> On Fri, Feb 1, 2013 at 9:21 AM, Sedat Dilek wrote:
>> people having the fbcon-locking-fixes [1] in their local GIT tree can
>> revert this change?
>
> Yeah, if you have all the fixes reverting this is fine and appr
On Sat, Jan 26, 2013 at 12:10 PM, Sedat Dilek wrote:
> On Fri, Jan 25, 2013 at 6:26 AM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> Changes since 20130124:
>>
>> New trees: ipsec and ipsec-next
>>
>> The powerpc tree still had a build failur
On Sat, Jan 26, 2013 at 2:25 PM, Rafael J. Wysocki wrote:
> On Saturday, January 26, 2013 12:10:32 PM Sedat Dilek wrote:
>> On Fri, Jan 25, 2013 at 6:26 AM, Stephen Rothwell
>> wrote:
>> > Hi all,
>> >
>> > Changes since 20130124:
>> >
>>
On Sat, Jan 26, 2013 at 2:24 PM, Sedat Dilek wrote:
> On Sat, Jan 26, 2013 at 2:25 PM, Rafael J. Wysocki wrote:
>> On Saturday, January 26, 2013 12:10:32 PM Sedat Dilek wrote:
>>> On Fri, Jan 25, 2013 at 6:26 AM, Stephen Rothwell
>>> wrote:
>>> > Hi
On Sat, Jan 26, 2013 at 3:33 PM, Sedat Dilek wrote:
> On Sat, Jan 26, 2013 at 2:24 PM, Sedat Dilek wrote:
>> On Sat, Jan 26, 2013 at 2:25 PM, Rafael J. Wysocki wrote:
>>> On Saturday, January 26, 2013 12:10:32 PM Sedat Dilek wrote:
>>>> On Fri, Jan 25, 201
On Sat, Jan 26, 2013 at 4:05 PM, Sedat Dilek wrote:
> On Sat, Jan 26, 2013 at 3:33 PM, Sedat Dilek wrote:
>> On Sat, Jan 26, 2013 at 2:24 PM, Sedat Dilek wrote:
>>> On Sat, Jan 26, 2013 at 2:25 PM, Rafael J. Wysocki wrote:
>>>> On Saturday, January 26, 2013
On Sat, Jan 26, 2013 at 10:49 PM, Rafael J. Wysocki wrote:
> On Saturday, January 26, 2013 07:27:06 PM Sedat Dilek wrote:
>> On Sat, Jan 26, 2013 at 4:05 PM, Sedat Dilek wrote:
>> > On Sat, Jan 26, 2013 at 3:33 PM, Sedat Dilek wrote:
>> >> On Sat, Jan 26
Hi,
this is just an information for people might trapping into the same issue.
You can get the patch from patchwork-service [1] or directly from
wq.git# for-3.9-async GIT tree [2].
Next Monday's Linux-Next (next-20130127) should be fine, again.
Regards,
- Sedat -
[1] https://patchwork.kernel.o
On Sun, Jan 27, 2013 at 7:48 PM, Guenter Roeck wrote:
> On Sun, Jan 27, 2013 at 02:56:46PM +0100, Sedat Dilek wrote:
>> Hi Geert,
>>
>> what is the intention of this list [1] which you regularly sent to LKML?
>>
>> Statistics?
>>
>> [ Compiler errors
en Rostedt
> Cc: Thomas Gleixner
> [fixed kvm module related build errors]
> Signed-off-by: Sedat Dilek
>
Can you explain a bit what is the difference between "3.8-rc4-nohz3"
and "full-dynticks-cputime-for-mingo" patchsets?
Does the latter need no more EXPORT_S
On Mon, Feb 25, 2013 at 3:27 PM, Al Viro wrote:
> On Mon, Feb 25, 2013 at 03:22:03PM +0100, Sedat Dilek wrote:
>> On Mon, Feb 25, 2013 at 2:54 PM, Al Viro wrote:
>> > On Mon, Feb 25, 2013 at 02:22:42PM +0100, Sedat Dilek wrote:
>> >
>> >> [ 120.310366] Ro
February 26th...
- Sedat -
On Tue, Feb 26, 2013 at 4:16 AM, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any work destined for v3.10 to your -next included
> branches until after Linus has release v3.9-rc1.
>
> Changes since 20130223:
>
> The kbuild tree lost its build failure.
>
> Th
On Tue, Feb 26, 2013 at 4:16 AM, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any work destined for v3.10 to your -next included
> branches until after Linus has release v3.9-rc1.
>
> Changes since 20130223:
>
> The kbuild tree lost its build failure.
>
> The infiniband tree gained a co
On Tue, Feb 26, 2013 at 5:48 PM, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running latest -next,
> I've started seeing a bunch of these, which wasn't there in the -next from
> couple of days ago:
>
> [ 1169.020539] [ cut here ]
> [
On Wed, Feb 27, 2013 at 11:46 AM, Dan Williams wrote:
> On Tue, 2013-02-26 at 12:58 -0800, Bing Zhao wrote:
>> For SD8688, FUNC_INIT command is queued before fw_ready flag is
>> set. This causes the following crash as lbs_thread blocks any
>> command if fw_ready is not set.
>
> While we're at this
On Wed, Feb 27, 2013 at 12:52 PM, richard -rw- weinberger
wrote:
> On Tue, Feb 26, 2013 at 8:54 AM, richard -rw- weinberger
> wrote:
>> On Tue, Feb 26, 2013 at 7:31 AM, Srinivas Eeda
>> wrote:
>>> This is due to a race in lock mastery/purge. I have recently fixed this
>>> problem but haven't ye
On Wed, Feb 27, 2013 at 12:58 PM, Wim Van Sebroeck wrote:
> Hi Sedat,
>
>> while digging into a Linux-Next issue [0] I wanted to browse the
>> watchdog GitWeb, but it seems not to be available for me!
>
> Correct. I disabled it because the server has not enough memory...
>
Then please update your
On Tue, Feb 26, 2013 at 10:39 AM, Sedat Dilek wrote:
> On Mon, Feb 25, 2013 at 2:44 PM, Sedat Dilek wrote:
>> On Mon, Feb 25, 2013 at 6:00 AM, Stephen Rothwell
>> wrote:
>>> Hi all,
>>>
>>> Please do not add any work destined for v3.10 to your -next i
Hi Marek,
as I see the today's git-pull-request for linux-kbuild... I and some
other people (see 2/3 and 3/3) sent minor fixes to deb-pkg.
Where they overseen?
Anything wrong with them?
( Sorry, didn't follow linux-kbuild ML for a while. )
Regards,
- Sedat -
[PATCH 1/3] kbuild, deb-pkg: Try to d
On Tue, Feb 26, 2013 at 6:01 PM, Sedat Dilek wrote:
> On Tue, Feb 26, 2013 at 5:48 PM, Sasha Levin wrote:
>> Hi all,
>>
>> While fuzzing with trinity inside a KVM tools guest running latest -next,
>> I've started seeing a bunch of these, which wasn't there in
t be I come back when Debian/wheezy is released... you never know :-).
Or I get an Amiga-3000 with Debian/m68k running... with DirOpus and
DPaint-IV, hahaha.
I was simply too lazy to place a rock-solid changelog.
- Sedat -
> Michal
>
> On 24.4.2012 00:16, Sedat Dilek wrote:
>> Sign
On Wed, Feb 27, 2013 at 5:08 PM, Borislav Petkov wrote:
> On Wed, Feb 27, 2013 at 04:56:27PM +0100, Sedat Dilek wrote:
>> Hmm, I am not very amused to read all this, really.
>>
>> If such fixes are around why aren't they applied quickly?
>
> Sedat, you need to
[ QUOTE ]
On Wed, Feb 27, 2013 at 3:15 AM, Heiko Carstens
wrote:
>
> Tested with 64 bit kernel with 64 bit and 31 bit mode user space as well as
> with 31 bit kernel and 31 bit user space. Each with legacy and flexible
> mmap layout.
> The bug is fixed and everything else still seems to work. Than
On Wed, Feb 27, 2013 at 6:20 PM, Linus Torvalds
wrote:
> On Wed, Feb 27, 2013 at 9:15 AM, Sedat Dilek wrote:
>>
>> Where is it?
>
> Oh sorry, I hadn't pushed it out, I was looking through other emails
> in the meantime.
>
> Pushed out now (but mirror delays t
Hi,
I am seeing this also on Linux-Next.
/var/log/kern.log:Feb 27 22:52:35 fambox kernel: [ 28.202381]
[drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal timeout
(has irq: 1)!
/var/log/kern.log:Feb 27 22:52:35 fambox kernel: [ 28.210588]
[drm:intel_dp_aux_wait_done] *ERROR* dp aux
On Wed, Feb 27, 2013 at 11:36 PM, Sedat Dilek wrote:
> Hi,
>
> I am seeing this also on Linux-Next.
>
> /var/log/kern.log:Feb 27 22:52:35 fambox kernel: [ 28.202381]
> [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal timeout
> (has irq: 1)!
> /var/log/
On Wed, Feb 27, 2013 at 4:07 PM, Tejun Heo wrote:
> Replying here too just in case.
>
> On Wed, Feb 27, 2013 at 02:08:40PM +0100, Sedat Dilek wrote:
>> >> static inline void *idr_find(struct idr *idr, int id)
>> >> {
>> >> struct id
On Thu, Feb 28, 2013 at 8:24 AM, Sedat Dilek wrote:
> On Wed, Feb 27, 2013 at 4:07 PM, Tejun Heo wrote:
>> Replying here too just in case.
>>
>> On Wed, Feb 27, 2013 at 02:08:40PM +0100, Sedat Dilek wrote:
>>> >> static inline vo
eue to send).
>
>> On 24.4.2012 00:16, Sedat Dilek wrote:
>> > Signed-off-by: Sedat Dilek
>> > ---
>> > scripts/package/builddeb | 15 ++-
>> > 1 file changed, 14 insertions(+), 1 deletion(-)
>> >
>> > diff --git a/script
On Thu, Feb 28, 2013 at 12:18 PM, Chris Wilson wrote:
> On Thu, Feb 28, 2013 at 12:06:28AM +0100, Sedat Dilek wrote:
>> On Wed, Feb 27, 2013 at 11:36 PM, Sedat Dilek wrote:
>> > Hi,
>> >
>> > I am seeing this also on Linux-Next.
>> >
>>
On Thu, Feb 28, 2013 at 3:31 PM, Paulo Zanoni wrote:
> Hi
>
> 2013/2/28 Chris Wilson :
>> On Thu, Feb 28, 2013 at 12:06:28AM +0100, Sedat Dilek wrote:
>>> On Wed, Feb 27, 2013 at 11:36 PM, Sedat Dilek wrote:
>>> > Hi,
>>> >
>>> &g
On Thu, Feb 28, 2013 at 6:12 PM, Sedat Dilek wrote:
> On Thu, Feb 28, 2013 at 3:31 PM, Paulo Zanoni wrote:
>> Hi
>>
>> 2013/2/28 Chris Wilson :
>>> On Thu, Feb 28, 2013 at 12:06:28AM +0100, Sedat Dilek wrote:
>>>> On Wed, Feb 27, 2013 at 11:
On Thu, Feb 28, 2013 at 6:33 PM, Paulo Zanoni wrote:
> Hi
>
> 2013/2/28 Sedat Dilek :
>> On Thu, Feb 28, 2013 at 6:12 PM, Sedat Dilek wrote:
>>> On Thu, Feb 28, 2013 at 3:31 PM, Paulo Zanoni wrote:
>>>> Hi
>>>>
>>>> 2013/2/28 Chris Wi
On Wed, Jan 30, 2013 at 8:26 PM, Dave Kleikamp wrote:
> By the way, I have updated the patchset in git. I removed the version
> from the name of the branch and will keep this one updated:
>
> git://github.com/kleikamp/linux-shaggy.git aio_loop
What's the status of this patchset?
Will it go into L
On Tue, Mar 12, 2013 at 4:41 PM, Miklos Szeredi wrote:
> Al and Linus,
>
> Please consider overlayfs for inclusion into 3.10.
>
> It's included in Ubuntu and openSUSE, used by OpenWrt and various other
> projects. I regularly get emails asking when it will be included in mainline.
>
> Git tree is
On Tue, Mar 12, 2013 at 11:23 PM, Al Viro wrote:
> On Tue, Mar 12, 2013 at 02:50:02PM -0700, Linus Torvalds wrote:
>> On Tue, Mar 12, 2013 at 8:41 AM, Miklos Szeredi wrote:
>> > Al and Linus,
>> >
>> > Please consider overlayfs for inclusion into 3.10.
>>
>> Yes, I think we should just do it. It'
On Tue, Mar 12, 2013 at 6:18 PM, Mark Knecht wrote:
> On Tue, Mar 12, 2013 at 9:55 AM, Sedat Dilek wrote:
>> Hi,
>>
>> what's the status of union-mount?
>> Where does the development happen - in [1]?
>>
>> Regards,
>> - Sedat -
>>
>>
On Tue, Mar 12, 2013 at 6:19 PM, David Howells wrote:
> Sedat Dilek wrote:
>
>> what's the status of union-mount?
>
> It's being reengineered again to take account of VFS changes that went in in
> the last merge window.
>
Hmmm, sorry for asking, but when do y
On Tue, Mar 12, 2013 at 4:41 PM, Miklos Szeredi wrote:
> Al and Linus,
>
> Please consider overlayfs for inclusion into 3.10.
>
> It's included in Ubuntu and openSUSE, used by OpenWrt and various other
> projects. I regularly get emails asking when it will be included in mainline.
>
> Git tree is
On Tue, Mar 12, 2013 at 10:50 AM, Sedat Dilek wrote:
> On Tue, Mar 12, 2013 at 6:46 AM, Kees Cook wrote:
>> On Mon, Mar 11, 2013 at 9:22 PM, Stephen Rothwell
>> wrote:
>>> Hi all,
>>>
>>> After merging the final tree, today's linux-n
On Wed, Mar 13, 2013 at 3:31 PM, Sedat Dilek wrote:
> On Wed, Mar 13, 2013 at 3:16 PM, Miklos Szeredi wrote:
>> Here's another version with the comments addressed plus a small bugfix and
>> some
>> checkpatch cleanups.
>>
>> Changes in v17:
>>
>&
On Wed, Mar 13, 2013 at 4:18 PM, Miklos Szeredi wrote:
>> Looks like this is missing (or intended?):
>>
>> diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
>> index 482c26f..f23ebfc 100644
>> --- a/fs/overlayfs/super.c
>> +++ b/fs/overlayfs/super.c
>> @@ -684,3 +684,6 @@ static void __exit
On Wed, Mar 13, 2013 at 4:26 PM, Sedat Dilek wrote:
> On Wed, Mar 13, 2013 at 4:18 PM, Miklos Szeredi wrote:
>>> Looks like this is missing (or intended?):
>>>
>>> diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
>>> index 482c26f..f23ebfc 100644
&
On Wed, Mar 13, 2013 at 4:53 PM, Sedat Dilek wrote:
> On Wed, Mar 13, 2013 at 4:26 PM, Sedat Dilek wrote:
>> On Wed, Mar 13, 2013 at 4:18 PM, Miklos Szeredi wrote:
>>>> Looks like this is missing (or intended?):
>>>>
>>>> diff --git a/fs/overla
On Wed, Mar 13, 2013 at 5:21 PM, Miklos Szeredi wrote:
> On Wed, Mar 13, 2013 at 5:10 PM, Sedat Dilek wrote:
>
>> Anyway, with CONFIG_OVERLAYFS_FS=m I do not see any related messages
>> when the kernel-module is loaded.
>> So, is this intended?
>> SquashFS print
On Wed, Mar 13, 2013 at 5:21 PM, Miklos Szeredi wrote:
> On Wed, Mar 13, 2013 at 5:10 PM, Sedat Dilek wrote:
>
>> Anyway, with CONFIG_OVERLAYFS_FS=m I do not see any related messages
>> when the kernel-module is loaded.
>> So, is this intended?
>> SquashFS print
Signed-off-by: Sedat Dilek
---
fs/overlayfs/super.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
index 482c26f..92b9ad5 100644
--- a/fs/overlayfs/super.c
+++ b/fs/overlayfs/super.c
@@ -675,11 +675,13 @@ MODULE_ALIAS_FS("overlayfs"
Signed-off-by: Sedat Dilek
---
fs/squashfs/super.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/squashfs/super.c b/fs/squashfs/super.c
index 260e392..9747764 100644
--- a/fs/squashfs/super.c
+++ b/fs/squashfs/super.c
@@ -447,8 +447,7 @@ static int __init
On Wed, Mar 13, 2013 at 7:37 PM, Felix Fietkau wrote:
> On 2013-03-13 7:12 PM, Robin Holt wrote:
>> On Wed, Mar 13, 2013 at 05:51:33PM +0100, Sedat Dilek wrote:
>>> On Wed, Mar 13, 2013 at 5:21 PM, Miklos Szeredi wrote:
>>> > On Wed, Mar 13, 2013 at 5:10
Signed-off-by: Sedat Dilek
---
fs/overlayfs/super.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
index 482c26f..e30141f 100644
--- a/fs/overlayfs/super.c
+++ b/fs/overlayfs/super.c
@@ -674,6 +674,8 @@ MODULE_ALIAS_FS("overlayfs");
On Wed, Mar 13, 2013 at 8:58 PM, Linus Torvalds
wrote:
> On Wed, Mar 13, 2013 at 12:54 PM, Eric W. Biederman
> wrote:
>>>
>>> Hehe, I just checked my new kernel... that does not work (nothing in the
>>> logs).
>>> But I think it's good to see if the filesystem is registered/loaded.
>>
>> lsmod |
On Wed, Mar 13, 2013 at 9:13 PM, Phillip Lougher
wrote:
>
>
> On Wed, Mar 13, 2013 at 4:10 PM, Sedat Dilek wrote:
>>
>> On Wed, Mar 13, 2013 at 4:53 PM, Sedat Dilek
>> wrote:
>> > On Wed, Mar 13, 2013 at 4:26 PM, Sedat Dilek
>> > wrote:
>>
On Wed, Mar 13, 2013 at 9:05 PM, Al Viro wrote:
> On Wed, Mar 13, 2013 at 08:47:14PM +0100, Sedat Dilek wrote:
>>
>> Signed-off-by: Sedat Dilek
>> ---
>> fs/overlayfs/super.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/fs/over
On Fri, Mar 15, 2013 at 5:41 AM, Rusty Russell wrote:
> Stephen Rothwell writes:
>> Hi Al,
>>
>> Today's linux-next merge of the signal tree got a conflict in
>> include/asm-generic/unistd.h between commit 837718bfd28b
>> ("CONFIG_SYMBOL_PREFIX: cleanup") from the modules tree and commit
>> e1b5b
On Fri, Mar 15, 2013 at 11:21 AM, Sedat Dilek wrote:
> On Fri, Mar 15, 2013 at 5:41 AM, Rusty Russell wrote:
>> Stephen Rothwell writes:
>>> Hi Al,
>>>
>>> Today's linux-next merge of the signal tree got a conflict in
>>> includ
On Tue, Sep 4, 2012 at 5:58 AM, Stephen Rothwell wrote:
> Hi Dave,
>
> After merging the drm tree, today's linux-next build (powerpc
> ppc64_defconfig) produced these warnings:
>
> drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
> drivers/gpu/drm/udl/Kconfig:1: symbol DRM_UDL
On Tue, Sep 4, 2012 at 10:22 AM, Dave Airlie wrote:
>> > After merging the drm tree, today's linux-next build (powerpc
>> > ppc64_defconfig) produced these warnings:
>> >
>> > drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
>> > drivers/gpu/drm/udl/Kconfig:1: symbol DRM_UDL de
On Tue, Sep 11, 2012 at 8:31 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 201209010:
>
> New tree: ixp4xx
>
> The pci tree gained a build failure so I used the version from
> next-20120910.
>
> The regulator tree lost its build failure.
>
> The staging tree lost its build failure.
>
> T
On Tue, Sep 11, 2012 at 8:12 PM, Sedat Dilek wrote:
> On Tue, Sep 11, 2012 at 8:31 AM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> Changes since 201209010:
>>
>> New tree: ixp4xx
>>
>> The pci tree gained a build failure so I used the version from
On Tue, Sep 11, 2012 at 8:29 PM, Sedat Dilek wrote:
> On Tue, Sep 11, 2012 at 8:12 PM, Sedat Dilek wrote:
>> On Tue, Sep 11, 2012 at 8:31 AM, Stephen Rothwell
>> wrote:
>>> Hi all,
>>>
>>> Changes since 201209010:
>>>
>>> New tree:
On Wed, Sep 12, 2012 at 9:52 PM, Bjorn Helgaas wrote:
> On Tue, Sep 11, 2012 at 4:04 PM, Sedat Dilek wrote:
>> On Tue, Sep 11, 2012 at 8:29 PM, Sedat Dilek wrote:
>>> On Tue, Sep 11, 2012 at 8:12 PM, Sedat Dilek wrote:
>>>> On Tue, Sep 11, 2012 at 8:31 AM,
On Thu, Sep 13, 2012 at 5:18 AM, Sedat Dilek wrote:
> On Wed, Sep 12, 2012 at 10:46 AM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> Changes since 201209011:
>>
>> The pci tree lost its build failure.
>>
>> The mfd tree gained a conflict agains
On Thu, Sep 13, 2012 at 8:04 AM, Minchan Kim wrote:
> On Thu, Sep 13, 2012 at 07:29:32AM +0200, Sedat Dilek wrote:
>> On Thu, Sep 13, 2012 at 5:18 AM, Sedat Dilek wrote:
>> > On Wed, Sep 12, 2012 at 10:46 AM, Stephen Rothwell
>> > wrote:
>> >> Hi a
Thanks for Sedat,
> and sorry for not catching this earlier. :-(
>
Hi Hendrik,
Wow, so fast :-).
Stephen, can you apply this to today's linux-next (next-20120913), please?
Regards,
- Sedat -
> Henrik
>
> --
>
> From ccc6557bfd02efdca4d9dfda6cfdfe5a08d0193b Mon Sep 17
0x4e138b): undefined reference to
>> `cpufreq_frequency_get_table'
>>
>> Signed-off-by: Randy Dunlap
>> Cc: Amit Daniel
Feel free to add:
Tested-by: Sedat Dilek
>> ---
>> drivers/thermal/Kconfig |1 +
>> 1 file changed, 1 insertion(+)
&
On Thu, Sep 13, 2012 at 10:18 AM, Sedat Dilek wrote:
> On Thu, Sep 13, 2012 at 9:04 AM, Henrik Rydberg wrote:
>>> > >> > this weeks linux-next seems to bring new and new issues, yay :-)!
>>> > >> >
>>> > >> > I have taken a
On Thu, Sep 13, 2012 at 10:22 AM, Stephen Rothwell
wrote:
> Hi all,
>
> Changes since 201209012:
>
> The staging tree gained a conflict against the tty tree.
>
> The arm-soc tree gained a conflict against the i2c-embedded tree.
>
> The tegra tree lost 2 conflicts.
>
> The akpm tree gained 3 build
On Fri, Sep 14, 2012 at 9:38 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 201209013:
>
> The pci tree lost its conflicts.
>
> The i2c tree lost its conflict.
>
> The net-next tree gained conflicts against the net tree.
>
> The cgroup tree gained a build failure so I used the version fro
On Fri, Sep 14, 2012 at 4:33 PM, Daniel Wagner wrote:
> From: Daniel Wagner
>
> commit 1f66c0a8833c3974ab6b35edcf4f8585b2f94592
> Author: Daniel Wagner
> Date: Wed Sep 12 16:12:01 2012 +0200
>
> cgroup: net_cls: Move sock_update_classid() declaration to cls_cgroup.h
>
> Claimed that there
On Fri, Sep 14, 2012 at 7:00 PM, Tejun Heo wrote:
> Hello,
>
> On Fri, Sep 14, 2012 at 08:56:29AM +0200, Daniel Wagner wrote:
>> On 14.09.2012 05:17, Stephen Rothwell wrote:
>> >After merging the cgroup tree, today's linux-next build (powerpc
>> >ppc64_defconfig) failed like this:
>> >
>> >drivers
Hi,
I am reading LKML offline (mostly on ).
Did you send out an announcement for Linux v3.11-rc7 or am I missing sth.?
Regards,
- Sedat -
--
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:
On Wed, Aug 28, 2013 at 11:49 AM, Sedat Dilek wrote:
> Hi all,
>
> Changes since 20130827:
>
> The f2fs tree lost its build failure.
>
> The md tree gained a conflict against the arm tree.
>
> The libata tree lost its build failure.
>
> The spi tree lost its bu
1 - 100 of 1444 matches
Mail list logo
