From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Chris Brandt <chris.brandt@renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Jacopo Mondi <jacopo@jmondi.org>
Subject: Re: [PATCH v2] pinctrl: rza1: reduce printed messages
Date: Fri, 20 Dec 2019 15:50:29 +0100 [thread overview]
Message-ID: <CAMuHMdUTyhKSt6qEhnkgKZpn5KizUDLe8zztY5cy0ZSxCSj+Mw@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdYOXvWpAs1LkgeQFxZiU=HvnaUod=px+42qpJBrcKGCfw@mail.gmail.com>
Hi Linus,
On Mon, Dec 16, 2019 at 10:41 AM Linus Walleij <linus.walleij@linaro.org> wrote:
> On Thu, Dec 12, 2019 at 2:53 PM Chris Brandt <chris.brandt@renesas.com> wrote:
> > Since this message is printed for each port, it creates a lot of output
> > during boot and would serve better only during debugging.
> >
> > Signed-off-by: Chris Brandt <chris.brandt@renesas.com>
> > Acked-by: Jacopo Mondi <jacopo@jmondi.org>
>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>
> I think Geert usually pick these up as well, else tell me if I should
> just apply it.
Indeed.
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
and queueing in sh-pfc-for-v5.6.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2019-12-20 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 13:53 [PATCH v2] pinctrl: rza1: reduce printed messages Chris Brandt
2019-12-16 9:41 ` Linus Walleij
2019-12-20 14:50 ` Geert Uytterhoeven [this message]
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=CAMuHMdUTyhKSt6qEhnkgKZpn5KizUDLe8zztY5cy0ZSxCSj+Mw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=chris.brandt@renesas.com \
--cc=geert+renesas@glider.be \
--cc=jacopo@jmondi.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).