Messages in this thread | | | From | Dan Streetman <> | Date | Wed, 10 Jun 2015 21:01:42 -0400 | Subject | Re: [RFC][PATCH 4/5] mm/zpool: allow NULL `zpool' pointer in zpool_destroy_pool() |
| |
On Wed, Jun 10, 2015 at 8:59 PM, Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> wrote: > On (06/10/15 17:48), Joe Perches wrote: > [..] >> > > > For consistency, tweak zpool_destroy_pool() and NULL-check the >> > > > pointer there. >> > > > >> > > > Proposed by Andrew Morton. >> > > > >> > > > Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com> >> > > > Reported-by: Andrew Morton <akpm@linux-foundation.org> >> > > > LKML-reference: https://lkml.org/lkml/2015/6/8/583 >> > > >> > > Acked-by: Dan Streetman <ddstreet@ieee.org> >> > >> > Thanks. >> > >> > Shall we ask Joe to add zpool_destroy_pool() to the >> > "$func(NULL) is safe and this check is probably not required" list? >> >> [] >> >> Is it really worth it? >> >> There isn't any use of zpool_destroy_pool preceded by an if >> There is one and only one use of zpool_destroy_pool. >> > > Yes, that's why I asked. I don't think that zpool_destroy_pool() > will gain any significant amount of users soon (well, who knows), > so I'm fine with keeping it out of checkpatch checks. Just checked > your opinion.
I really doubt if zpool will be used by anyone other than zswap anytime soon.
> > -ss
| |