From: Mark Brown <broonie@kernel.org>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@01.org, mazziesaccount@gmail.com,
heikki.haikola@fi.rohmeurope.com,
mikko.mutanen@fi.rohmeurope.com, gregkh@linuxfoundation.org,
rafael@kernel.org, linus.walleij@linaro.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
vladimir_zapolskiy@mentor.com
Subject: Re: [PATCH v3] regmap: regmap-irq/gpio-max77620: add level-irq support
Date: Wed, 19 Dec 2018 17:52:31 +0000 [thread overview]
Message-ID: <20181219175231.GL8130@sirena.org.uk> (raw)
In-Reply-To: <20181219064842.GG2477@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On Wed, Dec 19, 2018 at 08:48:42AM +0200, Matti Vaittinen wrote:
> I forgot that the block of code the commit "regmap: regmap-irq: Remove
> default irq type setting from core" removes do use the old type specifiers
> whcih this patch changes. So even though this patch applies cleanly on tree
> which does not include "regmap: regmap-irq: Remove default irq type setting
> from core" - it does not mean there is no dependency. This was my brain fart.
> There is dependency. "regmap: regmap-irq: Remove default irq type setting
> from core" should be applied prior this patch.
> Should I combine these two patches as a series (and resend them) or what is
> the correct way to note the dependency?
It's fine as-is.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-12-19 17:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 11:59 [PATCH v3] regmap: regmap-irq/gpio-max77620: add level-irq support Matti Vaittinen
2018-12-18 15:36 ` kbuild test robot
2018-12-18 15:36 ` kbuild test robot
2018-12-19 6:48 ` Matti Vaittinen
2018-12-19 17:52 ` Mark Brown [this message]
2018-12-26 11:39 ` Geert Uytterhoeven
2018-12-27 7:35 ` Matti Vaittinen
2018-12-27 7:56 ` Matti Vaittinen
2018-12-28 8:05 ` Matti Vaittinen
2018-12-31 19:11 ` Mark Brown
2019-01-02 7:42 ` Matti Vaittinen
2019-01-03 17:20 ` Charles Keepax
2019-01-03 17:20 ` Charles Keepax
2019-01-04 8:02 ` Matti Vaittinen
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=20181219175231.GL8130@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.haikola@fi.rohmeurope.com \
--cc=kbuild-all@01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--cc=mikko.mutanen@fi.rohmeurope.com \
--cc=rafael@kernel.org \
--cc=vladimir_zapolskiy@mentor.com \
/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.