From: Arjan van de Ven <arjan@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: netdev@vger.kernel.org
Subject: Re: tiacx - don't use UTS_RELEASE
Date: Tue, 04 Jul 2006 11:27:27 +0200 [thread overview]
Message-ID: <1152005247.3109.22.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060704022537.97f703b4.akpm@osdl.org>
On Tue, 2006-07-04 at 02:25 -0700, Andrew Morton wrote:
> On Tue, 04 Jul 2006 11:07:59 +0200
> Arjan van de Ven <arjan@infradead.org> wrote:
>
> > patch below removes the use of UTS_RELEASE from the tiacx driver; there
> > is absolutely no reason for a driver to print the kernel version or use
> > the UTS_RELEASE field; in addition this field changes all the time so
> > this causes spurious rebuilds..
>
> http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-04-usb/usb-storage-uname-in-pr-sc-unneeded-message.patch did it too.
>
> UTS_RELEASE doesn't change much. It's "2.6.17".
no but the header that it's in changes all the time iirc, at least it
used to (one of those kbuild regenerated files)
next prev parent reply other threads:[~2006-07-04 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 9:07 tiacx - don't use UTS_RELEASE Arjan van de Ven
2006-07-04 9:25 ` Andrew Morton
2006-07-04 9:27 ` Arjan van de Ven [this message]
2006-07-04 9:51 ` Sam Ravnborg
2006-07-04 10:00 ` Arjan van de Ven
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=1152005247.3109.22.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=netdev@vger.kernel.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