From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Khouloud Touil <ktouil@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
baylibre-upstreaming@groups.io,
LKML <linux-kernel@vger.kernel.org>,
linux-devicetree <devicetree@vger.kernel.org>,
linux-i2c <linux-i2c@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v2 0/4] at24: move write-protect pin handling to nvmem core
Date: Thu, 19 Dec 2019 11:59:29 +0100 [thread overview]
Message-ID: <CAMRc=Mc+OCJTMOx2qXT74RBma6iVTsuwjc_g3SbmHDKxvtfOWA@mail.gmail.com> (raw)
In-Reply-To: <b56813c2-d29e-c461-ca1d-80a131c9341a@linaro.org>
czw., 19 gru 2019 o 11:56 Srinivas Kandagatla
<srinivas.kandagatla@linaro.org> napisał(a):
> >>
> >> Thanks Khouloud for this patchset,
> >>
> >> I can take this via nvmem tree once we get an ack on dt bindings from DT
> >> maintainers.
> >>
> >
> > Hi Srinivas,
> >
> > this will conflict with my at24 tree for this release - can you put
> > those patches (once they're fine) into an immutable branch for me to
> > merge in?
>
> I can ack nvmem core patch so that you can take it directly via at24
> tree if thats okay.
>
Sure, even better!
Bart
prev parent reply other threads:[~2019-12-19 10:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 15:41 [PATCH v2 0/4] at24: move write-protect pin handling to nvmem core Khouloud Touil
2019-12-10 15:41 ` [PATCH v2 1/4] dt-bindings: nvmem: new optional property write-protect-gpios Khouloud Touil
2019-12-16 8:08 ` Linus Walleij
2019-12-18 11:10 ` Khouloud Touil
2019-12-10 15:41 ` [PATCH v2 2/4] nvmem: add support for the write-protect pin Khouloud Touil
2019-12-16 8:09 ` Linus Walleij
2019-12-19 10:58 ` Srinivas Kandagatla
2019-12-10 15:41 ` [PATCH v2 3/4] dt-bindings: at24: remove the optional property write-protect-gpios Khouloud Touil
2019-12-16 8:11 ` Linus Walleij
2019-12-10 15:41 ` [PATCH v2 4/4] eeprom: at24: remove the write-protect pin support Khouloud Touil
2019-12-16 8:13 ` Linus Walleij
2019-12-16 11:03 ` Bartosz Golaszewski
2019-12-19 10:51 ` [PATCH v2 0/4] at24: move write-protect pin handling to nvmem core Srinivas Kandagatla
2019-12-19 10:53 ` Bartosz Golaszewski
2019-12-19 10:56 ` Srinivas Kandagatla
2019-12-19 10:59 ` Bartosz Golaszewski [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='CAMRc=Mc+OCJTMOx2qXT74RBma6iVTsuwjc_g3SbmHDKxvtfOWA@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=baylibre-upstreaming@groups.io \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=ktouil@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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;
as well as URLs for NNTP newsgroup(s).