On Wed, Feb 13, 2019 at 01:12:08PM -0800, Randy Dunlap wrote:
> On 2/13/19 10:31 AM, Brian Masney wrote:
> > On Wed, Feb 13, 2019 at 06:18:17PM +0100, Marc Gonzalez wrote:
> >> On 13/02/2019 17:47, Randy Dunlap wrote:
> >>
> >>> seen on i386:
> >>>
> >>> when CONFIG_IRQ_DOMAIN_HIERARCHY is not enab
On Wed, Feb 13, 2019 at 06:18:17PM +0100, Marc Gonzalez wrote:
> On 13/02/2019 17:47, Randy Dunlap wrote:
>
> > seen on i386:
> >
> > when CONFIG_IRQ_DOMAIN_HIERARCHY is not enabled:
> >
> > ../drivers/spmi/spmi-pmic-arb.c:1154:2: error: unknown field ‘activate’
> > specified in initializer
> >
On 13/02/2019 17:47, Randy Dunlap wrote:
> seen on i386:
>
> when CONFIG_IRQ_DOMAIN_HIERARCHY is not enabled:
>
> ../drivers/spmi/spmi-pmic-arb.c:1154:2: error: unknown field ‘activate’
> specified in initializer
> .activate = qpnpint_irq_domain_activate,
> ^
> ../drivers/spmi/spmi-pmic-arb
On 2/12/19 11:39 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190212:
>
seen on i386:
when CONFIG_IRQ_DOMAIN_HIERARCHY is not enabled:
../drivers/spmi/spmi-pmic-arb.c:1154:2: error: unknown field ‘activate’
specified in initializer
.activate = qpnpint_irq_domain_activate,
^
.
On 02/12/2018 08:15 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20180212:
>
> Non-merge commits (relative to Linus' tree): 963
> 1297 files changed, 63627 insertions(+), 31515 deletions(-)
>
>
on i386:
ar
Hi Stephen,
On 02/13/2015 03:37 PM, Stephen Rothwell wrote:
Hi Guenter,
On Fri, 13 Feb 2015 10:54:28 -0800 Guenter Roeck wrote:
I see a number of runtime failures with this version.
It affects alpha, mips64, ppc64, and x86_64.
Symptom is always the same. There are lots of
BUG: non-zero nr_p
On 02/13/15 16:32, Randy Dunlap wrote:
> On 02/12/15 21:56, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do not add any material destined for v3.21 to your linux-next
>> included trees until after v3.20-rc1 has been released.
>>
>> Changes since 20150212:
>
> on i386: when CONFIG_I2C is not en
On 02/12/15 21:56, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material destined for v3.21 to your linux-next
> included trees until after v3.20-rc1 has been released.
>
> Changes since 20150212:
on i386: when CONFIG_I2C is not enabled:
../drivers/iio/magnetometer/ak8975.c: In
Hi Guenter,
On Fri, 13 Feb 2015 10:54:28 -0800 Guenter Roeck wrote:
>
> I see a number of runtime failures with this version.
> It affects alpha, mips64, ppc64, and x86_64.
> Symptom is always the same. There are lots of
>
> BUG: non-zero nr_pmds on freeing mm: X (where X is 1..4)
>
> messages
On Fri, Feb 13, 2015 at 04:56:15PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material destined for v3.21 to your linux-next
> included trees until after v3.20-rc1 has been released.
>
> Changes since 20150212:
>
> The mips tree gained a conflict against Linus' tree.
>
>
On 02/12/15 21:56, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material destined for v3.21 to your linux-next
> included trees until after v3.20-rc1 has been released.
>
> Changes since 20150212:
on x86_64, when
# CONFIG_NFS_FS is not set
CONFIG_NFSD=y
# CONFIG_NFSD_V3 is not set
2015-02-13, 16:56:15 +1100, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material destined for v3.21 to your linux-next
> included trees until after v3.20-rc1 has been released.
>
> Changes since 20150212:
Hi Stephen,
Your conflict resolution in
8fe7fba50596 "Merge branch 'akpm-
On Thu, Feb 14, 2013 at 4:23 PM, Stephen Rothwell wrote:
> Hi Greg,
>
> On Thu, 14 Feb 2013 16:02:29 -0800 Greg KH wrote:
>> On Fri, Feb 15, 2013 at 10:55:19AM +1100, Stephen Rothwell wrote:
>> >
>> > Also, has someone checked to see if any of the CONFIG_ symbols that had a
>> > dependency on TTY
Hi Greg,
On Thu, 14 Feb 2013 16:02:29 -0800 Greg KH wrote:
>
> On Fri, Feb 15, 2013 at 10:55:19AM +1100, Stephen Rothwell wrote:
> >
> > The patch below is needed in the tty tree (which introduced CONFIG_TTY).
>
> Ok, now done.
Thanks.
> > Also, has someone checked to see if any of the CONFIG
On Fri, Feb 15, 2013 at 10:55:19AM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> The patch below is needed in the tty tree (which introduced CONFIG_TTY).
Ok, now done.
> Also, has someone checked to see if any of the CONFIG_ symbols that had a
> dependency on TTY added are selected anywhere else
Hi Greg,
The patch below is needed in the tty tree (which introduced CONFIG_TTY).
Also, has someone checked to see if any of the CONFIG_ symbols that had a
dependency on TTY added are selected anywhere else?
On Thu, 14 Feb 2013 10:55:06 -0800 Randy Dunlap wrote:
>
> On 02/14/13 10:45, Randy Dun
On 02/14/13 10:45, Randy Dunlap wrote:
> On 02/13/13 19:00, Rusty Russell wrote:
>> Randy Dunlap writes:
>>
>>> On 02/13/13 00:35, Stephen Rothwell wrote:
Hi all,
Changes since 20130212:
>>>
>>> on i386:
>>>
>>> drivers/built-in.o: In function `in_intr':
>>> virtio_console.c:(.text+
On 02/13/13 19:00, Rusty Russell wrote:
> Randy Dunlap writes:
>
>> On 02/13/13 00:35, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20130212:
>>
>> on i386:
>>
>> drivers/built-in.o: In function `in_intr':
>> virtio_console.c:(.text+0x2dd31): undefined reference to `hvc_poll'
>> virt
Hi Rusty,
On Thu, 14 Feb 2013 13:30:37 +1030 Rusty Russell wrote:
>
> This looks like an impossible config. CONFIG_VIRTIO_CONSOLE=y, but
> CONFIG_HVC_DRIVER isn't set.
>
> From drivers/char/Kconfig:
>
> config VIRTIO_CONSOLE
> tristate "Virtio console"
> dep
Randy Dunlap writes:
> On 02/13/13 00:35, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20130212:
>
> on i386:
>
> drivers/built-in.o: In function `in_intr':
> virtio_console.c:(.text+0x2dd31): undefined reference to `hvc_poll'
> virtio_console.c:(.text+0x2dd41): undefined reference to
20 matches
Mail list logo