From: Mark Brown <broonie@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH 2/3] regmap: don't create the debugfs entries if locking is disabled
Date: Wed, 13 Dec 2017 16:00:18 +0000 [thread overview]
Message-ID: <20171213160018.GM6416@sirena.org.uk> (raw)
In-Reply-To: <CAMRc=MdyF3axnh60VYnjrTJDvWH2Jx12=-m2FnnxaAPmp7sf=w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 557 bytes --]
On Wed, Dec 13, 2017 at 04:46:10PM +0100, Bartosz Golaszewski wrote:
> 2017-12-13 16:39 GMT+01:00 Mark Brown <broonie@kernel.org>:
> > I (probably unsurprisingly) prefer my version that I posted yesterday as
> > it gives us the trivial memory saving of not having the flag if debugfs
> > is disabled but more importantly from my point of view keeps the
> > interface to debugfs as function calls in the core.
> It went into spam in my mailbox for some reason, that's why I didn't see it.
> Yes, it looks better. I'll drop it from the series.
OK, great.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-12-13 16:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 9:28 [PATCH 0/3] regmap: follow-up for ("regmap: allow to disable all locking mechanisms") Bartosz Golaszewski
2017-12-13 9:28 ` [PATCH 1/3] regmap: rename regmap_lock_unlock_empty() to regmap_lock_unlock_none() Bartosz Golaszewski
2017-12-13 9:28 ` [PATCH 2/3] regmap: don't create the debugfs entries if locking is disabled Bartosz Golaszewski
2017-12-13 14:54 ` Andy Shevchenko
2017-12-13 14:59 ` Bartosz Golaszewski
2017-12-13 15:39 ` Mark Brown
2017-12-13 15:46 ` Bartosz Golaszewski
2017-12-13 16:00 ` Mark Brown [this message]
2017-12-13 9:28 ` [PATCH 3/3] regmap: duplicate the name string stored in regmap Bartosz Golaszewski
2017-12-13 9:32 ` Lars-Peter Clausen
2017-12-13 9:56 ` Bartosz Golaszewski
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=20171213160018.GM6416@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=brgl@bgdev.pl \
--cc=gregkh@linuxfoundation.org \
--cc=lars@metafoo.de \
--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 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®