public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Hannes Eder <hannes@hanneseder.net>
Cc: trivial@kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 11/16] fs/super.c: fix sparse warning: Using plain integer as NULL pointer
Date: Fri, 27 Feb 2009 01:28:37 +0000	[thread overview]
Message-ID: <20090227012837.GQ28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <154e089b0902261710ybebe696p2c87334b29bf08a0@mail.gmail.com>

On Fri, Feb 27, 2009 at 02:10:14AM +0100, Hannes Eder wrote:
> [Added To]
> 
> On Sun, Feb 22, 2009 at 1:05 AM, Hannes Eder <hannes@hanneseder.net> wrote:
> > Fix this sparse warning:
> > ?fs/super.c:849:26: warning: Using plain integer as NULL pointer

May I suggest a better subject for those?  Namely,

Subject: NULL noise: <filename or glob>

Nobody _cares_ which tool generates that and boilerplates in subjects should
be as short as possible.

  reply	other threads:[~2009-02-27  1:28 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22  0:00 [PATCH 00/16] fix sparse warnings: Using plain integer as NULL pointer Hannes Eder
2009-02-22  0:00 ` [PATCH 01/16] kexec/i386: " Hannes Eder
2009-02-27  0:48   ` Hannes Eder
2009-02-22  0:01 ` [PATCH 02/16] x86, numa_32.c: fix sparse warning: " Hannes Eder
2009-02-27  0:50   ` Hannes Eder
2009-02-22  0:01 ` [PATCH 03/16] drm: radeon: fix sparse warnings: " Hannes Eder
2009-02-27  0:53   ` Hannes Eder
2009-02-22  0:01 ` [PATCH 04/16] ide: " Hannes Eder
2009-02-27  0:58   ` Hannes Eder
2009-02-22  0:02 ` [PATCH 05/16] dvb: " Hannes Eder
2009-02-27  1:00   ` Hannes Eder
2009-02-22  0:02 ` [PATCH 06/16] MTD: tests: " Hannes Eder
2009-02-27  1:02   ` Hannes Eder
2009-02-27  5:07     ` Artem Bityutskiy
2009-02-22  0:02 ` [PATCH 07/16] panasonic-laptop: fix sparse warning: " Hannes Eder
2009-02-27  1:03   ` Hannes Eder
2009-02-22  0:02 ` [PATCH 08/16] [SCSI] FlashPoint: fix sparse warnings: " Hannes Eder
2009-02-22  0:11   ` [PATCH 08/16 v2] " Hannes Eder
2009-02-22  0:04 ` [PATCH 09/16] usb host: fix sparse warning: " Hannes Eder
2009-02-27  1:04   ` Hannes Eder
2009-02-22  0:04 ` [PATCH 10/16] viafb: " Hannes Eder
2009-02-27  1:07   ` Hannes Eder
2009-02-22  0:05 ` [PATCH 11/16] fs/super.c: " Hannes Eder
2009-02-27  1:10   ` Hannes Eder
2009-02-27  1:28     ` Al Viro [this message]
2009-03-02 21:34       ` [PATCH 11/16 v2] NULL noise: drivers/ide/ide-*.c Hannes Eder
2009-03-02 23:53         ` [PATCH 04/16 v3] " Hannes Eder
2009-03-05 13:47           ` Bartlomiej Zolnierkiewicz
2009-02-22  0:05 ` [PATCH 12/16] reiserfs: fix sparse warning: Using plain integer as NULL pointer Hannes Eder
2009-02-27  1:12   ` Hannes Eder
2009-02-22  0:05 ` [PATCH 13/16] kprobes: fix sparse warnings: " Hannes Eder
2009-02-27  1:13   ` Hannes Eder
2009-02-22  0:05 ` [PATCH 14/16] memcg: fix sparse warning: " Hannes Eder
2009-02-27  1:15   ` Hannes Eder
2009-02-27  1:37     ` KAMEZAWA Hiroyuki
2009-02-22  0:05 ` [PATCH 15/16] ipv6: " Hannes Eder
2009-02-22  7:37   ` David Miller
2009-02-22  0:05 ` [PATCH 16/16] ALSA: msnd: " Hannes Eder

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=20090227012837.GQ28946@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=hannes@hanneseder.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@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