From: Sam Ravnborg <sam@ravnborg.org>
To: Josh Hunt <josh@scalex86.org>
Cc: linux-kernel@vger.kernel.org, kiran@scalex86.org, mingo@elte.hu,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCHv2] Fix 'make rpm' when CONFIG_LOCALVERSION_AUTO=y and using SCM tree
Date: Sat, 7 Mar 2009 13:29:13 +0100 [thread overview]
Message-ID: <20090307122913.GA5484@uranus.ravnborg.org> (raw)
In-Reply-To: <20090220074531.GF8151@localhost.localdomain>
On Thu, Feb 19, 2009 at 11:45:31PM -0800, Josh Hunt wrote:
> Updated patch with Sam's fixes as per this discussion:
> http://lkml.org/lkml/2009/2/15/18
>
> Running 'make rpm' fails when CONFIG_LOCALVERSION_AUTO=y and using a kernel
> source tree under SCM. This is due to KERNELRELEASE being different when the
> initial make is run and when make is run from rpmbuild.
...
Hand applied - your patches continue to be wordwrapped.
Please see if you can fix this next time.
Thanks,
Sam
prev parent reply other threads:[~2009-03-07 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 7:45 [PATCHv2] Fix 'make rpm' when CONFIG_LOCALVERSION_AUTO=y and using SCM tree Josh Hunt
2009-02-20 12:07 ` Sam Ravnborg
2009-03-07 12:29 ` Sam Ravnborg [this message]
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=20090307122913.GA5484@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=josh@scalex86.org \
--cc=kiran@scalex86.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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