All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 1/3] ubifs: Reintroduce using CONFIG_UBIFS_SILENCE_MSG
Date: Sun, 18 Mar 2018 19:33:22 +0100	[thread overview]
Message-ID: <20180318183322.GA13800@x230> (raw)

Hi,

> Use of CONFIG_UBIFS_SILENCE_MSG was added in
> 147162dac6 ("ubi: ubifs: Turn off verbose prints")
>
> Then it was removed in
> ff94bc40af ("mtd, ubi, ubifs: resync with Linux-3.14")
>
> Cc: Joe Hershberger <joe.hershberger@ni.com>
> Cc: Heiko Schocher <hs@denx.de>
> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> ---
> Note, not sure whether we need to keep this workaround.  If not, it
> might be better to get rid of both CONFIG_UBI_SILENCE_MSG and
> CONFIG_UBIFS_SILENCE_MSG.
>
> Petr
> ---
>  fs/ubifs/ubifs.h | 4 ++++
>  1 file changed, 4 insertions(+)
>
> diff --git a/fs/ubifs/ubifs.h b/fs/ubifs/ubifs.h
> index 1d89465205..b4ce706a8e 100644
> --- a/fs/ubifs/ubifs.h
> +++ b/fs/ubifs/ubifs.h
> @@ -618,9 +618,13 @@ static inline ino_t parent_ino(struct dentry *dentry)
>  #define UBIFS_VERSION 1
>
>  /* Normal UBIFS messages */
> +#ifdef CONFIG_UBIFS_SILENCE_MSG
> +#define ubifs_msg(c, fmt, ...)
> +#else
>  #define ubifs_msg(c, fmt, ...)                                      \
>         pr_notice("UBIFS (ubi%d:%d): " fmt "\n",                    \
>                   (c)->vi.ubi_num, (c)->vi.vol_id, ##__VA_ARGS__)
> +#endif
>  /* UBIFS error messages */
>  #ifndef __UBOOT__
>  #define ubifs_err(c, fmt, ...)

ping, please.


Kind regards,
Petr

             reply	other threads:[~2018-03-18 18:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-18 18:33 Petr Vorel [this message]
     [not found] <20180318183002.GA10587@x230>
     [not found] ` <53f7c980-8314-2499-8265-05bf7359eeb7@denx.de>
2018-03-19 10:22   ` [U-Boot] [U-Boot, 1/3] ubifs: Reintroduce using CONFIG_UBIFS_SILENCE_MSG Petr Vorel

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=20180318183322.GA13800@x230 \
    --to=petr.vorel@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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.