From: Luis Henriques <henrix@sapo.pt>
To: Gregory Haskins <ghaskins@novell.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2 -tip] sched: Clean unused fields from struct rq
Date: Wed, 18 Mar 2009 20:08:29 +0000 [thread overview]
Message-ID: <20090318200829.GA4157@hades.domain.com> (raw)
In-Reply-To: <49C04F5F.1020700@novell.com>
On Tue, Mar 17, 2009 at 09:33:19PM -0400, Gregory Haskins wrote:
> >> I think this bit is ABI, so you either have to bump the version number
> >> or emit 0s, iirc gregory touched some of that last -- or at least wrote
> >> userspace for it..
> >>
> >
> > Hmm... you're right. I should have though about that. Anyway, what is the
> > the best approach here?
> >
> > I know that changes in ABI shall not break anything, but just increasing the
> > version number will really solve the issue? Will userspace care for this?
> > On the other hand, just writting 0s does not sound interesting either...
> >
> >
> Hi Luis,
> My app does check the version number, so bumping it is probably the
> best solution. Be sure to keep me in the loop about whether this patch
> gets merged and I will be sure to update it to handle the new version.
Hi Greg,
(sorry for the _huge_ delay for replying, but my timeslice for lkml is quite
small...)
I'll quickly prepare another patch that also modifies the version and repost it.
Maybe you can then give me more feedback on it.
Thanks for comments.
--
Luis Henriques
next prev parent reply other threads:[~2009-03-18 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 0:03 [PATCH 1/2 -tip] sched: Clean unused fields from struct rq Luis Henriques
2009-03-18 0:09 ` Peter Zijlstra
2009-03-18 0:23 ` Luis Henriques
2009-03-18 1:33 ` Gregory Haskins
2009-03-18 8:51 ` Peter Zijlstra
2009-03-18 20:08 ` Luis Henriques [this message]
2009-03-18 8:50 ` Peter Zijlstra
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=20090318200829.GA4157@hades.domain.com \
--to=henrix@sapo.pt \
--cc=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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.