Re: [PATCH,RFC] ext3: Add support for non-native signed/unsignedhtree hash algorithms

[Jeremy Fitzhardinge]

Andreas Dilger wrote:
> > Hmm..... is it considered safe to depend on the userspace limits.h
> > header file?  I guess if we trust that header file to be correct we
> > could check the value of CHAR_MIN and/or CHAR_MAX as defined by
> > limits.h.
> >     
>
> That would likely fail on cross-compiled environments, right?
>   

/usr/include/limits.h uses #include_next to pick up gcc's private 
limits.h, so it should be safe to use in a kernel cross-build 
environment.  (Picking up the compiler's limits.h directly would be better.)

   J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/