On 4/4/19 1:51 PM, Randy Dunlap wrote:
> On 4/4/19 10:16 AM, Josh Poimboeuf wrote:
>> On Wed, Apr 03, 2019 at 03:29:17PM -0700, Randy Dunlap wrote:
>>> On 4/3/19 1:53 PM, Josh Poimboeuf wrote:
On Wed, Apr 03, 2019 at 08:02:43AM -0700, Randy Dunlap wrote:
> On 4/3/19 1:24 AM, Stephen Rothwe
On 4/4/19 10:16 AM, Josh Poimboeuf wrote:
> On Wed, Apr 03, 2019 at 03:29:17PM -0700, Randy Dunlap wrote:
>> On 4/3/19 1:53 PM, Josh Poimboeuf wrote:
>>> On Wed, Apr 03, 2019 at 08:02:43AM -0700, Randy Dunlap wrote:
On 4/3/19 1:24 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes s
On Wed, Apr 03, 2019 at 03:29:17PM -0700, Randy Dunlap wrote:
> On 4/3/19 1:53 PM, Josh Poimboeuf wrote:
> > On Wed, Apr 03, 2019 at 08:02:43AM -0700, Randy Dunlap wrote:
> >> On 4/3/19 1:24 AM, Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> Changes since 20190402:
> >>>
> >>
> >> on x86_64:
> >
On Wed, Apr 03, 2019 at 08:02:43AM -0700, Randy Dunlap wrote:
> On 4/3/19 1:24 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20190402:
> >
>
> on x86_64:
>
> arch/x86/entry/entry_64.o: warning: objtool: .entry.text+0x909: unreachable
> instruction
Your .o file looks odd. I ca
On 4/3/19 1:24 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190402:
>
on i386 or x86_64:
The patch(es) that change acpi_dev_get_first_match_name() to
acpi_dev_get_first_match_dev() have a problem when CONFIG_ACPI is not
set/enabled.
../drivers/gpio/gpio-merrifield.c: In function
On 4/3/19 1:24 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190402:
>
on x86_64:
arch/x86/entry/entry_64.o: warning: objtool: .entry.text+0x909: unreachable
instruction
obj file is attached.
--
~Randy
entry_64.o
Description: application/object
Hi all,
Changes since 20190402:
Removed trees: nand-fixes, spi-nor-fixes (at maintainers request)
The net-next tree gained a conflict against Linus' tree.
The nand tree lost its build failure.
The sound-asoc tree gained a build failure so I used the version from
next-20190402.
The mfd tree ga
Hi all,
Please do not add any v4.18 destined stuff to your linux-next included
trees until after v4.17-rc1 has been released.
Changes since 20180329:
The kbuild tree lost its build failure.
The asm-generic tree gained a conflict against Linus' tree.
The vfs tree still had its build failure for
On 04/03/17 01:13, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20170331:
>
on i386:
when SCSI_LPFC=y and
CONFIG_NVME_CORE=m
CONFIG_BLK_DEV_NVME=m
CONFIG_BLK_DEV_NVME_SCSI=y
CONFIG_NVME_FABRICS=m
CONFIG_NVME_FC=m
CONFIG_NVME_TARGET=m
drivers/built-in.o: In function `lpfc_nvme_create_loc
Hi all,
Changes since 20170331:
The net-next tree gained conflicts against the net tree.
The drm-misc tree gained conflict agsinst the drm tree.
The vhost tree still had its build failure, so I used the version from
next-20170329.
Non-merge commits (relative to Linus' tree): 6501
6753 files c
Hi all,
Please do not add material intended for v3.16 to your linux-next included
branches until after v3.15-rc1 is released.
This tree still fails (more than usual) the powerpc allyesconfig build.
Changes since 20140402:
The powerpc tree still had its build failure.
The drm-intel tree gained
Hi all,
Changes since 20130402:
The nfsd tree gained a conflict against Linus' tree and a build failure
for which I reverted 2 commits.
The vfs tree lost its build failure but gained another so I used the
version from next-20130328.
The v4l-dvb tree gained conflicts against the i2c tree.
The w
12 matches
Mail list logo
