On Tue, Apr 28, 2015 at 10:25:46AM +0300, Jani Nikula wrote:
> On Mon, 27 Apr 2015, gr...@linuxhacker.ru wrote:
> > From: Oleg Drokin
> >
> > Need to free just allocated ctx allocation if we cannot
> > get our config mutex.
> >
> > This one has been flagged by kbuild bot all the way back in
On Tue, Apr 28, 2015 at 10:25:46AM +0300, Jani Nikula wrote:
On Mon, 27 Apr 2015, gr...@linuxhacker.ru wrote:
From: Oleg Drokin gr...@linuxhacker.ru
Need to free just allocated ctx allocation if we cannot
get our config mutex.
This one has been flagged by kbuild bot all the way back
On Mon, 27 Apr 2015, gr...@linuxhacker.ru wrote:
> From: Oleg Drokin
>
> Need to free just allocated ctx allocation if we cannot
> get our config mutex.
>
> This one has been flagged by kbuild bot all the way back in August,
> but somehow nobody picked it up:
>
On Mon, 27 Apr 2015, gr...@linuxhacker.ru wrote:
From: Oleg Drokin gr...@linuxhacker.ru
Need to free just allocated ctx allocation if we cannot
get our config mutex.
This one has been flagged by kbuild bot all the way back in August,
but somehow nobody picked it up:
From: Oleg Drokin
Need to free just allocated ctx allocation if we cannot
get our config mutex.
This one has been flagged by kbuild bot all the way back in August,
but somehow nobody picked it up:
https://lists.01.org/pipermail/kbuild/2014-August/001691.html
In addition there is another
From: Oleg Drokin gr...@linuxhacker.ru
Need to free just allocated ctx allocation if we cannot
get our config mutex.
This one has been flagged by kbuild bot all the way back in August,
but somehow nobody picked it up:
https://lists.01.org/pipermail/kbuild/2014-August/001691.html
In addition
6 matches
Mail list logo