From: Mark Brown <broonie@kernel.org>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: Matti Vaittinen <mazziesaccount@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] regulators: Add regulator_err2notif() helper
Date: Wed, 24 Nov 2021 12:54:28 +0000 [thread overview]
Message-ID: <YZ42BKFsbUgQDBiz@sirena.org.uk> (raw)
In-Reply-To: <eb1755ac0569ff07ffa466cf8912c6fd50e7c7c6.1637736436.git.matti.vaittinen@fi.rohmeurope.com>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
On Wed, Nov 24, 2021 at 09:16:45AM +0200, Matti Vaittinen wrote:
> Help drivers avoid storing both supported notification and supported error
> flags by supporting conversion from regulator error to notification.
> This may help saving some bytes.
Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-11-24 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 7:16 [PATCH v2 0/3] Provide event map helper for regulator drivers Matti Vaittinen
2021-11-24 7:16 ` [PATCH v2 1/3] regulators: Add regulator_err2notif() helper Matti Vaittinen
2021-11-24 12:54 ` Mark Brown [this message]
2021-11-24 7:17 ` [PATCH v2 2/3] regulators: irq_helper: Provide helper for trivial IRQ notifications Matti Vaittinen
2021-11-24 7:17 ` [PATCH v2 3/3] regulator: Drop unnecessary struct member Matti Vaittinen
2021-11-24 17:36 ` [PATCH v2 0/3] Provide event map helper for regulator drivers Mark Brown
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=YZ42BKFsbUgQDBiz@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®