public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Phil Carmody <ext-phil.2.carmody@nokia.com>
Cc: trivial@kernel.org, linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH 3/7] xfs: there is no CONFIG_KDB_MODULES
Date: Mon, 4 Jul 2011 14:58:20 +1000	[thread overview]
Message-ID: <20110704045820.GE1026@dastard> (raw)
In-Reply-To: <1309643272-364-4-git-send-email-ext-phil.2.carmody@nokia.com>

On Sun, Jul 03, 2011 at 12:47:48AM +0300, Phil Carmody wrote:

Hi Phil,

You should probably cc the relevant lists with such patchsets so the
developers actually see the patches go by....

> Seems like there was a decade ago, but no longer, so this block
> is dead code. The list being returned disappeared back in commit
> ff57ab21995a8636cfc72efeebb09cc6034d756f.

When you quote a commit, short form followed by the name (i.e.
one-line form) is preferable because it gives context to the commit
without needing to go look it up in a git tree. Commit IDs are not
human readable, while commit log should be.

The commit in question - ff57ab2 ("xfs: convert xfsbud shrinker to a
per-buftarg shrinker.") - removed the list but the code being
removed was already long dead. FWIW, I know just by reading the
commit description when the list went away and who was responsible
for missing that. i.e. me. ;)

> Part of a shotgun patchset; found by greps, seds, and diffs
> rather than actual understanding.

Not necessary in a commit description - the zero patch of a series,
yes, to describe how the issues were found, but it doesn't need to
be recorded forever in the commit log. ;)

> Signed-off-by: Phil Carmody <ext-phil.2.carmody@nokia.com>
> ---
>  fs/xfs/linux-2.6/xfs_buf.c |    8 --------
>  fs/xfs/linux-2.6/xfs_buf.h |    4 ----
>  2 files changed, 0 insertions(+), 12 deletions(-)
> 
> diff --git a/fs/xfs/linux-2.6/xfs_buf.c b/fs/xfs/linux-2.6/xfs_buf.c
> index 5e68099..5bccae0 100644
> --- a/fs/xfs/linux-2.6/xfs_buf.c
> +++ b/fs/xfs/linux-2.6/xfs_buf.c
> @@ -1889,11 +1889,3 @@ xfs_buf_terminate(void)
>  	destroy_workqueue(xfslogd_workqueue);
>  	kmem_zone_destroy(xfs_buf_zone);
>  }
> -
> -#ifdef CONFIG_KDB_MODULES
> -struct list_head *
> -xfs_get_buftarg_list(void)
> -{
> -	return &xfs_buftarg_list;
> -}
> -#endif
> diff --git a/fs/xfs/linux-2.6/xfs_buf.h b/fs/xfs/linux-2.6/xfs_buf.h
> index 50a7d5f..6881321 100644
> --- a/fs/xfs/linux-2.6/xfs_buf.h
> +++ b/fs/xfs/linux-2.6/xfs_buf.h
> @@ -339,10 +339,6 @@ extern void xfs_wait_buftarg(xfs_buftarg_t *);
>  extern int xfs_setsize_buftarg(xfs_buftarg_t *, unsigned int, unsigned int);
>  extern int xfs_flush_buftarg(xfs_buftarg_t *, int);
>  
> -#ifdef CONFIG_KDB_MODULES
> -extern struct list_head *xfs_get_buftarg_list(void);
> -#endif
> -
>  #define xfs_getsize_buftarg(buftarg)	block_size((buftarg)->bt_bdev)
>  #define xfs_readonly_buftarg(buftarg)	bdev_read_only((buftarg)->bt_bdev)

Code changes look good. Can you fix the commit description and
resend to xfs@oss.sgi.com?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  parent reply	other threads:[~2011-07-04  4:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-02 21:47 [PATCH 0/7] [TRIVIAL] Cleanup spurious CONFIGs Phil Carmody
2011-07-02 21:47 ` [PATCH 1/7] mn10300: there is no CONFIG_CALIBRATE_DELAY Phil Carmody
2011-07-02 21:47   ` [PATCH 2/7] cris: there is no CONFIG_ETRAX_KGB_PORT2 Phil Carmody
2011-07-02 21:47     ` [PATCH 3/7] xfs: there is no CONFIG_KDB_MODULES Phil Carmody
2011-07-02 21:47       ` [PATCH 4/7] ppc: there is no CONFIG_PPC47x Phil Carmody
2011-07-02 21:47         ` [PATCH 5/7] ppc: there is no CONFIG_PPC_CPU Phil Carmody
2011-07-02 21:47           ` [PATCH 6/7] nommu: there is no CONFIG_SMALL_TASKS Phil Carmody
2011-07-02 21:47             ` [PATCH 7/7] xtensa: there is no CONFIG_UNALIGNED_USER Phil Carmody
2011-07-04  4:58       ` Dave Chinner [this message]
2011-07-04  8:51         ` [PATCH 3/7] xfs: there is no CONFIG_KDB_MODULES Phil Carmody
2011-07-04 13:15           ` Lukasz

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=20110704045820.GE1026@dastard \
    --to=david@fromorbit.com \
    --cc=ext-phil.2.carmody@nokia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@kernel.org \
    --cc=xfs@oss.sgi.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