On 8/6/20 7:50 AM, Randy Dunlap wrote:
On 8/5/20 11:21 PM, Stephen Rothwell wrote:
Hi all,
on x86_64:
when CONFIG_MMU_NOTIFIER is not set/enabled:
../mm/migrate.c: In function 'migrate_vma_collect':
../mm/migrate.c:2481:7: error: 'struct mmu_notifier_range' has no member named
'migrate_p
On 8/5/20 11:21 PM, Stephen Rothwell wrote:
> Hi all,
>
on x86_64:
when CONFIG_MMU_NOTIFIER is not set/enabled:
../mm/migrate.c: In function 'migrate_vma_collect':
../mm/migrate.c:2481:7: error: 'struct mmu_notifier_range' has no member named
'migrate_pgmap_owner'
range.migrate_pgmap_owner =
Hi all,
News: The merge window has opened, so please do not add any v5.10
related material to your linux-next included branches until after the
merge window closes again.
Changes since 20200805:
My fixes tree contains:
dbf24e30ce2e ("device_cgroup: Fix RCU list debugging warning")
Non-merge
Hi all,
Changes since 20190805:
The crypto tree still had its build failure for which I applied a patch.
The integrity tree gained a build failure for which I applied a patch.
Non-merge commits (relative to Linus' tree): 4304
4721 files changed, 249705 insertions(+), 114654 deletions(-)
-
Hi all,
Changes since 20180803:
The vfs tree gained a build failure for which I applied a work around
patch.
The rdma tree gained a conflict against Linus' tree.
The net-next tree lost its build failure but gained another for which
I reverted a commit.
The wireless-drivers-next tree lost its b
Hi all,
Changes since 20150805:
The slave-dma tree gained a build failure so I used the version from
next-20150805.
The crypto tree lost its build failure.
The akpm-current tree gained a conflict against the char-misc tree and
a build failure for which I reverted a commit.
Non-merge commits (r
On Thu, Aug 07, 2014 at 01:25:07PM +0200, Maxime Ripard wrote:
> On Thu, Aug 07, 2014 at 09:56:14AM +0200, Philipp Zabel wrote:
> > Am Mittwoch, den 06.08.2014, 10:15 -0700 schrieb Randy Dunlap:
> > > On 08/06/14 09:42, Randy Dunlap wrote:
> > > > On 08/06/14 00:28, Stephen Rothwell wrote:
> > > >>
On Thu, Aug 07, 2014 at 09:56:14AM +0200, Philipp Zabel wrote:
> Am Mittwoch, den 06.08.2014, 10:15 -0700 schrieb Randy Dunlap:
> > On 08/06/14 09:42, Randy Dunlap wrote:
> > > On 08/06/14 00:28, Stephen Rothwell wrote:
> > >> Hi all,
> > >>
> > >> Please do not add code intended for v3.18 until af
Am Mittwoch, den 06.08.2014, 10:15 -0700 schrieb Randy Dunlap:
> On 08/06/14 09:42, Randy Dunlap wrote:
> > On 08/06/14 00:28, Stephen Rothwell wrote:
> >> Hi all,
> >>
> >> Please do not add code intended for v3.18 until after v3.17-rc1 is
> >> released.
> >>
> >> Changes since 20140805:
> >>
> >
On 08/06/14 09:42, Randy Dunlap wrote:
> On 08/06/14 00:28, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do not add code intended for v3.18 until after v3.17-rc1 is
>> released.
>>
>> Changes since 20140805:
>>
>
> on x86_64:
> when CONFIG_RESET_CONTROLLER is not enabled:
>
> ../drivers/dma/su
On 08/06/14 00:28, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add code intended for v3.18 until after v3.17-rc1 is
> released.
>
> Changes since 20140805:
>
on x86_64:
when CONFIG_RESET_CONTROLLER is not enabled:
../drivers/dma/sun6i-dma.c: In function 'sun6i_dma_probe':
../drivers/dm
Hi all,
Please do not add code intended for v3.18 until after v3.17-rc1 is
released.
Changes since 20140805:
The powerpc tree gained a build failure that only affected the powerpc
allyesconfig build, so I left it btroken.
The sparc-next tree gained a conflict against the sparc tree.
The drm tr
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:18 PM, Johannes Berg
>>> > 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:18 PM, Johannes Berg
>> > wrote:
>> >>
>> >>
>> >>> I have sent you a v2 of my logs (with -d and rsysl
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:
> >>
> >>
> >>> I have sent you a v2 of my logs (with -d and rsyslog-7.x).
> >>
> >> Hmm, that looks different? There no longer
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 about "PSK might
>> be wrong", but now just disconnections
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
> 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 was it working last?
johannes
--
To unsubscribe from this list: s
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, 2013-08-06 at 16:46 +0200, Sedat Dilek 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 interesting messages are always cut out of the log:
> >
> > Aug 6 16:30:34 fambox wpa_supplicant[2533]: wlan0:
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 interesting messages are always cut out of the log
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:04:0e:e4:00:3d (ver=
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:04:0e:e4:00:3d (ver=2)
Aug 6 16:30:34 fambox wpa_supplicant[2533]: RSN: msg 1/4 key
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 like security problems - check wpa_sup
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 like security problems - check wpa_sup
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 like security problems - check wpa_supplicant
log
johannes
--
To unsubscribe from this list: send
Hi all,
Changes since 20130805:
The ext4 tree still has its build failure so I used the version from
next-20130726.
The akpm tree gained a conflict against the drm-intel tree.
I have created today's linux-next tree at
Hi all,
OK, so the merge window is closed. Time to clean up your trees and then
start adding new stuff to them.
Changes since 20120803:
The cifs tree gained a build failure so I used the version from
next-20120803.
The acpi tree lost its build failure.
The rr tree gained a conflict against th
28 matches
Mail list logo
