From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jean Delvare <jdelvare@suse.de>
Cc: stable@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [BACKPORT] nvmem: Use the same permissions for eeprom as for nvmem
Date: Tue, 17 Sep 2019 20:10:18 +0200 [thread overview]
Message-ID: <20190917181018.GC1570310@kroah.com> (raw)
In-Reply-To: <20190917163001.5c775b61@endymion>
On Tue, Sep 17, 2019 at 04:30:01PM +0200, Jean Delvare wrote:
> [ Upstream commit e70d8b287301eb6d7c7761c6171c56af62110ea3 ]
>
> The compatibility "eeprom" attribute is currently root-only no
> matter what the configuration says. The "nvmem" attribute does
> respect the setting of the root_only configuration bit, so do the
> same for "eeprom".
>
> Signed-off-by: Jean Delvare <jdelvare@suse.de>
> Fixes: b6c217ab9be6 ("nvmem: Add backwards compatibility support for older EEPROM drivers.")
> Reviewed-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> Cc: Andrew Lunn <andrew@lunn.ch>
> Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Link: https://lore.kernel.org/r/20190728184255.563332e6@endymion
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
> This is the backport of commit e70d8b287301 "nvmem: Use the same
> permissions for eeprom as for nvmem" for stable kernel branches 4.19,
> 4.14 and 4.9. Thanks.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2019-09-17 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 14:30 [BACKPORT] nvmem: Use the same permissions for eeprom as for nvmem Jean Delvare
2019-09-17 18:10 ` Greg Kroah-Hartman [this message]
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=20190917181018.GC1570310@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bgolaszewski@baylibre.com \
--cc=jdelvare@suse.de \
--cc=sashal@kernel.org \
--cc=stable@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