Hi all,
Changes since 20180905:
Dropped trees: xarray, ida (temporarily)
New tree: icc
The vfs tree gained build failures for which I disabled some sample
programs.
The net-next tree still had its build failure for which I reverted
a commit.
The devicetree tree lost its build failure.
Hi all,
Changes since 20180905:
Dropped trees: xarray, ida (temporarily)
New tree: icc
The vfs tree gained build failures for which I disabled some sample
programs.
The net-next tree still had its build failure for which I reverted
a commit.
The devicetree tree lost its build failure.
On Wed, Sep 06, 2017 at 11:14:04AM -0700, Randy Dunlap wrote:
> On 09/06/17 11:03, Bjorn Helgaas wrote:
> > [+cc Marc, Thomas]
> >
> > On Wed, Sep 06, 2017 at 08:53:04AM -0700, Randy Dunlap wrote:
> >> On 09/05/17 22:57, Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> Please do not add any
On Wed, Sep 06, 2017 at 11:14:04AM -0700, Randy Dunlap wrote:
> On 09/06/17 11:03, Bjorn Helgaas wrote:
> > [+cc Marc, Thomas]
> >
> > On Wed, Sep 06, 2017 at 08:53:04AM -0700, Randy Dunlap wrote:
> >> On 09/05/17 22:57, Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> Please do not add any
On 09/06/17 11:03, Bjorn Helgaas wrote:
> [+cc Marc, Thomas]
>
> On Wed, Sep 06, 2017 at 08:53:04AM -0700, Randy Dunlap wrote:
>> On 09/05/17 22:57, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Please do not add any v4.15 related material to your linux-next
>>> included branches until after
On 09/06/17 11:03, Bjorn Helgaas wrote:
> [+cc Marc, Thomas]
>
> On Wed, Sep 06, 2017 at 08:53:04AM -0700, Randy Dunlap wrote:
>> On 09/05/17 22:57, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Please do not add any v4.15 related material to your linux-next
>>> included branches until after
[+cc Marc, Thomas]
On Wed, Sep 06, 2017 at 08:53:04AM -0700, Randy Dunlap wrote:
> On 09/05/17 22:57, Stephen Rothwell wrote:
> > Hi all,
> >
> > Please do not add any v4.15 related material to your linux-next
> > included branches until after v4.14-rc1 has been released.
> >
> > Changes since
[+cc Marc, Thomas]
On Wed, Sep 06, 2017 at 08:53:04AM -0700, Randy Dunlap wrote:
> On 09/05/17 22:57, Stephen Rothwell wrote:
> > Hi all,
> >
> > Please do not add any v4.15 related material to your linux-next
> > included branches until after v4.14-rc1 has been released.
> >
> > Changes since
On 09/05/17 22:57, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v4.15 related material to your linux-next
> included branches until after v4.14-rc1 has been released.
>
> Changes since 20170905:
>
on i386:
CONFIG_PCI is not enabled, so CONFIG_PCI_MSI is not enabled.
On 09/05/17 22:57, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v4.15 related material to your linux-next
> included branches until after v4.14-rc1 has been released.
>
> Changes since 20170905:
>
on i386:
CONFIG_PCI is not enabled, so CONFIG_PCI_MSI is not enabled.
Hi all,
Please do not add any v4.15 related material to your linux-next
included branches until after v4.14-rc1 has been released.
Changes since 20170905:
The devicetree tree gained conflicts against Linus' and the sound trees.
The akpm-current tree lost its build failure.
Non-merge commits
Hi all,
Please do not add any v4.15 related material to your linux-next
included branches until after v4.14-rc1 has been released.
Changes since 20170905:
The devicetree tree gained conflicts against Linus' and the sound trees.
The akpm-current tree lost its build failure.
Non-merge commits
Hi all,
Changes since 20160905:
The kbuild tree still had its build warnings for PowerPC, for which I
reverted a commit.
The tip tree gained a conflict against the kbuild tree.
The akpm-current tree lost its build failure after I applied a supplied
patch.
Non-merge commits (relative to Linus'
Hi all,
Changes since 20160905:
The kbuild tree still had its build warnings for PowerPC, for which I
reverted a commit.
The tip tree gained a conflict against the kbuild tree.
The akpm-current tree lost its build failure after I applied a supplied
patch.
Non-merge commits (relative to Linus'
Hi all,
Please do not add any code for v3.13 to your linux-next included branches
until after v3.12-rc1 is released.
Changes since 20130905:
*crickets*
I have created today's linux-next tree at
Hi all,
Please do not add any code for v3.13 to your linux-next included branches
until after v3.12-rc1 is released.
Changes since 20130905:
*crickets*
I have created today's linux-next tree at
16 matches
Mail list logo
