From: Wolfram Sang <wsa@the-dreams.de>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-i2c@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [GIT PULL] at24: updates for v5.6
Date: Wed, 29 Jan 2020 21:58:55 +0100 [thread overview]
Message-ID: <20200129205855.GC7586@ninjato> (raw)
In-Reply-To: <20200124164644.20020-1-brgl@bgdev.pl>
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
On Fri, Jan 24, 2020 at 05:46:44PM +0100, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>
> Hi Wolfram,
>
> I'm sorry for the late PR. I was (still am actually) OoO for family
> reasons. I hope you can still pull this for the next merge window.
Yes, it will work. Enjoy your OoO!
>
> This time the release is pretty big for this driver. We have moved the
> support for write-protect pin control into the core nvmem library so that
> all nvmem users can use it automatically. All nvmem changes were acked by
> Srinivas and have been in next for some time. The DT binding document for
> at25 was updated and the patch was acked by Greg KH. The driver also now
> supports regulator control and has suspend/resume callbacks.
>
> Best regards,
> Bartosz
>
> The following changes since commit e42617b825f8073569da76dc4510bfa019b1c35a:
>
> Linux 5.5-rc1 (2019-12-08 14:57:55 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git at24-updates-for-v5.6
>
> for you to fetch changes up to cd5676db0574cc1c0b234bc3b17565b07290aa72:
>
> misc: eeprom: at24: support pm_runtime control (2020-01-23 12:52:57 +0100)
>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-01-29 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 16:46 [GIT PULL] at24: updates for v5.6 Bartosz Golaszewski
2020-01-29 20:58 ` Wolfram Sang [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=20200129205855.GC7586@ninjato \
--to=wsa@the-dreams.de \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=linux-i2c@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