Hi Darrick,
On Thu, 18 Jul 2019 17:30:45 -0700 "Darrick J. Wong"
wrote:
>
> ... oh, this is some weird "mash all the kernel headers together and see
> if they compile" thing, isn't it? Um, yes, iomap.h should only be
> tested if CONFIG_IOMAP=y (which in turn requires CONFIG_BLOCK=y)
Actually i
Hi all,
On Fri, 19 Jul 2019 10:05:57 +1000 Stephen Rothwell
wrote:
>
> On Thu, 18 Jul 2019 10:00:22 -0700 Randy Dunlap wrote:
> >
> > on x86_64, when CONFIG_BLOCK is not set:
> >
> > CC include/linux/iomap.h.s
> > In file included from :0:0:
> > ./../include/linux/iomap.h: In function ‘
On Fri, Jul 19, 2019 at 10:05:57AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> On Thu, 18 Jul 2019 10:00:22 -0700 Randy Dunlap wrote:
> >
> > on x86_64, when CONFIG_BLOCK is not set:
> >
> > CC include/linux/iomap.h.s
> > In file included from :0:0:
> > ./../include/linux/iomap.h: In fun
Hi all,
On Thu, 18 Jul 2019 10:00:22 -0700 Randy Dunlap wrote:
>
> on x86_64, when CONFIG_BLOCK is not set:
>
> CC include/linux/iomap.h.s
> In file included from :0:0:
> ./../include/linux/iomap.h: In function ‘iomap_sector’:
> ./../include/linux/iomap.h:76:48: error: ‘SECTOR_SHIFT’ unde
On 7/17/19 8:37 PM, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add v5.4 material to your linux-next included branches
> until after v5.3-rc1 has been released.
>
> Changes since 20190717:
>
on x86_64, when CONFIG_BLOCK is not set:
CC include/linux/iomap.h.s
In file included fro
Hi all,
Please do not add v5.4 material to your linux-next included branches
until after v5.3-rc1 has been released.
Changes since 20190717:
The kbuild tree lost its build failure.
The xfs tree gained a conflict against Linus' tree.
Non-merge commits (relative to Linus' tree): 2156
1939 files
On 07/18/2018 12:59 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20180717:
>
> The netfilter-next tree gained a conflict against the net tree and
> a build failure due to an interaction with the net tree for which I
> applied a merge fix patch.
on x86_64:
../net/netfilter/nft_tproxy.c
Hi all,
Changes since 20180717:
The netfilter-next tree gained a conflict against the net tree and
a build failure due to an interaction with the net tree for which I
applied a merge fix patch.
The ipvs-next tree gained conflicts against the netfilter-next tree.
The integrity tree lost its buil
Hi all,
Changes since 20170717:
The btrfs-kdave tree gained a conflict against Linus' tree.
The net-next tree gained a build failure so I used the version from
next-20170717.
The drm-misc tree gained a confict against the drm-misc-fixes tree and
a build failure for which I applied a merge fix p
Hi all,
Changes since 20160715:
The net-next tree gained conflicts against the net tree.
The kspp tree gained conflicts against the arm64 and powerpc trees.
The device-mapper tree gained a conflict against the block tree.
The tip tree gained 2 build failures for which I applied a patches.
The
Hi all,
Changes since 20140717:
The net-next tree gained a build failure so I used the version from
next-20140717.
The irqchip tree gained conflicts against the arm64 and trivial trees.
The akpm-current tree gained a conflict against the random tree.
Non-merge commits (relative to Linus' tree)
Hi all,
Changes since 20130717:
The sound-asoc tree lost a build failure but still has another so I used
the version from next-20130715.
The drm-intel tree gained conflicts against the drm-intel-fixes tree.
The aio tree lost its build failure.
The akpm tree gained a conflict against the drm-in
12 matches
Mail list logo
