linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramiro Oliveira <Ramiro.Oliveira@synopsys.com>
To: p.zabel@pengutronix.de, linux-kernel@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com, CARLOS.PALMINHA@synopsys.com,
	Ramiro Oliveira <Ramiro.Oliveira@synopsys.com>
Subject: [PATCH v4 0/2] reset: Make optional functions really optional.
Date: Fri, 13 Jan 2017 17:57:39 +0000	[thread overview]
Message-ID: <cover.1484307350.git.Ramiro.Oliveira@synopsys.com> (raw)

v4:
 - Change the way error handling was being processed when in optional mode.

v3:
 - Improve description of changes ocurring in the patchset
 - Add 2 new return errors.

v2:
 - Make some comments more explicit
 - Add optional flag to reduce code duplication
 - Change shared flag from int to bool to match optional flag 

Up until now optional functions in the reset API were similar to the non
optional.

This patch corrects that, while maintaining compatibility with existing
drivers.

As suggested here: https://lkml.org/lkml/2016/12/14/502

Ramiro Oliveira (2):
  reset: Change shared flag from int to bool
  reset: make optional functions really optional

 drivers/reset/core.c  | 53 +++++++++++++++++++++++++++++++++++++++------------
 include/linux/reset.h | 45 +++++++++++++++++++++++++------------------
 2 files changed, 67 insertions(+), 31 deletions(-)

-- 
2.11.0

             reply	other threads:[~2017-01-13 17:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13 17:57 Ramiro Oliveira [this message]
2017-01-13 17:57 ` [PATCH v4 1/2] reset: Change shared flag from int to bool Ramiro Oliveira
2017-01-13 17:57 ` [PATCH v4 2/2] reset: make optional functions really optional Ramiro Oliveira

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=cover.1484307350.git.Ramiro.Oliveira@synopsys.com \
    --to=ramiro.oliveira@synopsys.com \
    --cc=CARLOS.PALMINHA@synopsys.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.zabel@pengutronix.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 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).