On Mon, Feb 15, 2016 at 06:31:29PM +, Sudeep Holla wrote:
> Understood. I knew lkml.org is broken if we tried very old links but
> expected to work at-least for couple of month old patches. Anyways
> hopefully [1] still works.
It's not old links in particular AFAICT, just general instability.
On 15/02/16 18:10, Mark Brown wrote:
On Wed, Feb 10, 2016 at 06:49:54PM +, Sudeep Holla wrote:
On 29/01/16 17:37, Sudeep Holla wrote:
The vexpress regulator implementation is currently just called vexpress.
This is a problem because it clashes with another module with the same
name in h
On Mon, Feb 15, 2016 at 06:10:17PM +, Mark Brown wrote:
> On Wed, Feb 10, 2016 at 06:49:54PM +, Sudeep Holla wrote:
> > [1] https://lkml.org/lkml/2016/1/29/7
> Please include human readable descriptions of things like commits and
> issues being discussed in e-mail in your mails, this make
On Wed, Feb 10, 2016 at 06:49:54PM +, Sudeep Holla wrote:
> On 29/01/16 17:37, Sudeep Holla wrote:
> >The vexpress regulator implementation is currently just called vexpress.
> >This is a problem because it clashes with another module with the same
> >name in hardware monitors.
> >This patch
Hi Mark,
On 29/01/16 17:37, Sudeep Holla wrote:
The vexpress regulator implementation is currently just called vexpress.
This is a problem because it clashes with another module with the same
name in hardware monitors.
This patch renames the vexpress regulator implementation to
vexpress-regulat
The vexpress regulator implementation is currently just called vexpress.
This is a problem because it clashes with another module with the same
name in hardware monitors.
This patch renames the vexpress regulator implementation to
vexpress-regulator so that there will be no clash in the module nam
6 matches
Mail list logo
