Hi all,
Changes since 20180926:
Dropped trees: xarray, ida (temporarily)
The pci tree lost its build failure.
Non-merge commits (relative to Linus' tree): 6252
6435 files changed, 294737 insertions(+), 131625 deletions(-)
Hi all,
Changes since 20180926:
Dropped trees: xarray, ida (temporarily)
The pci tree lost its build failure.
Non-merge commits (relative to Linus' tree): 6252
6435 files changed, 294737 insertions(+), 131625 deletions(-)
Hi all,
News: I will not be doing linux-next releases from Setp 30 to Oct 30
(inclusive).
Changes since 20170926:
The cifs tree lost its build failure.
The staging tree lost its build failure.
Non-merge commits (relative to Linus' tree): 2216
2254 files changed, 69344 insertions(+), 25159
Hi all,
News: I will not be doing linux-next releases from Setp 30 to Oct 30
(inclusive).
Changes since 20170926:
The cifs tree lost its build failure.
The staging tree lost its build failure.
Non-merge commits (relative to Linus' tree): 2216
2254 files changed, 69344 insertions(+), 25159
On (09/27/16 19:03), Sergey Senozhatsky wrote:
> Hello,
>
> On (09/27/16 16:40), Stephen Rothwell wrote:
> >
> > Changes since 20160923:
> >
>
> seems that commit e3b37f11e6e4e6b6 ("netfilter: replace list_head with
> single linked list") breaks the build on !CONFIG_NETFILTER_INGRESS systems
>
On (09/27/16 19:03), Sergey Senozhatsky wrote:
> Hello,
>
> On (09/27/16 16:40), Stephen Rothwell wrote:
> >
> > Changes since 20160923:
> >
>
> seems that commit e3b37f11e6e4e6b6 ("netfilter: replace list_head with
> single linked list") breaks the build on !CONFIG_NETFILTER_INGRESS systems
>
Hello,
On (09/27/16 16:40), Stephen Rothwell wrote:
>
> Changes since 20160923:
>
seems that commit e3b37f11e6e4e6b6 ("netfilter: replace list_head with
single linked list") breaks the build on !CONFIG_NETFILTER_INGRESS systems
accessing ->nf_hooks_ingress
static void nf_set_hooks_head(struct
Hello,
On (09/27/16 16:40), Stephen Rothwell wrote:
>
> Changes since 20160923:
>
seems that commit e3b37f11e6e4e6b6 ("netfilter: replace list_head with
single linked list") breaks the build on !CONFIG_NETFILTER_INGRESS systems
accessing ->nf_hooks_ingress
static void nf_set_hooks_head(struct
Hi all,
Changes since 20160923:
New tree: vfs-jk
The vfs-jk tree gained a conflict against the fuse tree.
The rdma tree gained a build failure so I used the version from
next-20160923.
The drm-exynos tree gained a conflict against the drm tree.
The kvm-arm tree lost its build failure but
Hi all,
Changes since 20160923:
New tree: vfs-jk
The vfs-jk tree gained a conflict against the fuse tree.
The rdma tree gained a build failure so I used the version from
next-20160923.
The drm-exynos tree gained a conflict against the drm tree.
The kvm-arm tree lost its build failure but
On Fri, 2013-09-27 at 19:05 +1000, Stephen Rothwell wrote:
> Hi all,
>
> Heads up: I will be having a 3 week break leading up to the kernel
> summit. This means that next-20130927 (today) will be the last
> linux-next release until next-20131028 (or maybe 29). I presume that
> Linus will be up
Hi all,
Heads up: I will be having a 3 week break leading up to the kernel
summit. This means that next-20130927 (today) will be the last
linux-next release until next-20131028 (or maybe 29). I presume that
Linus will be up to v3.12-rc7 by then and -rc7 is often the last before
a release ...
Hi all,
Heads up: I will be having a 3 week break leading up to the kernel
summit. This means that next-20130927 (today) will be the last
linux-next release until next-20131028 (or maybe 29). I presume that
Linus will be up to v3.12-rc7 by then and -rc7 is often the last before
a release ...
On Fri, 2013-09-27 at 19:05 +1000, Stephen Rothwell wrote:
Hi all,
Heads up: I will be having a 3 week break leading up to the kernel
summit. This means that next-20130927 (today) will be the last
linux-next release until next-20131028 (or maybe 29). I presume that
Linus will be up to
14 matches
Mail list logo
