public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Harvey Harrison <harvey.harrison@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] jbd/jbd2 NULL noise
Date: Fri, 28 Mar 2008 21:01:52 -0700	[thread overview]
Message-ID: <1206763312.6543.4.camel@brick> (raw)
In-Reply-To: <20080329035431.GL10722@ZenIV.linux.org.uk>

On Sat, 2008-03-29 at 03:54 +0000, Al Viro wrote:
> On Sat, Mar 29, 2008 at 03:42:28AM +0000, Al Viro wrote:
> 
> > > I did, it went into -mm and on Mar 5 it was taken into the subsystem
> > > tree.
> > 
> > Wait a minute...  where had it been taken?  What subsystem tree for "just
> > about all of fs/"?  
> 
> You've really got me curious.  The latest -mm I can find is 2.6.25-rc5-mm1,
> it's dated Mar 11 and the patches are very much there -
> broken-out/jbd-sparse-warnings-in-revokec-journalc.patch and
> broken-out/jbd2-sparse-warnings-in-revokec-journalc.patch
> resp., all by themselves and not as a part of any subsystem tree.
> 
> Linus, consider the patch upthread withdrawn.
> 
> Al, still morbidly curious about the akpm's scripts and aforementioned
> message...

Not sure which tree, but received this on Feb 27:


The patch titled
     jbd2: sparse warnings in revoke.c, journal.c
has been removed from the -mm tree.  Its filename was
     jbd2-sparse-warnings-in-revokec-journalc.patch

This patch was dropped because it was merged into mainline or a
subsystem tree

The current -mm tree may be found at
http://userweb.kernel.org/~akpm/mmotm/

------------------------------------------------------
Subject: jbd2: sparse warnings in revoke.c, journal.c
From: Harvey Harrison <harvey.harrison@gmail.com>

fs/jbd2/revoke.c:177:34: warning: Using plain integer as NULL pointer
fs/jbd2/revoke.c:183:33: warning: Using plain integer as NULL pointer
fs/jbd2/journal.c:222:2: warning: Using plain integer as NULL pointer
fs/jbd2/journal.c:222:2: warning: Using plain integer as NULL pointer
fs/jbd2/journal.c:234:3: warning: Using plain integer as NULL pointer
fs/jbd2/journal.c:234:3: warning: Using plain integer as NULL pointer
fs/jbd2/journal.c:1972:2: warning: Using plain integer as NULL pointer
fs/jbd2/journal.c:1979:33: warning: Using plain integer as NULL pointer
fs/jbd2/journal.c:2005:13: warning: Using plain integer as NULL pointer
fs/jbd2/journal.c:2012:17: warning: Using plain integer as NULL pointer

Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
Cc: <linux-ext4@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>


  reply	other threads:[~2008-03-29  4:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-29  3:07 [PATCH] jbd/jbd2 NULL noise Al Viro
2008-03-29  3:15 ` Harvey Harrison
2008-03-29  3:18   ` Al Viro
2008-03-29  3:26     ` Harvey Harrison
2008-03-29  3:42       ` Al Viro
2008-03-29  3:54         ` Al Viro
2008-03-29  4:01           ` Harvey Harrison [this message]
2008-03-29  4:56             ` Al Viro
2008-03-29  5:12               ` Harvey Harrison
2008-03-29  5:33               ` Andrew Morton
2008-03-29  5:25     ` Andrew Morton

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=1206763312.6543.4.camel@brick \
    --to=harvey.harrison@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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