mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [GIT PATCHES] kbuild updates
Date: Mon, 5 Sep 2005 22:32:04 +0100	[thread overview]
Message-ID: <200509052232.04135.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <20050905201345.GA26106@mars.ravnborg.org>

On Monday 05 September 2005 21:13, Sam Ravnborg wrote:
> On Mon, Sep 05, 2005 at 08:35:14PM +0100, Alistair John Strachan wrote:
> > On Monday 05 September 2005 18:41, Sam Ravnborg wrote:
> > > Hi Linus.
> > >
> > > kbuild updates as accumulated over the last few months.
> > > All patches has been in -mm in one or several versions.
> > >
> > > Most noteworthy:
> > > 1) -Wundef added to CFLAGS. This is the cause of several new warnings,
> > >    which for the most part has been fixed for now.
> > > 2) "PREEMPT" in UTS_VERSION. So we complain when dealing
> > >    with modules compiled for a wrong kernel
> >
> > How is this different from the preempt module vermagic?
> >
> > ~$ modinfo agpgart | grep vermagic
> > vermagic:       2.6.13 preempt gcc-4.0
>
> My bad. Adding PREEMT to UTS_VERSION makes it visible in uname -a.
>

I see. I can understand adding an extraversion for SMP and experimental 
patches (like Ingo's RT work), but why is it useful to differentiate (by 
name) between preempt and non-preempt kernels? Do distributors wish to 
package both in parallel?

-- 
Cheers,
Alistair.

'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

  reply	other threads:[~2005-09-05 21:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-05 17:41 Sam Ravnborg
2005-09-05 19:35 ` Alistair John Strachan
2005-09-05 20:13   ` Sam Ravnborg
2005-09-05 21:32     ` Alistair John Strachan [this message]
2005-09-06  1:28       ` Sam Ravnborg
2005-09-06  1:38       ` Matt Mackall
2006-01-06 21:03 Sam Ravnborg
2006-01-09 21:11 Sam Ravnborg
2006-01-10 16:27 ` Linus Torvalds
2006-06-24 22:22 Sam Ravnborg

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=200509052232.04135.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®