mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Josh Triplett <josht@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Pass sparse the lock expression given to lock annotations
Date: Fri, 25 Aug 2006 10:46:32 -0700	[thread overview]
Message-ID: <20060825104632.df1fd26b.akpm@osdl.org> (raw)
In-Reply-To: <1156521234.3420.19.camel@josh-work.beaverton.ibm.com>

On Fri, 25 Aug 2006 08:53:53 -0700
Josh Triplett <josht@us.ibm.com> wrote:

> On Thu, 2006-08-24 at 21:05 -0700, Andrew Morton wrote:
> > On Thu, 24 Aug 2006 17:48:56 -0700
> > Josh Triplett <josht@us.ibm.com> wrote:
> > 
> > > The lock annotation macros __acquires, __releases, __acquire, and __release
> > > all currently throw the lock expression passed as an argument.  Now that
> > > sparse can parse __context__ and __attribute__((context)) with a context
> > > expression, pass the lock expression down to sparse as the context expression.
> > 
> > What is the dependency relationship between your kernel changes and your
> > proposed change to sparse?
> 
> Sparse with my multi-context patch will continue to parse versions of
> the kernel without this kernel patch, since I made the context
> expression optional in sparse.  Versions of sparse without my
> multi-context patch will not parse kernels with this kernel patch (since
> previous versions of sparse will not support the extra argument).

OK.  Is this patch the only one which will break current sparse versions? 
If not, please identify the others.

I'll keep the non-back-compatible kernel patches in -mm until you've
informed me that a suitable version of sparse has been released.  Then we
can include that sparse version number in the kernel changelogs so things
are nice and organised.


  reply	other threads:[~2006-08-25 17:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-25  0:48 Josh Triplett
2006-08-25  4:05 ` Andrew Morton
2006-08-25 15:53   ` Josh Triplett
2006-08-25 17:46     ` Andrew Morton [this message]
2006-08-25 18:21       ` Josh Triplett
2006-08-31 17:49         ` [PATCH v2] " Josh Triplett

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=20060825104632.df1fd26b.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=josht@us.ibm.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®