All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matheus Castello <matheus@castello.eng.br>
To: linus.walleij@linaro.org
Cc: linux-kernel@vger.kernel.org, Matheus Castello <matheus@castello.eng.br>
Subject: [PATCH v1 0/2] pinctrl: generic: improve apply_setting error verbosity
Date: Tue,  1 May 2018 03:40:35 -0400	[thread overview]
Message-ID: <1525160437-5222-1-git-send-email-matheus@castello.eng.br> (raw)

This series is for improve verbosity in debug for error cases using pinconf 
generic API. Legacy pinctrl-vendor drivers prints error messages with more 
verbosity when parse invalid or not supported sub-nodes properties. In this 
series we try to show messages with more information about the pinctrl-vendor 
driver and sub-nodes that returned error when applied.

Let me know your opinion about this.

Matheus Castello (2):
  pinctrl: generic: add API to solve generic sub-node property name
  pinctrl: generic: improve apply_setting error verbosity

 drivers/pinctrl/pinconf-generic.c       | 61 +++++++++++++++++----------------
 drivers/pinctrl/pinconf.c               | 15 +++++++-
 include/linux/pinctrl/pinconf-generic.h | 32 +++++++++++++++++
 3 files changed, 77 insertions(+), 31 deletions(-)

-- 
2.7.4

             reply	other threads:[~2018-05-01  8:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01  7:40 Matheus Castello [this message]
2018-05-01  7:40 ` [PATCH v1 1/2] pinctrl: generic: add API to solve generic sub-node property name Matheus Castello
2018-05-01  7:40 ` [PATCH v1 2/2] pinctrl: generic: improve apply_setting error verbosity Matheus Castello
2018-05-01  8:34   ` kbuild test robot
2018-05-01 10:05   ` kbuild test robot
2018-05-01 19:09     ` [PATCH v2 0/2] " Matheus Castello
2018-05-01 19:10       ` [PATCH v2 1/2] pinctrl: generic: add API to solve generic sub-node property name Matheus Castello
2018-05-02 12:56         ` Linus Walleij
2018-05-01 19:10       ` [PATCH v2 2/2] pinctrl: generic: improve apply_setting error verbosity Matheus Castello
2018-05-02 12:51         ` Linus Walleij
2018-05-08  5:27           ` Matheus Castello

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=1525160437-5222-1-git-send-email-matheus@castello.eng.br \
    --to=matheus@castello.eng.br \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@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.