From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: what is the "+" sigh in the modules folder name?
Date: Mon, 23 Jan 2012 10:15:27 -0800 [thread overview]
Message-ID: <20120123181527.GA27664@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1201231237500.26817@oneiric>
On Mon, Jan 23, 2012 at 12:40:41PM -0500, Robert P. J. Day wrote:
> On Mon, 23 Jan 2012, Greg KH wrote:
>
> > On Tue, Jan 24, 2012 at 12:25:20AM +0700, Mulyadi Santosa wrote:
> > > Hi...
> > >
> > > On Mon, Jan 23, 2012 at 23:15, Christopher Harvey
> > > <chris@basementcode.com> wrote:
> > > > I have a path on system called:
> > > > '/lib/modules/2.6.37+/'
> > > > It used to be called:
> > > > '/lib/modules/2.6.37/'
> > >
> > > Hm strange. You said you have the kernel source, right? Can you show
> > > us about ten top lines of the Makefile in the main kernel source
> > > directory?
> > >
> > > I am suspecting there is "+" character in the extraversion..but that
> > > needs to be checked....
> >
> > No, it just means you have a "modified" kernel tree, that is not reall
> > 2.6.37, you have changed it somehow. The build system asks git about
> > this when building the kernel.
>
> you sure? i thought that if it was a modified working tree, you'd
> get the "-dirty" qualifier added, not just a "+".
Try it and see :)
next prev parent reply other threads:[~2012-01-23 18:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 16:15 what is the "+" sigh in the modules folder name? Christopher Harvey
2012-01-23 17:25 ` Mulyadi Santosa
2012-01-23 17:34 ` Greg KH
2012-01-23 17:40 ` Robert P. J. Day
2012-01-23 18:15 ` Greg KH [this message]
2012-01-23 19:52 ` Graeme Russ
2012-01-23 19:58 ` Robert P. J. Day
2012-01-23 21:30 ` Javier Martinez Canillas
2012-01-23 21:46 ` Graeme Russ
2012-01-23 21:53 ` Robert P. J. Day
2012-01-23 21:55 ` Graeme Russ
2012-01-24 15:16 ` Christopher Harvey
2012-01-24 16:27 ` Anand Moon
2012-01-23 17:36 ` Robert P. J. Day
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=20120123181527.GA27664@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.