On lunedì 20 agosto 2007, Joe Perches wrote: > (untested) > > There are several files that > #include "linux/file" not #include <linux/file> > #include "asm/file" not #include <asm/file> > > Here's a little script that converts them: > > egrep -i -r -l --include=*.[ch] \ > "^[[:space:]]*\#[[:space:]]*include[[:space:]]*\"(linux|asm)/(.*)\"" * \ > > | xargs sed -i -e > | 's/^[[:space:]]*#[[:space:]]*include[[:space:]]*"\(linux\|asm\)\/\(.*\)"/ > |#include <\1\/\2>/g' > > Signed-off-by: Joe Perches <[EMAIL PROTECTED]>
Wait, this patch may or may not be sane (Jeff will tell more I guess). Since we use two different sets of headers (the host ones from userspace and the guest ones from Linux), this peculiar style has been used till now to make clear the difference (#include <file> is used for host headers) - at least that's what I think (I've never asked to Jeff, but I silently deduced this and followed this practice). -- "Doh!" (cit.), I've made another another mistake! Paolo Giarrusso, aka Blaisorblade Linux registered user n. 292729 http://www.user-mode-linux.org/~blaisorblade
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
