devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Eddie James <eajames@linux.ibm.com>, linux-kernel@vger.kernel.org
Cc: linux-aspeed@lists.ozlabs.org, devicetree@vger.kernel.org,
	andrew@aj.id.au, joel@jms.id.au,
	krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
	arnd@arndb.de, gregkh@linuxfoundation.org
Subject: Re: [PATCH v2 3/4] eeprom: ee1004: Add devicetree binding
Date: Tue, 21 Mar 2023 16:20:23 +0100	[thread overview]
Message-ID: <bad282d5-9e40-a99d-0abb-d04163dcf080@linaro.org> (raw)
In-Reply-To: <20230321151642.461618-4-eajames@linux.ibm.com>

On 21/03/2023 16:16, Eddie James wrote:
> Add an OF match table for devicetree instantiation of EE1004
> devices.

Subject: There is no device tree binding here. You add OF matching (or
support) to the driver.

> 
> Signed-off-by: Eddie James <eajames@linux.ibm.com>
> ---
>  drivers/misc/eeprom/ee1004.c | 7 +++++++
>  1 file changed, 7 insertions(+)

Best regards,
Krzysztof


  reply	other threads:[~2023-03-21 15:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 15:16 [PATCH v2 0/4] eeprom: ee1004: Enable devices on multiple busses Eddie James
2023-03-21 15:16 ` [PATCH v2 1/4] " Eddie James
2023-03-21 15:39   ` Rob Herring
2023-03-21 15:45     ` Eddie James
2023-03-21 15:16 ` [PATCH v2 2/4] doc: Add Atmel AT30TSE serial eeprom Eddie James
2023-03-21 15:19   ` Krzysztof Kozlowski
2023-03-21 15:46     ` Eddie James
2023-03-21 15:55       ` Eddie James
2023-03-27 15:18         ` Rob Herring
2023-03-27 19:01           ` Eddie James
2023-03-21 15:16 ` [PATCH v2 3/4] eeprom: ee1004: Add devicetree binding Eddie James
2023-03-21 15:20   ` Krzysztof Kozlowski [this message]
2023-03-21 15:16 ` [PATCH v2 4/4] ARM: dts: aspeed: bonnell: Add DIMM SPD Eddie James

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=bad282d5-9e40-a99d-0abb-d04163dcf080@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=andrew@aj.id.au \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=eajames@linux.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joel@jms.id.au \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --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).