From: Bjorn Andersson
Date: Mon, 27 Mar 2017 22:49:22 -0700
> On Mon 27 Mar 16:04 PDT 2017, David Miller wrote:
>
>> From: Bjorn Andersson
>> Date: Mon, 27 Mar 2017 15:58:37 -0700
>>
>> > I'm sorry, but I can't figure out how to
From: Bjorn Andersson
Date: Mon, 27 Mar 2017 22:49:22 -0700
> On Mon 27 Mar 16:04 PDT 2017, David Miller wrote:
>
>> From: Bjorn Andersson
>> Date: Mon, 27 Mar 2017 15:58:37 -0700
>>
>> > I'm sorry, but I can't figure out how to reproduce this.
>>
>> All of my builds are "make allmodconfig"
On Mon 27 Mar 16:04 PDT 2017, David Miller wrote:
> From: Bjorn Andersson
> Date: Mon, 27 Mar 2017 15:58:37 -0700
>
> > I'm sorry, but I can't figure out how to reproduce this.
>
> All of my builds are "make allmodconfig" so it should be easy to reproduce.
Thanks,
On Mon 27 Mar 16:04 PDT 2017, David Miller wrote:
> From: Bjorn Andersson
> Date: Mon, 27 Mar 2017 15:58:37 -0700
>
> > I'm sorry, but I can't figure out how to reproduce this.
>
> All of my builds are "make allmodconfig" so it should be easy to reproduce.
Thanks, turns out that while it was
From: Bjorn Andersson
Date: Mon, 27 Mar 2017 15:58:37 -0700
> I'm sorry, but I can't figure out how to reproduce this.
All of my builds are "make allmodconfig" so it should be easy to reproduce.
From: Bjorn Andersson
Date: Mon, 27 Mar 2017 15:58:37 -0700
> I'm sorry, but I can't figure out how to reproduce this.
All of my builds are "make allmodconfig" so it should be easy to reproduce.
On Thu 23 Mar 16:56 PDT 2017, David Miller wrote:
> From: Bjorn Andersson
> Date: Wed, 22 Mar 2017 14:57:33 -0700
>
> > On Wed 22 Mar 11:44 PDT 2017, David Miller wrote:
> >
> >> From: Bjorn Andersson
> >> Date: Mon, 20 Mar 2017 16:35:42
On Thu 23 Mar 16:56 PDT 2017, David Miller wrote:
> From: Bjorn Andersson
> Date: Wed, 22 Mar 2017 14:57:33 -0700
>
> > On Wed 22 Mar 11:44 PDT 2017, David Miller wrote:
> >
> >> From: Bjorn Andersson
> >> Date: Mon, 20 Mar 2017 16:35:42 -0700
> >>
> >> What is the status of the Kconfig
From: Bjorn Andersson
Date: Wed, 22 Mar 2017 14:57:33 -0700
> On Wed 22 Mar 11:44 PDT 2017, David Miller wrote:
>
>> From: Bjorn Andersson
>> Date: Mon, 20 Mar 2017 16:35:42 -0700
>>
>> What is the status of the Kconfig dependency fix
From: Bjorn Andersson
Date: Wed, 22 Mar 2017 14:57:33 -0700
> On Wed 22 Mar 11:44 PDT 2017, David Miller wrote:
>
>> From: Bjorn Andersson
>> Date: Mon, 20 Mar 2017 16:35:42 -0700
>>
>> What is the status of the Kconfig dependency fix and how will I be
>> getting it?
>>
>
> There are two
From: Marcel Holtmann
Date: Wed, 22 Mar 2017 20:23:15 +0100
> Hi Dave,
>
>>> By moving these client drivers to use RPMSG instead of the direct SMD
>>> API we can reuse them ontop of the newly added GLINK wire-protocol
>>> support found in the 820 and 835 Qualcomm platforms.
From: Marcel Holtmann
Date: Wed, 22 Mar 2017 20:23:15 +0100
> Hi Dave,
>
>>> By moving these client drivers to use RPMSG instead of the direct SMD
>>> API we can reuse them ontop of the newly added GLINK wire-protocol
>>> support found in the 820 and 835 Qualcomm platforms.
>>>
>>> As the new
On Wed 22 Mar 11:44 PDT 2017, David Miller wrote:
> From: Bjorn Andersson
> Date: Mon, 20 Mar 2017 16:35:42 -0700
>
> > By moving these client drivers to use RPMSG instead of the direct SMD
> > API we can reuse them ontop of the newly added GLINK wire-protocol
> >
On Wed 22 Mar 11:44 PDT 2017, David Miller wrote:
> From: Bjorn Andersson
> Date: Mon, 20 Mar 2017 16:35:42 -0700
>
> > By moving these client drivers to use RPMSG instead of the direct SMD
> > API we can reuse them ontop of the newly added GLINK wire-protocol
> > support found in the 820 and
On Wed, Mar 22, 2017 at 11:44:39AM -0700, David Miller wrote:
> From: Bjorn Andersson
> Date: Mon, 20 Mar 2017 16:35:42 -0700
>
> > By moving these client drivers to use RPMSG instead of the direct SMD
> > API we can reuse them ontop of the newly added GLINK
On Wed, Mar 22, 2017 at 11:44:39AM -0700, David Miller wrote:
> From: Bjorn Andersson
> Date: Mon, 20 Mar 2017 16:35:42 -0700
>
> > By moving these client drivers to use RPMSG instead of the direct SMD
> > API we can reuse them ontop of the newly added GLINK wire-protocol
> > support found in
On Mon, Mar 20, 2017 at 04:35:42PM -0700, Bjorn Andersson wrote:
> By moving these client drivers to use RPMSG instead of the direct SMD
> API we can reuse them ontop of the newly added GLINK wire-protocol
> support found in the 820 and 835 Qualcomm platforms.
>
> As the new (RPMSG-based) and old
On Mon, Mar 20, 2017 at 04:35:42PM -0700, Bjorn Andersson wrote:
> By moving these client drivers to use RPMSG instead of the direct SMD
> API we can reuse them ontop of the newly added GLINK wire-protocol
> support found in the 820 and 835 Qualcomm platforms.
>
> As the new (RPMSG-based) and old
Hi Dave,
>> By moving these client drivers to use RPMSG instead of the direct SMD
>> API we can reuse them ontop of the newly added GLINK wire-protocol
>> support found in the 820 and 835 Qualcomm platforms.
>>
>> As the new (RPMSG-based) and old SMD implementations are mutually
>> exclusive we
Hi Dave,
>> By moving these client drivers to use RPMSG instead of the direct SMD
>> API we can reuse them ontop of the newly added GLINK wire-protocol
>> support found in the 820 and 835 Qualcomm platforms.
>>
>> As the new (RPMSG-based) and old SMD implementations are mutually
>> exclusive we
From: Bjorn Andersson
Date: Mon, 20 Mar 2017 16:35:42 -0700
> By moving these client drivers to use RPMSG instead of the direct SMD
> API we can reuse them ontop of the newly added GLINK wire-protocol
> support found in the 820 and 835 Qualcomm platforms.
>
> As the
From: Bjorn Andersson
Date: Mon, 20 Mar 2017 16:35:42 -0700
> By moving these client drivers to use RPMSG instead of the direct SMD
> API we can reuse them ontop of the newly added GLINK wire-protocol
> support found in the 820 and 835 Qualcomm platforms.
>
> As the new (RPMSG-based) and old
Marcel Holtmann writes:
>> By moving these client drivers to use RPMSG instead of the direct SMD
>> API we can reuse them ontop of the newly added GLINK wire-protocol
>> support found in the 820 and 835 Qualcomm platforms.
>>
>> As the new (RPMSG-based) and old SMD
Marcel Holtmann writes:
>> By moving these client drivers to use RPMSG instead of the direct SMD
>> API we can reuse them ontop of the newly added GLINK wire-protocol
>> support found in the 820 and 835 Qualcomm platforms.
>>
>> As the new (RPMSG-based) and old SMD implementations are mutually
Hi Bjorn,
> By moving these client drivers to use RPMSG instead of the direct SMD
> API we can reuse them ontop of the newly added GLINK wire-protocol
> support found in the 820 and 835 Qualcomm platforms.
>
> As the new (RPMSG-based) and old SMD implementations are mutually
> exclusive we have
Hi Bjorn,
> By moving these client drivers to use RPMSG instead of the direct SMD
> API we can reuse them ontop of the newly added GLINK wire-protocol
> support found in the 820 and 835 Qualcomm platforms.
>
> As the new (RPMSG-based) and old SMD implementations are mutually
> exclusive we have
By moving these client drivers to use RPMSG instead of the direct SMD
API we can reuse them ontop of the newly added GLINK wire-protocol
support found in the 820 and 835 Qualcomm platforms.
As the new (RPMSG-based) and old SMD implementations are mutually
exclusive we have to change all client
By moving these client drivers to use RPMSG instead of the direct SMD
API we can reuse them ontop of the newly added GLINK wire-protocol
support found in the 820 and 835 Qualcomm platforms.
As the new (RPMSG-based) and old SMD implementations are mutually
exclusive we have to change all client
28 matches
Mail list logo