On Tue, Oct 25, 2016 at 09:09:33PM -0400, Paul Gortmaker wrote:
> On Mon, Oct 24, 2016 at 11:31 PM, Stephen Rothwell
> wrote:
> > Hi all,
> >
> > There will probably be no linux-next releases next week while I attend
> > the Kernel Summit.
> >
> > Changes since 20161024:
> >
> > The pm tree gaine
On Mon, Oct 24, 2016 at 11:31 PM, Stephen Rothwell
wrote:
> Hi all,
>
> There will probably be no linux-next releases next week while I attend
> the Kernel Summit.
>
> Changes since 20161024:
>
> The pm tree gained a conflict against the imx-mxs tree.
>
> The mali-dp tree gained a conflict agains
Hi all,
There will probably be no linux-next releases next week while I attend
the Kernel Summit.
Changes since 20161024:
The pm tree gained a conflict against the imx-mxs tree.
The mali-dp tree gained a conflict against the drm-misc tree.
The sunxi tree gained a build failure so I used the ve
On Mon, Oct 28, 2013 at 09:01:24AM +0100, Thierry Reding wrote:
> Perhaps something like the above scheme might be a good compromise. On
> one hand, many people are using linux-next for their daily work, myself
> included. That implies that if linux-next doesn't build, people either
> use a previo
On Fri, Oct 25, 2013 at 03:31:44PM -0700, Randy Dunlap wrote:
> On 10/25/13 08:03, Thierry Reding wrote:
> > Hi all,
> >
> > I've uploaded today's linux-next tree to the master branch of the
> > repository below:
> >
> > git://gitorious.org/thierryreding/linux-next.git
> >
> > A next-201
On Fri, Oct 25, 2013 at 03:31:44PM -0700, Randy Dunlap wrote:
> That's unfortunate. The fixes should be part of the tree IMO.
What Stephen does (which does seem like a good policy) is to keep the
tree at the previous day's version instead of taking a new version if it
introduces breakages on the
On 10/25/13 08:03, Thierry Reding wrote:
> Hi all,
>
> I've uploaded today's linux-next tree to the master branch of the
> repository below:
>
> git://gitorious.org/thierryreding/linux-next.git
>
> A next-20131025 tag is also provided for convenience.
>
> One new trivial conflicts and a
Ignore my patch. Already a patch by Thierry Reding is in PM next tree.
Thanks,
Srinivas
On 10/25/2013 03:17 PM, Srinivas Pandruvada wrote:
On 10/25/2013 12:46 PM, Randy Dunlap wrote:
On 10/25/13 08:03, Thierry Reding wrote:
Hi all,
I've uploaded today's linux-next tree to the master branc
On 10/25/2013 12:46 PM, Randy Dunlap wrote:
On 10/25/13 08:03, Thierry Reding wrote:
Hi all,
I've uploaded today's linux-next tree to the master branch of the
repository below:
git://gitorious.org/thierryreding/linux-next.git
A next-20131025 tag is also provided for convenience.
On
On 10/25/13 08:03, Thierry Reding wrote:
> Hi all,
>
> I've uploaded today's linux-next tree to the master branch of the
> repository below:
>
> git://gitorious.org/thierryreding/linux-next.git
>
> A next-20131025 tag is also provided for convenience.
>
> One new trivial conflicts and a
On Fri, Oct 25, 2013 at 05:03:45PM +0200, Thierry Reding wrote:
> Hi all,
>
> I've uploaded today's linux-next tree to the master branch of the
> repository below:
>
> git://gitorious.org/thierryreding/linux-next.git
>
> A next-20131025 tag is also provided for convenience.
>
> One new
On 10/25/13 08:03, Thierry Reding wrote:
> Hi all,
>
> I've uploaded today's linux-next tree to the master branch of the
> repository below:
>
> git://gitorious.org/thierryreding/linux-next.git
>
> A next-20131025 tag is also provided for convenience.
>
> One new trivial conflicts and a
Hi all,
I've uploaded today's linux-next tree to the master branch of the
repository below:
git://gitorious.org/thierryreding/linux-next.git
A next-20131025 tag is also provided for convenience.
One new trivial conflicts and a new build failure caused by an incorrect
use of the genpool
Hi all,
Changes since 201201024:
New tree: akpm-current
The modules tree lost its conflict.
The pm tree lost its build failure.
The usb tree gained a conflict against the usb.current tree.
The staging tree gained a conflict against the staging.current tree.
The akpm tree lost its 2 build fai
14 matches
Mail list logo