Hi all,
News: there will be no linux-next release on Thursday April 25.
Changes since 20190418:
The at91 tree gained a build failure so I used the version from
next-20190418.
The v4l-dvb-next tree gained a conflict against the v4l-dvb tree.
The next-next tree gained a build failure for which I
Hi all,
Changes since 20180420:
The usb tree gained a conflict against the usb.current tree.
Non-merge commits (relative to Linus' tree): 1418
1459 files changed, 55564 insertions(+), 22829 deletions(-)
I have create
Hi all,
Please do not add any v4.2 material to your linux-next included trees
until after v4.1-rc1 is released.
Changes since 20150422:
Removed tree: exec-domain (merged)
Non-merge commits (relative to Linus' tree): 1466
1311 files changed, 78501 insertions(+), 20869 deletions(-)
Hi all,
This tree still fails (more than usual) the powerpc allyesconfig build.
Changes since 20140422:
New tree: drm-panel
The arm tree still produces quite a few build warnings.
The powerpc tree still had its build failure.
The vfs tree still had its build failure so I applied a fix patch.
On Thu, Apr 25, 2013 at 7:56 PM, Rik van Riel wrote:
> On 04/24/2013 07:05 PM, Sedat Dilek wrote:
>>
>> On Thu, Apr 25, 2013 at 12:16 AM, Davidlohr Bueso
>> wrote:
>
>
>>> This patch converts the IPC RCU header's reference counter to atomic_t.
>>> The return of
>>> ipc_rcu_getref() is modified to
On 04/24/2013 07:05 PM, Sedat Dilek wrote:
On Thu, Apr 25, 2013 at 12:16 AM, Davidlohr Bueso
wrote:
This patch converts the IPC RCU header's reference counter to atomic_t. The
return of
ipc_rcu_getref() is modified to inform the callers if it actually succeeded.
Now all callers return -EIDR
On Thu, Apr 25, 2013 at 1:38 AM, Davidlohr Bueso wrote:
> On Thu, 2013-04-25 at 01:05 +0200, Sedat Dilek wrote:
>> On Thu, Apr 25, 2013 at 12:16 AM, Davidlohr Bueso
>> wrote:
>> > From: Davidlohr Bueso
>> >
>> > Sedat reported an issue leading to a NULL dereference in update_queue():
>> >
>> > [
On Thu, 2013-04-25 at 01:05 +0200, Sedat Dilek wrote:
> On Thu, Apr 25, 2013 at 12:16 AM, Davidlohr Bueso
> wrote:
> > From: Davidlohr Bueso
> >
> > Sedat reported an issue leading to a NULL dereference in update_queue():
> >
> > [ 178.490583] BUG: spinlock bad magic on CPU#1, sh/8066
> > [ 178
On Thu, Apr 25, 2013 at 12:16 AM, Davidlohr Bueso
wrote:
> From: Davidlohr Bueso
>
> Sedat reported an issue leading to a NULL dereference in update_queue():
>
> [ 178.490583] BUG: spinlock bad magic on CPU#1, sh/8066
> [ 178.490595] lock: 0x88008b53ea18, .magic: 6b6b6b6b, .owner:
> make/
From: Davidlohr Bueso
Sedat reported an issue leading to a NULL dereference in update_queue():
[ 178.490583] BUG: spinlock bad magic on CPU#1, sh/8066
[ 178.490595] lock: 0x88008b53ea18, .magic: 6b6b6b6b, .owner: make/8068,
.owner_cpu: 3
[ 178.490599] BUG: unable to handle kernel NULL p
On 04/23/13 12:19, David Miller wrote:
> From: Randy Dunlap
> Date: Tue, 23 Apr 2013 11:04:18 -0700
>
>> On 04/23/13 01:00, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20130422:
>>>
>>> The net-next tree lost its build failure but gained another for which I
>>> applied a patch.
>>>
From: Randy Dunlap
Date: Tue, 23 Apr 2013 11:04:18 -0700
> On 04/23/13 01:00, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20130422:
>>
>> The net-next tree lost its build failure but gained another for which I
>> applied a patch.
>>
>
>
> when CONFIG_NETLINK_MMAP is not enabled:
>
On 04/23/13 01:00, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130422:
>
on i386, when CONFIG_PM_RUNTIME is not enabled so REALTEK_AUTOPM is not
enabled:
drivers/usb/storage/realtek_cr.c: In function 'realtek_cr_destructor':
drivers/usb/storage/realtek_cr.c:942:11: error: 'struct rts
On 04/23/13 01:00, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130422:
>
> The net-next tree lost its build failure but gained another for which I
> applied a patch.
>
when CONFIG_NETLINK_MMAP is not enabled:
net/netlink/diag.c: In function 'sk_diag_put_rings_cfg':
net/netlink/diag.
14 matches
Mail list logo
