So, like, the other day Kumar Gala mumbled:
> "Add an option to pad the blob that is generated" broke the padding
> support. We were updating the fdt header after writing it.
>
> Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
Applied.
jdl
___
Linuxppc-
"Add an option to pad the blob that is generated" broke the padding
support. We were updating the fdt header after writing it.
Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
---
Better commit message for this, since my commit ID is different.
flattree.c | 12 +++-
1 files changed, 7 i
I guess it was really git commit
2b7dc8dce549ad72ad437b254bf756d7ba4c2a5a
Add an option to pad the blob that is generated
- k
On Dec 4, 2007, at 4:04 PM, David Gibson wrote:
> On Tue, Dec 04, 2007 at 10:27:52AM -0600, Kumar Gala wrote:
>> commit 22e787ca2b1e49a9a0f3c43262564ab1038c5c3c broke
On Tue, Dec 04, 2007 at 10:27:52AM -0600, Kumar Gala wrote:
> commit 22e787ca2b1e49a9a0f3c43262564ab1038c5c3c broke the padding
> support. We were updating the fdt header after writing it.
Uh.. I can't find a commit with that SHA1. Which one are you
referring to?
--
David Gibson
commit 22e787ca2b1e49a9a0f3c43262564ab1038c5c3c broke the padding
support. We were updating the fdt header after writing it.
Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
---
flattree.c | 12 +++-
1 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/flattree.c b/flattree.c
in