On Sat, Apr 20, 2013 at 2:19 AM, Sedat Dilek wrote:
> On Sat, Apr 20, 2013 at 2:06 AM, Sedat Dilek wrote:
>> On Sat, Apr 20, 2013 at 1:02 AM, Linus Torvalds
>> wrote:
>>> On Fri, Apr 19, 2013 at 3:55 PM, Sedat Dilek wrote:
>>>>
>>>> Dav
On Sat, Apr 20, 2013 at 5:59 PM, Rik van Riel wrote:
> On 04/20/2013 08:46 AM, Sedat Dilek wrote:
>
>> I have started a new thread "[next-20130419] ipc: sem: BROKEN", please
>> use this one!
>>
>> Thanks for all your feedback!
>>
>>
On Sat, Apr 20, 2013 at 10:00 PM, Davidlohr Bueso
wrote:
> On Sat, 2013-04-20 at 02:19 +0200, Sedat Dilek wrote:
>> On Sat, Apr 20, 2013 at 2:06 AM, Sedat Dilek wrote:
>> > On Sat, Apr 20, 2013 at 1:02 AM, Linus Torvalds
>> > wrote:
>> >> On Fr
On Mon, Apr 22, 2013 at 7:47 AM, liguang wrote:
> originally, 'data->flags = CSD_FLAG_LOCK',
> and we use 'data->flags &= ~CSD_FLAG_LOCK'
> for csd_unlock, they are not symmetrix operations
> so use '|=' instead of '='.
> though, now data->flags only hold CSD_FLAG_LOCK,
> it's not so meaningful to
On Mon, Apr 22, 2013 at 8:22 AM, li guang wrote:
> 在 2013-04-22一的 08:18 +0200，Sedat Dilek写道：
>> On Mon, Apr 22, 2013 at 7:47 AM, liguang wrote:
>> > originally, 'data->flags = CSD_FLAG_LOCK',
>> > and we use 'data->flags &= ~CSD_FLAG_LOCK
On Mon, Apr 22, 2013 at 8:30 AM, Sedat Dilek wrote:
> On Mon, Apr 22, 2013 at 8:22 AM, li guang wrote:
>> 在 2013-04-22一的 08:18 +0200，Sedat Dilek写道：
>>> On Mon, Apr 22, 2013 at 7:47 AM, liguang wrote:
>>> > originally, 'data->flags = CSD_FLA
Commit c8dc68ad0fbd ("kconfig/lxdialog: support resize") added support
for resizing, but forgot to collect all hardcoded values at one single
place.
Signed-off-by: Sedat Dilek
---
scripts/kconfig/lxdialog/checklist.c | 4 ++--
scripts/kconfig/lxdialog/dialog.h| 13
INDOW_{HEIGTH,WIDTH}_MIN
* Mention the check for a minimum screen/window size in the changelog
* Add a comment above the block of new definitions ]
Signed-off-by: Sedat Dilek
---
scripts/kconfig/lxdialog/checklist.c | 4 ++--
scripts/kconfig/lxdialog/dialog.h| 14 ++
sc
> MENUBOX_{HEIGTH,WIDTH}_MIN
ChangeLog v2:
* Rename WIN_{HEIGTH,WIDTH}_MIN -> WINDOW_{HEIGTH,WIDTH}_MIN
* Mention the check for a minimum screen/window size in the changelog
* Add a comment above the block of new definitions ]
Signed-off-by: Sedat Dilek
---
scripts/kconfig/lxdialog/
On Fri, Jun 21, 2013 at 10:17 AM, Stephen Rothwell
wrote:
> Hi all,
>
> Happy solstice!
>
> Changes since 20130620:
>
> Dropped tree: mailbox (really bad merge conflicts with the arm-soc tree)
>
> The net-next tree gained a conflict against the net tree.
>
> The leds tree still had its build fail
On Sat, Jun 22, 2013 at 12:07 AM, Davidlohr Bueso
wrote:
> On Fri, 2013-06-21 at 21:34 +0200, Sedat Dilek wrote:
>> On Fri, Jun 21, 2013 at 10:17 AM, Stephen Rothwell
>> wrote:
>> > Hi all,
>> >
>> > Happy solstice!
>> >
>> > Changes
On Sat, Jun 22, 2013 at 1:11 AM, Davidlohr Bueso wrote:
> On Sat, 2013-06-22 at 00:54 +0200, Sedat Dilek wrote:
>> On Sat, Jun 22, 2013 at 12:07 AM, Davidlohr Bueso
>> wrote:
>> > On Fri, 2013-06-21 at 21:34 +0200, Sedat Dilek wrote:
>> >> On Fri, Jun 21
On Sat, Jun 22, 2013 at 12:54 AM, Sedat Dilek wrote:
> On Sat, Jun 22, 2013 at 12:07 AM, Davidlohr Bueso
> wrote:
>> On Fri, 2013-06-21 at 21:34 +0200, Sedat Dilek wrote:
>>> On Fri, Jun 21, 2013 at 10:17 AM, Stephen Rothwell
>>> wrote:
>>&g
d-by: Matthieu CASTET
> Signed-off-by: Matthieu CASTET
> [yann.morin.1...@free.fr: independently re-done the same patch as Matthieu,
> as pointed out by Sedat]
> Cc: Arnaud Lacombe
> Cc: Sedat Dilek
> Signed-off-by: "Yann E. MORIN"
[
On Tue, Jun 25, 2013 at 10:01 AM, Yann E. MORIN wrote:
> Michal, All,
>
> On Monday 24 June 2013 20:11:59 Yann E. MORIN wrote:
>> Currently, randconfig does randomise choice entries, unless KCONFIG_ALLCONFIG
>> is specified.
> [--SNIP--]
>> This patch defers setting that a choice has a value until
On Tue, Jun 25, 2013 at 10:44 AM, Stephen Rothwell
wrote:
> Hi all,
>
> Changes since 20130624:
>
> The vfs tree lost its build failure.
>
> The net-next tree gained a conflict against the net tree.
>
> The usb tree gained a conflict against the devicetree tree.
>
> The staging tree lost its buil
On Tue, Jun 25, 2013 at 10:55 AM, Sedat Dilek wrote:
> On Tue, Jun 25, 2013 at 10:44 AM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> Changes since 20130624:
>>
>> The vfs tree lost its build failure.
>>
>> The net-next tree gained a conflict a
On Tue, Jun 25, 2013 at 11:21 AM, Yann E. MORIN wrote:
> Sedat, All,
>
> On Tuesday 25 June 2013 10:55:20 Sedat Dilek wrote:
>> Not sure what's going on, but I get this with today's Linux-Next.
>> ( Yesterday's next-20130624 was OK. )
>>
>> $ LA
On Tue, Jun 25, 2013 at 11:17 AM, Sedat Dilek wrote:
> On Tue, Jun 25, 2013 at 10:55 AM, Sedat Dilek wrote:
>> On Tue, Jun 25, 2013 at 10:44 AM, Stephen Rothwell
>> wrote:
>>> Hi all,
>>>
>>> Changes since 20130624:
>>>
>>> The vfs t
On Tue, Jun 25, 2013 at 11:30 AM, Michal Marek wrote:
> On 25.6.2013 11:26, Sedat Dilek wrote:
>> On Tue, Jun 25, 2013 at 11:21 AM, Yann E. MORIN
>> wrote:
>> http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=a11650e11093ed57dca78bf16e7836517c
Hi Linus,
AFAICS the funny release-names ($NAME) have not changed for a long
while (did not check the logs).
Is that now useless...
L#5: NAME = Unicycling Gorilla
... or you lost all creativity in your brain :-)?
If I look at the xserver folks, they do change it for even rc#s...
(too much creat
On Tue, Jun 25, 2013 at 10:57 PM, Yann E. MORIN wrote:
> Sedat, All,
>
> On 2013-06-25 11:28 +0200, Sedat Dilek spake thusly:
>> On Tue, Jun 25, 2013 at 11:17 AM, Sedat Dilek wrote:
>> > On Tue, Jun 25, 2013 at 10:55 AM, Sedat Dilek
>> > wrote:
> [--SNIP--]
On Tue, Jun 25, 2013 at 11:03 PM, Yann E. MORIN wrote:
> Sedat, All,
>
> On 2013-06-25 11:26 +0200, Sedat Dilek spake thusly:
>> On Tue, Jun 25, 2013 at 11:21 AM, Yann E. MORIN
>> wrote:
>> > On Tuesday 25 June 2013 10:55:20 Sedat Dilek wrote:
>> >> Not
On Wed, Jun 26, 2013 at 11:48 AM, Sedat Dilek wrote:
> On Wed, Jun 26, 2013 at 10:06 AM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> Changes since 20130625:
>>
>> New tree: cpuinit
>>
>> The arm-mpidr tree gained a conflict against the arm tree.
&
On Mon, Jul 1, 2013 at 11:03 AM, Sedat Dilek wrote:
> On Mon, Jul 1, 2013 at 10:52 AM, Daniel Vetter wrote:
>> On Mon, Jul 1, 2013 at 10:49 AM, Sedat Dilek wrote:
>>> On Mon, Jul 1, 2013 at 9:59 AM, Stephen Rothwell
>>> wrote:
>>>> Hi all,
>>
I should
> never try to touch wait.h.
>
> On 06/29, Sedat Dilek wrote:
>>
>> As this all did not show me what caused the problem I started a
>> git-bisect session.
>>
>> This revealed the following culprit commit:
>>
>> commit bb1f30cb7d3b
On Tue, Jul 2, 2013 at 9:07 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130701:
>
> The powerpc tree gained a build failure so I used the version from
> next-20130701.
>
> The regulator tree lost its build failure.
>
> The arm-soc tree gained conflicts against the l2-mtd tree.
>
> Th
On Wed, Jul 3, 2013 at 12:37 AM, Oleg Nesterov wrote:
> Hi Sedat,
>
> On 07/02, Sedat Dilek wrote:
>>
>> did you made a cleaned-up version?
>> AFAICS v3, I read that on linux-mm ML, sorry if I ask here in this thread.
>
> Yes, I am going to send v3 with this fi
On Wed, Jul 3, 2013 at 12:34 AM, wrote:
> The mm-of-the-moment snapshot 2013-07-02-15-32 has been uploaded to
>
>http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue.
On Wed, Jul 3, 2013 at 9:48 AM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allnoconfig) failed like this:
[...]
> Caused by commit 1bc2774d8664 ("net: convert lls to use time_in_range()")
> from the net-next tree.
>
> I cherry-picked the
On Wed, Jul 3, 2013 at 11:29 AM, Sedat Dilek wrote:
> On Wed, Jul 3, 2013 at 10:06 AM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> Changes since 20130702:
>>
>> The powerpc tree lost its build failure.
>>
>> The device-mapper tree gained a confl
On Wed, Jul 3, 2013 at 12:58 PM, Sedat Dilek wrote:
> On Wed, Jul 3, 2013 at 11:29 AM, Sedat Dilek wrote:
>> On Wed, Jul 3, 2013 at 10:06 AM, Stephen Rothwell
>> wrote:
>>> Hi all,
>>>
>>> Changes since 20130702:
>>>
>>> The powerpc
mem_cgroup_sockets_{init,destroy} here...
[ net/core/sock.c ]
...
int mem_cgroup_sockets_init()
...
void mem_cgroup_sockets_destroy()
...
...I did the the same for both in "include/net/sock.h".
This fixes the issue for me in next-20130703.
Signed-off-by: Sedat Dilek
---
include/net/sock
cgroup_sockets_{init,destroy} here...
[ net/core/sock.c ]
#ifdef CONFIG_MEMCG_KMEM
int mem_cgroup_sockets_init()
...
void mem_cgroup_sockets_destroy()
...
#endif
...I did the the same for both in "include/net/sock.h".
This fixes the issue for me in next-20130703.
Signed-off-
cgroup_sockets_{init,destroy} here...
[ net/core/sock.c ]
#ifdef CONFIG_MEMCG_KMEM
int mem_cgroup_sockets_init()
...
void mem_cgroup_sockets_destroy()
...
#endif
...I did the the same for both in "include/net/sock.h".
This fixes the issue for me in next-20130703.
Signed-off-by:
On Wed, Jul 3, 2013 at 2:51 PM, Li Zefan wrote:
> On 2013/7/3 20:19, Sedat Dilek wrote:
>> When "CONFIG_MEMCG_KMEM=n" I see this in my build-log:
>>
>> LD init/built-in.o
>> mm/built-in.o: In function `mem_cgroup_css_free':
>> memc
On Wed, Jul 3, 2013 at 3:09 PM, Sedat Dilek wrote:
> On Wed, Jul 3, 2013 at 2:51 PM, Li Zefan wrote:
>> On 2013/7/3 20:19, Sedat Dilek wrote:
>>> When "CONFIG_MEMCG_KMEM=n" I see this in my build-log:
>>>
>>> LD init/built-in.o
>&
On Wed, Jul 3, 2013 at 2:51 PM, Li Zefan wrote:
> On 2013/7/3 20:19, Sedat Dilek wrote:
>> When "CONFIG_MEMCG_KMEM=n" I see this in my build-log:
>>
>> LD init/built-in.o
>> mm/built-in.o: In function `mem_cgroup_css_free':
>> memc
On Wed, Jul 3, 2013 at 5:20 PM, Michal Hocko wrote:
> On Wed 03-07-13 20:51:00, Li Zefan wrote:
> [...]
>> [PATCH] memcg: fix build error if CONFIG_MEMCG_KMEM=n
>>
>> Fix this build error:
>>
>> mm/built-in.o: In function `mem_cgroup_css_free':
>> memcontrol.c:(.text+0x5caa6): undefined reference
On Wed, Jul 3, 2013 at 5:59 PM, Michal Hocko wrote:
> On Wed 03-07-13 17:53:21, Sedat Dilek wrote:
>> On Wed, Jul 3, 2013 at 5:20 PM, Michal Hocko wrote:
>> > On Wed 03-07-13 20:51:00, Li Zefan wrote:
>> > [...]
>> >> [PATCH] memcg: fix build error if C
On Wed, Jul 3, 2013 at 6:34 PM, Michal Hocko wrote:
> On Wed 03-07-13 18:11:28, Sedat Dilek wrote:
>> On Wed, Jul 3, 2013 at 5:59 PM, Michal Hocko wrote:
>> > On Wed 03-07-13 17:53:21, Sedat Dilek wrote:
>> >> On Wed, Jul 3, 2013 at 5:20 PM, Michal Hocko wrote:
&g
On Wed, Jul 3, 2013 at 7:19 PM, Randy Dunlap wrote:
> On 07/02/13 15:34, a...@linux-foundation.org wrote:
>> The mm-of-the-moment snapshot 2013-07-02-15-32 has been uploaded to
>>
>>http://www.ozlabs.org/~akpm/mmotm/
>>
>> mmotm-readme.txt says
>>
>> README for mm-of-the-moment:
>>
>> http://w
On Thu, Jul 4, 2013 at 8:06 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130703:
>
> The net-next tree lost its build failure.
>
> The akpm tree gained a conflict against the kbuild tree and lost lots of
> patches that turned up elsewhere.
>
> -
On Thu, Jul 4, 2013 at 9:41 AM, Sedat Dilek wrote:
> On Thu, Jul 4, 2013 at 8:06 AM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> Changes since 20130703:
>>
>> The net-next tree lost its build failure.
>>
>> The akpm tree gained a conflict against
On Thu, Jul 4, 2013 at 10:21 AM, Sedat Dilek wrote:
> On Thu, Jul 4, 2013 at 9:41 AM, Sedat Dilek wrote:
>> On Thu, Jul 4, 2013 at 8:06 AM, Stephen Rothwell
>> wrote:
>>> Hi all,
>>>
>>> Changes since 20130703:
>>>
>>> The net-next
On Thu, Jul 4, 2013 at 10:45 AM, Andrew Morton
wrote:
> On Thu, 4 Jul 2013 10:21:09 +0200 Sedat Dilek wrote:
>
>> I have compared both mm/memcontrol.c files from
>> next-20130703/next-20130704 - they are identical.
>>
>> These hunks...
>>
>> [ From Li Ze
On Wed, Jun 26, 2013 at 5:24 PM, Thomas Petazzoni
wrote:
> Dear Sedat Dilek,
>
> On Wed, 26 Jun 2013 16:50:55 +0200, Sedat Dilek wrote:
>
>> [ TO/CC char-misc folks ]
>>
>> The CULPRIT commit [1] due to my git-bisecting is:
>>
>> commit 585d98e00ba7a
On Wed, Jun 26, 2013 at 5:32 PM, Greg Kroah-Hartman
wrote:
> On Wed, Jun 26, 2013 at 05:24:46PM +0200, Thomas Petazzoni wrote:
>> Dear Sedat Dilek,
>>
>> On Wed, 26 Jun 2013 16:50:55 +0200, Sedat Dilek wrote:
>>
>> > [ TO/CC char-misc folks ]
>> &
On Wed, Jun 26, 2013 at 6:16 PM, Jörg Otte wrote:
> 2013/5/25 Jörg Otte :
>> If iwlwifi/iwldvm are built into the kernel (no loadable modules)
>> following error is written to console and syslog since v3.10-rc:
>>
>> iwlwifi :08:00.0: failed to load module iwldvm (error -38), is
>> dynamic loa
On Wed, Jun 26, 2013 at 7:15 PM, Greg Kroah-Hartman
wrote:
> On Wed, Jun 26, 2013 at 05:36:03PM +0200, Sedat Dilek wrote:
>> On Wed, Jun 26, 2013 at 5:32 PM, Greg Kroah-Hartman
>> wrote:
>> > On Wed, Jun 26, 2013 at 05:24:46PM +0200, Thomas Petazzoni wrote:
>> >&
On Wed, Jun 26, 2013 at 6:37 PM, Sedat Dilek wrote:
> On Wed, Jun 26, 2013 at 6:16 PM, Jörg Otte wrote:
>> 2013/5/25 Jörg Otte :
>>> If iwlwifi/iwldvm are built into the kernel (no loadable modules)
>>> following error is written to console and syslog since v3.10-rc:
&
On Fri, Jun 28, 2013 at 9:33 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130627:
>
> This tree produces the following warning when built for many (all?)
> configs (it has been fixed in the drm tree):
>
> drivers/video/Kconfig:42:error: recursive dependency detected!
> drivers/video/K
On Fri, Jun 28, 2013 at 10:29 AM, Dave Airlie wrote:
>>
>> [ CC wq and drm(-intel) folks ]
>>
>
> Already know the commit which caused it, mentioned on dri-devel,
> waiting for danvet to wake up and look, before I revert it later.
>
Thanks, I like fast responses.
For followers... See "workqueue
On Fri, Jun 28, 2013 at 10:31 AM, Sedat Dilek wrote:
> On Fri, Jun 28, 2013 at 10:29 AM, Dave Airlie wrote:
>>>
>>> [ CC wq and drm(-intel) folks ]
>>>
>>
>> Already know the commit which caused it, mentioned on dri-devel,
>> waiting for danv
On Fri, Jun 28, 2013 at 11:21 AM, Sedat Dilek wrote:
> On Fri, Jun 28, 2013 at 10:31 AM, Sedat Dilek wrote:
>> On Fri, Jun 28, 2013 at 10:29 AM, Dave Airlie wrote:
>>>>
>>>> [ CC wq and drm(-intel) folks ]
>>>>
>>>
>>> Already know
On Sat, Jun 29, 2013 at 11:44 PM, Sedat Dilek wrote:
> On Fri, Jun 28, 2013 at 9:33 AM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> Changes since 20130627:
>>
>> This tree produces the following warning when built for many (all?)
>> configs (it has
I should
> never try to touch wait.h.
>
> On 06/29, Sedat Dilek wrote:
>>
>> As this all did not show me what caused the problem I started a
>> git-bisect session.
>>
>> This revealed the following culprit commit:
>>
>> commit bb1f30cb7d3b
On Sun, Jun 30, 2013 at 10:17 PM, wrote:
> On Sun, 30 Jun 2013 20:19:45 +0200, Oleg Nesterov said:
>>
>> Not only "__wait_no_timeout(tout) ?:" was wrong, I didn't bother
>> to recheck this logic even after I got the "warning: the omitted
>> middle operand in ?:" reports.
>>
>> Sedat, thanks you v
On Mon, Jul 1, 2013 at 10:52 AM, Daniel Vetter wrote:
> On Mon, Jul 1, 2013 at 10:49 AM, Sedat Dilek wrote:
>> On Mon, Jul 1, 2013 at 9:59 AM, Stephen Rothwell
>> wrote:
>>> Hi all,
>>>
>>> Changes since 20130628:
>>>
>>> The regu
On Wed, Jul 31, 2013 at 2:43 AM, Dave Chinner wrote:
> On Tue, Jul 30, 2013 at 02:28:20PM -0700, Andrew Morton wrote:
>> On Thu, 25 Jul 2013 12:50:26 -0500 Dave Kleikamp
>> wrote:
>>
>> > This patch series adds a kernel interface to fs/aio.c so that kernel code
>> > can
>> > issue concurrent as
On Wed, Jul 31, 2013 at 6:15 AM, Dave Chinner wrote:
> Hi folks,
>
> This series of patches is against the curent mmotm tree here:
>
> http://git.cmpxchg.org/cgit/linux-mmotm.git/
>
"Current" is not precise enough... above tree has git-tags.
I guess you mean "v3.11-rc1-mmotm-2013-07-18-16-40" ?
On Thu, Aug 1, 2013 at 8:19 AM, Dave Chinner wrote:
> On Wed, Jul 31, 2013 at 08:48:40AM +0200, Sedat Dilek wrote:
>> On Wed, Jul 31, 2013 at 6:15 AM, Dave Chinner wrote:
>> > Hi folks,
>> >
>> > This series of patches is against the curent mmotm tree here:
&
On Thu, Aug 1, 2013 at 9:25 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130731:
>
> Removed trees: xen-arm (merged into the xen-tip tree)
>
> The ext4 tree still has its build failure so I used the version from
> next-20130726.
>
> The driver-core tree gained a conflict against the n
On Wed, Aug 21, 2013 at 2:14 AM, Stephen Rothwell wrote:
> Hi Dave,
>
> On Tue, 20 Aug 2013 14:13:15 -0500 Dave Kleikamp
> wrote:
>>
>> Would you be willing to pick up
>> git://github.com/kleikamp/linux-shaggy.git for-next
>> into linux-next?
>
> I have added that from today.
>
>> There will be
On Wed, Aug 21, 2013 at 11:21 AM, Stephen Rothwell
wrote:
> Hi all,
>
> There will be no linux-next trees on Aug 23 or 26.
>
> Changes since 20130820:
>
> New tree: aio-direct
>
> Removed tree: xilinx (at maintainer's request)
>
> The xfs tree still had its build failure for which I reverted a co
On Wed, Aug 21, 2013 at 3:44 PM, Daniel Vetter wrote:
> On Wed, Aug 21, 2013 at 12:35:08PM +0200, Sedat Dilek wrote:
>> On Wed, Aug 21, 2013 at 11:21 AM, Stephen Rothwell
>> wrote:
>> > Hi all,
>> >
>> > There will be no linux-next trees on Aug
On Wed, Aug 21, 2013 at 11:20 PM, Daniel Vetter wrote:
> On Wed, Aug 21, 2013 at 08:11:27PM +0200, Sedat Dilek wrote:
>> On Wed, Aug 21, 2013 at 3:44 PM, Daniel Vetter wrote:
>> > On Wed, Aug 21, 2013 at 12:35:08PM +0200, Sedat Dilek wrote:
>> >> On Wed, Aug
On Thu, Aug 22, 2013 at 1:32 PM, Daniel Vetter wrote:
> On Thu, Aug 22, 2013 at 1:30 PM, Daniel Vetter wrote:
>> On Thu, Aug 22, 2013 at 1:13 PM, Sedat Dilek wrote:
>>> dmesg (a lot of traces) and kernel-config attached.
>>>
>>> UXA causes still screen c
On Fri, Aug 23, 2013 at 9:55 AM, Sedat Dilek wrote:
> On Thu, Aug 22, 2013 at 1:32 PM, Daniel Vetter wrote:
>> On Thu, Aug 22, 2013 at 1:30 PM, Daniel Vetter
>> wrote:
>>> On Thu, Aug 22, 2013 at 1:13 PM, Sedat Dilek wrote:
>>>> dmesg (a lot o
On Fri, Aug 23, 2013 at 10:34 AM, Chris Wilson wrote:
> On Fri, Aug 23, 2013 at 10:04:37AM +0200, Sedat Dilek wrote:
>> On Fri, Aug 23, 2013 at 9:55 AM, Sedat Dilek wrote:
>> > On Thu, Aug 22, 2013 at 1:32 PM, Daniel Vetter
>> > wrote:
>> >> On Thu,
On Fri, Aug 23, 2013 at 10:34 AM, Chris Wilson wrote:
> On Fri, Aug 23, 2013 at 10:04:37AM +0200, Sedat Dilek wrote:
>> On Fri, Aug 23, 2013 at 9:55 AM, Sedat Dilek wrote:
>> > On Thu, Aug 22, 2013 at 1:32 PM, Daniel Vetter
>> > wrote:
>> >> On Thu,
On Fri, Aug 23, 2013 at 10:34 AM, Chris Wilson wrote:
> On Fri, Aug 23, 2013 at 10:04:37AM +0200, Sedat Dilek wrote:
>> On Fri, Aug 23, 2013 at 9:55 AM, Sedat Dilek wrote:
>> > On Thu, Aug 22, 2013 at 1:32 PM, Daniel Vetter
>> > wrote:
>> >> On Thu,
On Tue, Aug 6, 2013 at 3:54 PM, Johannes Berg wrote:
> On Tue, 2013-08-06 at 15:51 +0200, Sedat Dilek wrote:
>> OK, I did not try with debugging enabled and/or w/o Network-Manager.
>>
>> If you know of an issue, please let me know.
>
> No, but the dmesg looks lik
On Tue, Aug 6, 2013 at 3:54 PM, Johannes Berg wrote:
> On Tue, 2013-08-06 at 15:51 +0200, Sedat Dilek wrote:
>> OK, I did not try with debugging enabled and/or w/o Network-Manager.
>>
>> If you know of an issue, please let me know.
>
> No, but the dmesg looks lik
On Tue, Aug 6, 2013 at 4:50 PM, Johannes Berg wrote:
> On Tue, 2013-08-06 at 16:46 +0200, Sedat Dilek wrote:
>
> Heh, the interesting messages are always cut out of the log:
>
> Aug 6 16:30:34 fambox wpa_supplicant[2533]: wlan0: WPA: RX message 1 of
> 4-Way Handshake from 00:0
On Tue, Aug 6, 2013 at 4:57 PM, Johannes Berg wrote:
> On Tue, 2013-08-06 at 16:56 +0200, Sedat Dilek wrote:
>> On Tue, Aug 6, 2013 at 4:50 PM, Johannes Berg
>> wrote:
>> > On Tue, 2013-08-06 at 16:46 +0200, Sedat Dilek wrote:
>> >
>> > Heh, the inte
On Tue, Aug 6, 2013 at 4:59 PM, Sedat Dilek wrote:
> On Tue, Aug 6, 2013 at 4:57 PM, Johannes Berg
> wrote:
>> On Tue, 2013-08-06 at 16:56 +0200, Sedat Dilek wrote:
>>> On Tue, Aug 6, 2013 at 4:50 PM, Johannes Berg
>>> wrote:
>>> > On Tue, 20
On Tue, Aug 6, 2013 at 5:18 PM, Johannes Berg wrote:
>
>
>> I have sent you a v2 of my logs (with -d and rsyslog-7.x).
>
> Hmm, that looks different? There no longer is anything about "PSK might
> be wrong", but now just disconnections by the AP, which unfortunately
> indicate no reason.
>
> When
On Tue, Aug 6, 2013 at 5:20 PM, Sedat Dilek wrote:
> On Tue, Aug 6, 2013 at 5:18 PM, Johannes Berg
> wrote:
>>
>>
>>> I have sent you a v2 of my logs (with -d and rsyslog-7.x).
>>
>> Hmm, that looks different? There no longer is anything abou
On Tue, Aug 6, 2013 at 5:29 PM, Johannes Berg wrote:
> On Tue, 2013-08-06 at 17:27 +0200, Sedat Dilek wrote:
>> On Tue, Aug 6, 2013 at 5:20 PM, Sedat Dilek wrote:
>> > On Tue, Aug 6, 2013 at 5:18 PM, Johannes Berg
>> > wrote:
>> >>
>> >>
On Tue, Aug 6, 2013 at 5:43 PM, Sedat Dilek wrote:
> On Tue, Aug 6, 2013 at 5:29 PM, Johannes Berg
> wrote:
>> On Tue, 2013-08-06 at 17:27 +0200, Sedat Dilek wrote:
>>> On Tue, Aug 6, 2013 at 5:20 PM, Sedat Dilek wrote:
>>> > On Tue, Aug 6, 2013 at 5:1
On Mon, Jul 29, 2013 at 3:08 AM, Stephen Rothwell wrote:
> Hi Theodore,
>
> After merging the ext4 tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> fs/ext4/ialloc.c: In function '__ext4_new_inode':
> fs/ext4/ialloc.c:817:1: warning: label 'next_ino' defined but not
On Wed, Aug 7, 2013 at 7:38 AM, Stephen Rothwell wrote:
> Hi Sedat,
>
> On Wed, 7 Aug 2013 07:16:57 +0200 Sedat Dilek
> wrote:
>>
>> On Mon, Jul 29, 2013 at 3:08 AM, Stephen Rothwell
>> wrote:
>> >
>> > After merging the ext4 tree, today's l
On Wed, Aug 7, 2013 at 7:54 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130806:
>
> The ext4 tree lost its build failure.
>
> The mvebu tree gained a build failure so I used the version from
> next-20130806.
>
> The akpm tree gained conflicts against the ext4 tree.
>
> --
ce they are all in the freezer, so the output will be very long.
>
If you provide a patch, I will give it a try.
- Sedat -
> On Wed, Aug 7, 2013 at 4:02 PM, Rafael J. Wysocki wrote:
>> On Wednesday, August 07, 2013 04:25:14 PM Sedat Dilek wrote:
>>> On Wed, Aug 7, 2013 at 7:54
On Thu, Aug 8, 2013 at 1:36 AM, David Miller wrote:
> From: David Miller
> Date: Wed, 07 Aug 2013 16:27:48 -0700 (PDT)
>
>> Look, I'm going to fix this myself, because I'm pretty tired of
>> waiting for the obvious fix.
>
> Someone please test this:
>
Your patch on top of next-20130807 does not
On Thu, Aug 8, 2013 at 3:12 AM, Colin Cross wrote:
> On Wed, Aug 7, 2013 at 6:01 PM, Sedat Dilek wrote:
>> On Thu, Aug 8, 2013 at 1:34 AM, Colin Cross wrote:
>>> On Wed, Aug 7, 2013 at 4:15 PM, Sedat Dilek wrote:
>>>> On Thu, Aug 8, 2013 at 12:58 AM, Colin Cross
On Thu, Aug 8, 2013 at 10:46 AM, Sedat Dilek wrote:
> On Thu, Aug 8, 2013 at 3:12 AM, Colin Cross wrote:
>> On Wed, Aug 7, 2013 at 6:01 PM, Sedat Dilek wrote:
>>> On Thu, Aug 8, 2013 at 1:34 AM, Colin Cross wrote:
>>>> On Wed, Aug 7, 2013 at 4:15 PM, Sedat Dil
On Thu, Jul 25, 2013 at 3:36 PM, Daniel Vetter wrote:
> On Thu, Jul 25, 2013 at 12:37:44PM +0200, Sedat Dilek wrote:
>> On Thu, Jul 25, 2013 at 12:21 PM, Jani Nikula
>> wrote:
>> > On Thu, 25 Jul 2013, Sedat Dilek wrote:
>> >> On Thu, Jul 25, 2013 at
On Thu, Jul 25, 2013 at 4:27 PM, Daniel Vetter wrote:
> On Thu, Jul 25, 2013 at 04:23:40PM +0200, Sedat Dilek wrote:
>> On Thu, Jul 25, 2013 at 3:36 PM, Daniel Vetter wrote:
>> > On Thu, Jul 25, 2013 at 12:37:44PM +0200, Sedat Dilek wrote:
>> >> On Thu, Jul 25,
On Thu, Jul 25, 2013 at 5:05 PM, Daniel Vetter wrote:
> On Thu, Jul 25, 2013 at 5:03 PM, Sedat Dilek wrote:
>> On Thu, Jul 25, 2013 at 4:27 PM, Daniel Vetter wrote:
>>> On Thu, Jul 25, 2013 at 04:23:40PM +0200, Sedat Dilek wrote:
>>>> On Thu, Jul 25, 2013 at
On Thu, Jul 25, 2013 at 5:34 PM, Sedat Dilek wrote:
> On Thu, Jul 25, 2013 at 5:05 PM, Daniel Vetter wrote:
>> On Thu, Jul 25, 2013 at 5:03 PM, Sedat Dilek wrote:
>>> On Thu, Jul 25, 2013 at 4:27 PM, Daniel Vetter wrote:
>>>> On Thu, Jul 25, 2013 at 04:23
On Thu, Jul 25, 2013 at 7:26 PM, Chris Wilson wrote:
> On Thu, Jul 25, 2013 at 07:15:03PM +0200, Sedat Dilek wrote:
>> On Thu, Jul 25, 2013 at 7:01 PM, Chris Wilson
>> wrote:
>> > Basically boils down to either an object allocation failure or mmaping
>> > failur
On Thu, Jul 25, 2013 at 7:52 PM, Sedat Dilek wrote:
> On Thu, Jul 25, 2013 at 7:26 PM, Chris Wilson
> wrote:
>> On Thu, Jul 25, 2013 at 07:15:03PM +0200, Sedat Dilek wrote:
>>> On Thu, Jul 25, 2013 at 7:01 PM, Chris Wilson
>>> wrote:
>>> > Basically
On Thu, Jul 25, 2013 at 8:45 PM, Chris Wilson wrote:
> On Thu, Jul 25, 2013 at 08:03:06PM +0200, Sedat Dilek wrote:
>> On Thu, Jul 25, 2013 at 7:55 PM, Sedat Dilek wrote:
>> > F*ck. Wrong patch refreshed.
>> >
>>
>> New dmesg attached.
>
> Hmm, not
On Thu, Jul 25, 2013 at 9:32 PM, Sedat Dilek wrote:
> On Thu, Jul 25, 2013 at 9:22 PM, Chris Wilson
> wrote:
>> On Thu, Jul 25, 2013 at 09:12:41PM +0200, Sedat Dilek wrote:
>>> New -3 dmesg.
>>
>> That puts the ball back in the ddx's court. Next d
On Thu, Jul 25, 2013 at 11:52 PM, Chris Wilson wrote:
> On Thu, Jul 25, 2013 at 10:07:02PM +0200, Sedat Dilek wrote:
>> What means the bang line?
>>
>> [54.564] (II) GLX: Initialized DRI2 GL provider for screen 0
>> [54.565] bang: 1159
>> [54.565]
>
On Fri, Jul 26, 2013 at 1:25 AM, Chris Wilson wrote:
> On Fri, Jul 26, 2013 at 01:21:07AM +0200, Sedat Dilek wrote:
>> On Thu, Jul 25, 2013 at 11:52 PM, Chris Wilson
>> wrote:
>> > On Thu, Jul 25, 2013 at 10:07:02PM +0200, Sedat Dilek wrote:
>&g
On Fri, Jul 26, 2013 at 9:26 AM, Chris Wilson wrote:
> On Fri, Jul 26, 2013 at 09:15:14AM +0200, Sedat Dilek wrote:
>> For example: I could start my X with even doing ugly hacks like this...
>>
>> [ intel-ddx (git) ]
>> ...
>> Bool intel_uxa_create_screen_resource
On Fri, Jul 26, 2013 at 10:52 AM, Daniel Vetter wrote:
> On Fri, Jul 26, 2013 at 10:50 AM, Chris Wilson
> wrote:
>> On Fri, Jul 26, 2013 at 10:27:03AM +0200, Sedat Dilek wrote:
>>> On Fri, Jul 26, 2013 at 10:25 AM, Sedat Dilek wrote:
>>> > ...
>>> >
201 - 300 of 1444 matches
Mail list logo
