From: "John W. Linville" <linville@tuxdriver.com>
To: Michal Marek <mmarek@suse.cz>
Cc: reinette chatre <reinette.chatre@intel.com>,
Sam Ravnborg <sam@ravnborg.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: net/kbuild trees build failure
Date: Mon, 7 Dec 2009 17:28:53 -0500 [thread overview]
Message-ID: <20091207222853.GE18939@tuxdriver.com> (raw)
In-Reply-To: <4B1D76B1.6070601@suse.cz>
On Mon, Dec 07, 2009 at 10:42:09PM +0100, Michal Marek wrote:
> reinette chatre napsal(a):
> > Right - could we please use the solution that works at compile time? I
> > used UTS_RELEASE after learning about its use in init/version.c, would
> > that not make it an approved solution?
>
> It seems there is some misunderstanding.
Alright, if Stephen's fix is acceptable then your suggestion is fine.
Sam seemed to suggest that Stephen's fix was a stop-gap.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-12-07 22:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 9:03 linux-next: net/kbuild trees build failure Stephen Rothwell
2009-12-07 11:41 ` Sam Ravnborg
2009-12-07 12:22 ` Michal Marek
2009-12-07 16:09 ` John W. Linville
2009-12-07 18:12 ` reinette chatre
2009-12-07 21:42 ` Michal Marek
2009-12-07 22:04 ` reinette chatre
2009-12-07 22:28 ` John W. Linville [this message]
2009-12-08 5:38 ` Sam Ravnborg
2009-12-08 14:54 ` John W. Linville
2009-12-08 23:11 ` Stephen Rothwell
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=20091207222853.GE18939@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=sam@ravnborg.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).