All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@trained-monkey.org>
To: Kinga Tanska <kinga.tanska@intel.com>, linux-raid@vger.kernel.org
Cc: colyli@suse.de
Subject: Re: [PATCH v3 2/2] mdadm: replace container level checking with inline
Date: Wed, 24 Aug 2022 12:03:10 -0400	[thread overview]
Message-ID: <f16e1cc6-e373-13ef-1d3e-b3f3a00d0e80@trained-monkey.org> (raw)
In-Reply-To: <20220819005547.17343-3-kinga.tanska@intel.com>

On 8/18/22 20:55, Kinga Tanska wrote:
> To unify all containers checks in code, is_container() function is
> added and propagated.
> 
> Signed-off-by: Kinga Tanska <kinga.tanska@intel.com>
> ---
>  Assemble.c    |  5 ++---
>  Create.c      |  6 +++---
>  Grow.c        |  6 +++---
>  Incremental.c |  4 ++--
>  mdadm.h       | 14 ++++++++++++++
>  super-ddf.c   |  6 +++---
>  super-intel.c |  4 ++--
>  super0.c      |  2 +-
>  super1.c      |  2 +-
>  sysfs.c       |  2 +-
>  10 files changed, 32 insertions(+), 19 deletions(-)

This one fails to apply for me from patcheworks. That said, a minor nit
below.

Mind fixing this and posting an updated version?

Thanks,
Jes


> diff --git a/mdadm.h b/mdadm.h
> index c7268a71..72abfc50 100644
> --- a/mdadm.h
> +++ b/mdadm.h
> @@ -1885,3 +1885,17 @@ enum r0layout {
>   * This is true for native and DDF, IMSM allows 16.
>   */
>  #define MD_NAME_MAX 32
> +
> +/**
> + * is_container() - check if @level is &LEVEL_CONTAINER
> + * @level: level value
> + *
> + * return:
> + * 1 if level is equal to &LEVEL_CONTAINER, 0 otherwise.
> + */
> +static inline int is_container(const int level)
> +{
> +	if (level == LEVEL_CONTAINER)
> +		return 1;
> +	return 0;
> +}
> \ No newline at end of file

Please add the lost newline


  reply	other threads:[~2022-08-24 16:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19  0:55 [PATCH v3 0/2] Fix force assemblation Kinga Tanska
2022-08-19  0:55 ` [PATCH v3 1/2] Assemble: check if device is container before scheduling force-clean update Kinga Tanska
2022-08-24 16:01   ` Jes Sorensen
2022-08-19  0:55 ` [PATCH v3 2/2] mdadm: replace container level checking with inline Kinga Tanska
2022-08-24 16:03   ` Jes Sorensen [this message]
2022-08-24 16:44     ` Coly Li
  -- strict thread matches above, loose matches on Subject: below --
2022-08-18  7:20 [PATCH v3 0/2] Fix force addemblation Kinga Tanska
2022-08-18  7:20 ` [PATCH v3 2/2] mdadm: replace container level checking with inline Kinga Tanska
2022-07-05 11:58 [PATCH v3 0/2] Fix force assemblation Kinga Tanska
2022-07-05 11:58 ` [PATCH v3 2/2] mdadm: replace container level checking with inline Kinga Tanska

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=f16e1cc6-e373-13ef-1d3e-b3f3a00d0e80@trained-monkey.org \
    --to=jes@trained-monkey.org \
    --cc=colyli@suse.de \
    --cc=kinga.tanska@intel.com \
    --cc=linux-raid@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.