devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Rosin <peda@axentia.se>
To: linux-kernel@vger.kernel.org
Cc: Peter Rosin <peda@axentia.se>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>,
	Russell King <linux@armlinux.org.uk>,
	linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] dt-bindings: at24: sort manufacturers alphabetically
Date: Tue, 16 Jan 2018 17:06:15 +0100	[thread overview]
Message-ID: <20180116160618.27859-2-peda@axentia.se> (raw)
In-Reply-To: <20180116160618.27859-1-peda@axentia.se>

Makes them easier to find.

Signed-off-by: Peter Rosin <peda@axentia.se>
---
 Documentation/devicetree/bindings/eeprom/at24.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/eeprom/at24.txt b/Documentation/devicetree/bindings/eeprom/at24.txt
index 1812c848e369..abfae1beca2b 100644
--- a/Documentation/devicetree/bindings/eeprom/at24.txt
+++ b/Documentation/devicetree/bindings/eeprom/at24.txt
@@ -38,9 +38,9 @@ Required properties:
 
                 "catalyst",
                 "microchip",
+                "nxp",
                 "ramtron",
                 "renesas",
-                "nxp",
                 "st",
 
                 Some vendors use different model names for chips which are just
-- 
2.11.0

  reply	other threads:[~2018-01-16 16:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16 16:06 [PATCH 0/4] use correct compatibles for the nxp,se97b chips Peter Rosin
2018-01-16 16:06 ` Peter Rosin [this message]
2018-01-16 17:26   ` [PATCH 1/4] dt-bindings: at24: sort manufacturers alphabetically Bartosz Golaszewski
     [not found]   ` <20180116160618.27859-2-peda-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>
2018-01-29 16:17     ` Rob Herring
2018-01-29 16:56       ` Bartosz Golaszewski
2018-02-21  9:11         ` Wolfram Sang
2018-02-21  9:23           ` Bartosz Golaszewski
2018-02-21  9:40             ` Wolfram Sang
2018-02-23  7:52               ` Bartosz Golaszewski
2018-02-23 10:32                 ` Wolfram Sang
2018-02-23 11:40                   ` Bartosz Golaszewski
2018-02-28  9:28   ` Bartosz Golaszewski
2018-01-16 16:06 ` [PATCH 2/4] dt-bindings: at24: add compatible for nxp,se97b Peter Rosin
2018-01-16 17:26   ` Bartosz Golaszewski
2018-01-29 16:18   ` Rob Herring
2018-03-02 10:17   ` Bartosz Golaszewski
2018-01-16 16:06 ` [PATCH 3/4] ARM: dts: at91: nattis: use the correct compatible for the eeprom Peter Rosin
2018-01-30 22:15   ` Alexandre Belloni
2018-01-16 16:06 ` [PATCH 4/4] ARM: dts: at91: tse850: " Peter Rosin
2018-01-30 22:15   ` Alexandre Belloni

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=20180116160618.27859-2-peda@axentia.se \
    --to=peda@axentia.se \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=brgl@bgdev.pl \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=nicolas.ferre@microchip.com \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).