On 15-07-20, 08:18, Randy Dunlap wrote:
> On 7/15/20 1:05 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20200714:
> >
>
> on x86_64:
> # CONFIG_GPIOLIB is not set
>
> ../drivers/phy/allwinner/phy-sun4i-usb.c: In function
> ‘sun4i_usb_phy0_get_id_det’:
>
On 7/15/20 1:05 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200714:
>
on x86_64:
# CONFIG_GPIOLIB is not set
../drivers/phy/allwinner/phy-sun4i-usb.c: In function
‘sun4i_usb_phy0_get_id_det’:
../drivers/phy/allwinner/phy-sun4i-usb.c:367:11: error: implicit declaration of
Hi all,
Changes since 20200714:
My fixes tree contains:
dbf24e30ce2e ("device_cgroup: Fix RCU list debugging warning")
b236d81d9e4f ("powerpc/boot/dts: Fix dtc "pciex" warnings")
The bpf-next tree lost its a build failure.
The block tree gained a build failure for which i reverted a
On Tue, Jul 16, 2019 at 3:09 AM Pablo Neira Ayuso wrote:
>
> On Tue, Jul 16, 2019 at 02:56:09AM +0900, Masahiro Yamada wrote:
> > On Tue, Jul 16, 2019 at 2:33 AM Pablo Neira Ayuso
> > wrote:
> > >
> > > On Mon, Jul 15, 2019 at 07:28:04PM +0200, Laura Garcia wrote:
> > > > CC'ing netfilter.
> >
On Tue, Jul 16, 2019 at 02:56:09AM +0900, Masahiro Yamada wrote:
> On Tue, Jul 16, 2019 at 2:33 AM Pablo Neira Ayuso wrote:
> >
> > On Mon, Jul 15, 2019 at 07:28:04PM +0200, Laura Garcia wrote:
> > > CC'ing netfilter.
> > >
> > > On Mon, Jul 15, 2019 at 6:45 PM Randy Dunlap
> > > wrote:
> > > >
On Tue, Jul 16, 2019 at 2:33 AM Pablo Neira Ayuso wrote:
>
> On Mon, Jul 15, 2019 at 07:28:04PM +0200, Laura Garcia wrote:
> > CC'ing netfilter.
> >
> > On Mon, Jul 15, 2019 at 6:45 PM Randy Dunlap wrote:
> > >
> > > On 7/14/19 9:48 PM, Stephen Rothwell wrote:
> > > > Hi all,
> > > >
> > > >
On Mon, Jul 15, 2019 at 07:28:04PM +0200, Laura Garcia wrote:
> CC'ing netfilter.
>
> On Mon, Jul 15, 2019 at 6:45 PM Randy Dunlap wrote:
> >
> > On 7/14/19 9:48 PM, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Please do not add v5.4 material to your linux-next included branches
> > > until
CC'ing netfilter.
On Mon, Jul 15, 2019 at 6:45 PM Randy Dunlap wrote:
>
> On 7/14/19 9:48 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 20190712:
> >
>
> Hi,
>
On 7/14/19 9:48 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 20190712:
>
Hi,
I am seeing these build errors from HEADERS_TEST (or KERNEL_HEADERS_TEST)
for
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 20190712:
The pm tree gained a build failure for which I applied a fix patch.
Non-merge commits (relative to Linus' tree): 5001
4262 files changed, 599496
Hi all,
Changes since 20160714:
The pm tree gained conflicts against the i2c tree.
The drm tree gained a build failure for which I applied a merge fix patch.
The block tree gained conflicts against the ext4 tree.
The devicetree tree gained a conflict against the arc tree.
The luto-misc tree
Hi all,
Changes since 20160714:
The pm tree gained conflicts against the i2c tree.
The drm tree gained a build failure for which I applied a merge fix patch.
The block tree gained conflicts against the ext4 tree.
The devicetree tree gained a conflict against the arc tree.
The luto-misc tree
Hi all,
Changes since 20150714:
New tree: ftrace-fixes
The drm-intel tree gained another conflict against the drm-intel-fixes
tree.
The drm-misc tree lost its build failure.
The tip tree gained a build failure so I applied a fix patch.
Non-merge commits (relative to Linus' tree): 1971
1793
Hi all,
Changes since 20150714:
New tree: ftrace-fixes
The drm-intel tree gained another conflict against the drm-intel-fixes
tree.
The drm-misc tree lost its build failure.
The tip tree gained a build failure so I applied a fix patch.
Non-merge commits (relative to Linus' tree): 1971
1793
Hi all,
Changes since 20140714:
The v4l-dvb tree gained a build failure so I used the version from
next-20140714.
The pm tree gained a conflict against the ia64 tree.
The char-misc tree gained a conflict against the ia64 tree.
The random tree gained a conflict against the crypto-current tree.
Hi all,
Changes since 20140714:
The v4l-dvb tree gained a build failure so I used the version from
next-20140714.
The pm tree gained a conflict against the ia64 tree.
The char-misc tree gained a conflict against the ia64 tree.
The random tree gained a conflict against the crypto-current tree.
Hello,
On Monday, July 15, 2013 5:55 PM Randy Dunlap wrote:
> On 07/14/13 20:45, Stephen Rothwell wrote:
> > Hi all,
> >
> > The merge window is closed. Time to clean up all those unclean trees.
> > The good among you can just fast forward to v3.11-rc1 ;-)
> >
> > Changes since 20130712:
> >
>
Hello,
On Monday, July 15, 2013 5:55 PM Randy Dunlap wrote:
On 07/14/13 20:45, Stephen Rothwell wrote:
Hi all,
The merge window is closed. Time to clean up all those unclean trees.
The good among you can just fast forward to v3.11-rc1 ;-)
Changes since 20130712:
on x86_64:
Hi all,
The merge window is closed. Time to clean up all those unclean trees.
The good among you can just fast forward to v3.11-rc1 ;-)
Changes since 20130712:
The akpm tree lost some patches that turned up elsewhere.
Hi all,
The merge window is closed. Time to clean up all those unclean trees.
The good among you can just fast forward to v3.11-rc1 ;-)
Changes since 20130712:
The akpm tree lost some patches that turned up elsewhere.
20 matches
Mail list logo