public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: maximilian attems <max@stro.at>, Ray Lee <ray-lk@madrabbit.org>,
	Arnaud Lacombe <lacombar@gmail.com>,
	pefoley2@verizon.net, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT] kbuild fixes for 3.0
Date: Fri, 10 Jun 2011 22:45:40 +0200	[thread overview]
Message-ID: <4DF28274.3000708@suse.cz> (raw)
In-Reply-To: <BANLkTin+RBL9aYzWeTBZ2Fj_m+8WuA_Ckg@mail.gmail.com>

Dne 10.6.2011 17:22, Linus Torvalds napsal(a):
>  - if no such work-arounds can be done without excessive hackery, at
> least make sure that the packages in question know that they are
> broken, so that they get fixed and we can drop the third digit later
> even if we don't drop it at 3.0 itself.

So can we fix the kernel package now, even if the version has to stay at
3.0.0? The depmod hack is probably superfluous, but the rest are either
cleanups or fixes to make a future NUM.NUM release:

      kbuild: Fix KERNELVERSION for empty SUBLEVEL or PATCHLEVEL
      kbuild: Fix <linux/version.h> for empty SUBLEVEL or PATCHLEVEL
      kbuild: Move depmod call to a separate script
      perf: Use make kernelversion instead of parsing the Makefile

and this one is a genuine regression fix:

      kbuild: silence Nothing to be done for 'all' message

So would pull the branch if I revert "kbuild: Hack for depmod not
handling X.Y versions"?

thanks,
Michal

  reply	other threads:[~2011-06-10 20:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 21:42 [GIT] kbuild fixes for 3.0 Michal Marek
2011-06-10  0:10 ` Linus Torvalds
2011-06-10  3:14   ` Arnaud Lacombe
2011-06-10  3:37     ` Linus Torvalds
2011-06-10  3:41       ` Arnaud Lacombe
2011-06-10  3:45       ` Arnaud Lacombe
2011-06-10  3:57         ` Linus Torvalds
2011-06-10  5:16           ` Arnaud Lacombe
2011-06-10  5:53             ` Ray Lee
2011-06-10 10:03               ` maximilian attems
2011-06-10 15:22                 ` Linus Torvalds
2011-06-10 20:45                   ` Michal Marek [this message]
2011-06-10 20:56                     ` Linus Torvalds
2011-06-10 15:06               ` Andy Whitcroft
2011-06-10 15:26                 ` Milan Broz
2011-06-10 16:30             ` Arnaud Lacombe
2011-06-10 19:31               ` [lm-sensors] " Jean Delvare
2011-06-10 12:13           ` Michal Marek

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=4DF28274.3000708@suse.cz \
    --to=mmarek@suse.cz \
    --cc=lacombar@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max@stro.at \
    --cc=pefoley2@verizon.net \
    --cc=ray-lk@madrabbit.org \
    --cc=torvalds@linux-foundation.org \
    /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