From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Khouloud Touil <ktouil@baylibre.com>,
baylibre-upstreaming@groups.io,
LKML <linux-kernel@vger.kernel.org>,
Rob Herring <robh@kernel.org>,
linux-devicetree <devicetree@vger.kernel.org>,
linux-i2c <linux-i2c@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v4 4/5] dt-bindings: at25: add reference for the wp-gpios property
Date: Tue, 14 Jan 2020 16:05:57 +0100 [thread overview]
Message-ID: <CAMpxmJW8edEZw81iQkwDr-Umdb1ibb85s=EshQs4yXRFh5LP=A@mail.gmail.com> (raw)
In-Reply-To: <20200114144214.GA1898224@kroah.com>
wt., 14 sty 2020 o 15:42 Greg KH <gregkh@linuxfoundation.org> napisał(a):
>
> On Thu, Jan 09, 2020 at 10:47:56AM +0100, Bartosz Golaszewski wrote:
> > śr., 8 sty 2020 o 21:54 Rob Herring <robh@kernel.org> napisał(a):
> > >
> > > On Tue, 7 Jan 2020 10:29:21 +0100, Khouloud Touil wrote:
> > > > As the at25 uses the NVMEM subsystem, and the property is now being
> > > > handled, adding reference for it in the device tree binding document,
> > > > which allows to specify the GPIO line to which the write-protect pin
> > > > is connected.
> > > >
> > > > Signed-off-by: Khouloud Touil <ktouil@baylibre.com>
> > > > ---
> > > > Documentation/devicetree/bindings/eeprom/at25.txt | 2 ++
> > > > 1 file changed, 2 insertions(+)
> > > >
> > >
> > > Reviewed-by: Rob Herring <robh@kernel.org>
> >
> > Hi Greg,
> >
> > AT25 patches usually go through the char-misc tree. In this case
> > however, the change depends on the other patches in this series. Can
> > you ack this and I'll take it through the AT24 tree exceptionally?
>
> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Patch applied with Greg's Ack.
Bart
WARNING: multiple messages have this Message-ID (diff)
From: Bartosz Golaszewski <bgolaszewski-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
To: Greg KH <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Srinivas Kandagatla
<srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Khouloud Touil <ktouil-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>,
baylibre-upstreaming-GWfripvEmMdhl2p70BpVqQ@public.gmane.org,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-devicetree
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-i2c <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linus Walleij
<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH v4 4/5] dt-bindings: at25: add reference for the wp-gpios property
Date: Tue, 14 Jan 2020 16:05:57 +0100 [thread overview]
Message-ID: <CAMpxmJW8edEZw81iQkwDr-Umdb1ibb85s=EshQs4yXRFh5LP=A@mail.gmail.com> (raw)
In-Reply-To: <20200114144214.GA1898224-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
wt., 14 sty 2020 o 15:42 Greg KH <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org> napisał(a):
>
> On Thu, Jan 09, 2020 at 10:47:56AM +0100, Bartosz Golaszewski wrote:
> > śr., 8 sty 2020 o 21:54 Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> napisał(a):
> > >
> > > On Tue, 7 Jan 2020 10:29:21 +0100, Khouloud Touil wrote:
> > > > As the at25 uses the NVMEM subsystem, and the property is now being
> > > > handled, adding reference for it in the device tree binding document,
> > > > which allows to specify the GPIO line to which the write-protect pin
> > > > is connected.
> > > >
> > > > Signed-off-by: Khouloud Touil <ktouil-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
> > > > ---
> > > > Documentation/devicetree/bindings/eeprom/at25.txt | 2 ++
> > > > 1 file changed, 2 insertions(+)
> > > >
> > >
> > > Reviewed-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
> >
> > Hi Greg,
> >
> > AT25 patches usually go through the char-misc tree. In this case
> > however, the change depends on the other patches in this series. Can
> > you ack this and I'll take it through the AT24 tree exceptionally?
>
> Acked-by: Greg Kroah-Hartman <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
Patch applied with Greg's Ack.
Bart
next prev parent reply other threads:[~2020-01-14 15:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 9:29 [PATCH v4 0/5] at24: move write-protect pin handling to nvmem core Khouloud Touil
2020-01-07 9:29 ` [PATCH v4 1/5] dt-bindings: nvmem: new optional property wp-gpios Khouloud Touil
2020-01-07 9:50 ` Linus Walleij
2020-01-07 9:50 ` Linus Walleij
2020-01-08 20:54 ` Rob Herring
2020-01-08 20:54 ` Rob Herring
2020-01-07 9:29 ` [PATCH v4 2/5] nvmem: add support for the write-protect pin Khouloud Touil
2020-01-30 8:06 ` Geert Uytterhoeven
2020-01-30 8:06 ` Geert Uytterhoeven
2020-02-17 13:14 ` Khouloud Touil
2020-02-17 13:14 ` Khouloud Touil
2020-02-17 14:34 ` Bartosz Golaszewski
2020-02-17 14:34 ` Bartosz Golaszewski
2020-02-17 15:11 ` Geert Uytterhoeven
2020-02-17 15:11 ` Geert Uytterhoeven
2020-01-07 9:29 ` [PATCH v4 3/5] dt-bindings: at24: make wp-gpios a reference to the property defined by nvmem Khouloud Touil
2020-01-08 20:54 ` Rob Herring
2020-01-08 20:54 ` Rob Herring
2020-01-07 9:29 ` [PATCH v4 4/5] dt-bindings: at25: add reference for the wp-gpios property Khouloud Touil
2020-01-08 20:54 ` Rob Herring
2020-01-08 20:54 ` Rob Herring
2020-01-09 9:47 ` Bartosz Golaszewski
2020-01-09 9:47 ` Bartosz Golaszewski
2020-01-14 14:42 ` Greg KH
2020-01-14 15:05 ` Bartosz Golaszewski [this message]
2020-01-14 15:05 ` Bartosz Golaszewski
2020-01-07 9:29 ` [PATCH v4 5/5] eeprom: at24: remove the write-protect pin support Khouloud Touil
2020-01-09 10:31 ` [PATCH v4 0/5] at24: move write-protect pin handling to nvmem core 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='CAMpxmJW8edEZw81iQkwDr-Umdb1ibb85s=EshQs4yXRFh5LP=A@mail.gmail.com' \
--to=bgolaszewski@baylibre.com \
--cc=baylibre-upstreaming@groups.io \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.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=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.