Re: [PATCH 0/4] Removing full paths from DT full_name

On Mon, Aug 7, 2017 at 9:21 PM, Michael Ellerman wrote: > Rob Herring writes: > >> On Tue, Jul 25, 2017 at 4:44 PM, Rob Herring wrote: >>> This series is the last steps to remove storing the full path for every >>> DT node. Instead, we can

Re: [PATCH 0/4] Removing full paths from DT full_name

On Mon, Aug 7, 2017 at 9:21 PM, Michael Ellerman wrote: > Rob Herring writes: > >> On Tue, Jul 25, 2017 at 4:44 PM, Rob Herring wrote: >>> This series is the last steps to remove storing the full path for every >>> DT node. Instead, we can create full path strings dynamically as needed >>> with

Re: [PATCH 0/4] Removing full paths from DT full_name

Rob Herring writes: > On Tue, Jul 25, 2017 at 4:44 PM, Rob Herring wrote: >> This series is the last steps to remove storing the full path for every >> DT node. Instead, we can create full path strings dynamically as needed >> with printf %pOF specifiers

Re: [PATCH 0/4] Removing full paths from DT full_name

Rob Herring writes: > On Tue, Jul 25, 2017 at 4:44 PM, Rob Herring wrote: >> This series is the last steps to remove storing the full path for every >> DT node. Instead, we can create full path strings dynamically as needed >> with printf %pOF specifiers (commit ce4fecf1fe15). There are a

Re: [PATCH 0/4] Removing full paths from DT full_name

On Tue, Jul 25, 2017 at 4:44 PM, Rob Herring wrote: > This series is the last steps to remove storing the full path for every > DT node. Instead, we can create full path strings dynamically as needed > with printf %pOF specifiers (commit ce4fecf1fe15). There are a number of >

Re: [PATCH 0/4] Removing full paths from DT full_name

On Tue, Jul 25, 2017 at 4:44 PM, Rob Herring wrote: > This series is the last steps to remove storing the full path for every > DT node. Instead, we can create full path strings dynamically as needed > with printf %pOF specifiers (commit ce4fecf1fe15). There are a number of > remaining direct

Re: [PATCH 0/4] Removing full paths from DT full_name

On Wed, Jul 26, 2017 at 9:20 AM, Frank Rowand wrote: > Hi Rob, > > On 07/25/17 14:44, Rob Herring wrote: >> This series is the last steps to remove storing the full path for every >> DT node. Instead, we can create full path strings dynamically as needed >> with printf

Re: [PATCH 0/4] Removing full paths from DT full_name

On Wed, Jul 26, 2017 at 9:20 AM, Frank Rowand wrote: > Hi Rob, > > On 07/25/17 14:44, Rob Herring wrote: >> This series is the last steps to remove storing the full path for every >> DT node. Instead, we can create full path strings dynamically as needed >> with printf %pOF specifiers (commit

Re: [PATCH 0/4] Removing full paths from DT full_name

Hi Rob, On 07/25/17 14:44, Rob Herring wrote: > This series is the last steps to remove storing the full path for every > DT node. Instead, we can create full path strings dynamically as needed > with printf %pOF specifiers (commit ce4fecf1fe15). There are a number of > remaining direct users

Re: [PATCH 0/4] Removing full paths from DT full_name

Hi Rob, On 07/25/17 14:44, Rob Herring wrote: > This series is the last steps to remove storing the full path for every > DT node. Instead, we can create full path strings dynamically as needed > with printf %pOF specifiers (commit ce4fecf1fe15). There are a number of > remaining direct users

[PATCH 0/4] Removing full paths from DT full_name

This series is the last steps to remove storing the full path for every DT node. Instead, we can create full path strings dynamically as needed with printf %pOF specifiers (commit ce4fecf1fe15). There are a number of remaining direct users of full_name after this series. I don't believe there

[PATCH 0/4] Removing full paths from DT full_name

This series is the last steps to remove storing the full path for every DT node. Instead, we can create full path strings dynamically as needed with printf %pOF specifiers (commit ce4fecf1fe15). There are a number of remaining direct users of full_name after this series. I don't believe there