From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 27/34] gfs2: Drop __TIME__ usage
Date: Thu, 26 May 2011 09:43:54 +0100 [thread overview]
Message-ID: <1306399434.2893.2.camel@menhir> (raw)
In-Reply-To: <4DDD6B1F.1060303@suse.cz>
Hi,
On Wed, 2011-05-25 at 22:48 +0200, Michal Marek wrote:
> Dne 5.4.2011 16:59, Michal Marek napsal(a):
> > The kernel already prints its build timestamp during boot, no need to
> > repeat it in random drivers and produce different object files each
> > time.
> >
> > Cc: Steven Whitehouse <swhiteho@redhat.com>
> > Cc: cluster-devel at redhat.com
> > Signed-off-by: Michal Marek <mmarek@suse.cz>
> > ---
> > fs/gfs2/main.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
>
> Hi,
>
> I don't see this patch in today's linux-next. Any objection against me
> applying it to the kbuild-2.6.git repository?
>
> Thanks,
> Michal
>
No, I think that should be ok. It was added as a method to spot when
someone had compiled their own module against a distro kernel, but tbh
this isn't a problem in practice, so I don't think it will be a problem,
Steve.
prev parent reply other threads:[~2011-05-26 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1302015561-21047-1-git-send-email-mmarek@suse.cz>
[not found] ` <1302015561-21047-27-git-send-email-mmarek@suse.cz>
[not found] ` <4DDD6AD4.6040801@suse.cz>
2011-05-25 20:47 ` [Cluster-devel] [PATCH 26/34] dlm: Drop __TIME__ usage David Teigland
[not found] ` <1302015561-21047-28-git-send-email-mmarek@suse.cz>
[not found] ` <4DDD6B1F.1060303@suse.cz>
2011-05-26 8:43 ` Steven Whitehouse [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=1306399434.2893.2.camel@menhir \
--to=swhiteho@redhat.com \
/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).