public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
To: Andrew Morton <akpm@osdl.org>
Cc: Olaf Hering <olh@suse.de>, linux-kernel@vger.kernel.org
Subject: [Fwd: [PATCH 0/82] changing CONFIG_LOCALVERSION rebuilds too much, for no good reason.]
Date: Tue, 12 Jul 2005 13:51:14 -0300	[thread overview]
Message-ID: <42D3F502.9040209@brturbo.com.br> (raw)

Andrew,

	Do you intend to apply Olaf's patchsets to eliminate linux/version.h?
Some of them will not apply, because, at -mm2, KERNEL_VERSION isn't used
anymore.

	Maybe I can generate a patchset for V4L eliminating version.h, if you
want, against latest version.

Mauro.

-------- Original Message --------
Date: Sun, 10 Jul 2005 19:35:08 +0000
From: Olaf Hering <olh@suse.de>
To: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org


The following series of patches removes almost all inclusions
of linux/version.h. The 3 #defines are unused in most of the touched files.

A few drivers use the simple KERNEL_VERSION(a,b,c) macro, which is
unfortunatly
in linux/version.h. This define moved to linux/utsname.h

There are also lots of #ifdef for long obsolete kernels, this will go as
well.


quilt vi `find * -type f -name "*.[ch]"|xargs grep -El
'(UTS_RELEASE|LINUX_VERSION_CODE|KERNEL_VERSION|linux/version.h)'|grep
-Ev '(/(boot|coda|drm)/|~$)'`

search pattern:
/UTS_RELEASE|LINUX_VERSION_CODE|KERNEL_VERSION|linux/(utsname|version).h

PS: I hope my script is working ok.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



             reply	other threads:[~2005-07-12 16:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12 16:51 Mauro Carvalho Chehab [this message]
2005-07-12 23:57 ` [Fwd: [PATCH 0/82] changing CONFIG_LOCALVERSION rebuilds too much, for no good reason.] Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42D3F502.9040209@brturbo.com.br \
    --to=mchehab@brturbo.com.br \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olh@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox