Dear David Hawkins,
In message <49443c7f.3020...@ovro.caltech.edu> you wrote:
>
> > In message <2008121325.gn15...@game.jcrosoft.org> you wrote:
> >>> 705 /* Terminate fs_type string. Writing past the end of vistart
> >>> 706is ok - it's just the buffer. */
> >>> 707
Wolfgang Denk wrote:
> Dear Jean-Christophe PLAGNIOL-VILLARD,
>
> In message <2008121325.gn15...@game.jcrosoft.org> you wrote:
>>> 705 /* Terminate fs_type string. Writing past the end of vistart
>>> 706is ok - it's just the buffer. */
>>> 707 vistart->fs_type[8]
Dear Jean-Christophe PLAGNIOL-VILLARD,
In message <2008121325.gn15...@game.jcrosoft.org> you wrote:
>
> > 705 /* Terminate fs_type string. Writing past the end of vistart
> > 706is ok - it's just the buffer. */
> > 707 vistart->fs_type[8] = '\0';
>
> why not do
On 23:13 Sat 13 Dec , Wolfgang Denk wrote:
> Hello,
>
> building U-Boot with recent toolchains (like GCC-4.3.2) results in
> this warning:
>
> fat.c: In function 'read_bootsectandvi':
> fat.c:707: warning: array subscript is above array bounds
>
> The respective code looks like this:
>
> fs
Hello,
building U-Boot with recent toolchains (like GCC-4.3.2) results in
this warning:
fat.c: In function 'read_bootsectandvi':
fat.c:707: warning: array subscript is above array bounds
The respective code looks like this:
fs/fat/fat.c:
705 /* Terminate fs_type string. Writing past t
5 matches
Mail list logo
