devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Farber, Eliav" <farbere@amazon.com>, Rob Herring <robh@kernel.org>
Cc: brgl@bgdev.pl, mark.rutland@arm.com, arnd@arndb.de,
	gregkh@linuxfoundation.org, linux-i2c@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	talel@amazon.com, hhhawa@amazon.com, jonnyc@amazon.com,
	hanochu@amazon.com, ronenk@amazon.com, itamark@amazon.com,
	shellykz@amazon.com, shorer@amazon.com, amitlavi@amazon.com,
	almogbs@amazon.com, dkl@amazon.com, dwmw@amazon.co.uk
Subject: Re: [PATCH v2 1/2] dt-bindings: at24: add new optional power-supply property
Date: Tue, 30 Aug 2022 20:05:32 +0300	[thread overview]
Message-ID: <8b9f49c6-86fa-b072-9cd0-5e363596593c@linaro.org> (raw)
In-Reply-To: <9e8a39d0-6267-cbac-da29-00e41871e14b@amazon.com>

On 28/08/2022 18:45, Farber, Eliav wrote:
> On 8/23/2022 12:46 AM, Rob Herring wrote:
>>>  Documentation/devicetree/bindings/eeprom/at24.txt | 3 +++
>>>  1 file changed, 3 insertions(+)
>>
>> This file doesn't exist any more. Use the latest -rc1 kernel unless
>> there is a reason you need a different (even later) base.
> I applied the change on top of v6.0-rc1

Not really. The file is gone since v5.5-rc1 as you can easily see in the
sources.

Since you did not Cc-me, it's another proof you based your work on some
old kernel.

Best regards,
Krzysztof

  reply	other threads:[~2022-08-30 17:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 10:58 [PATCH v2 0/2] add power-supply control to enable eeprom usage Eliav Farber
2022-08-22 10:58 ` [PATCH v2 1/2] dt-bindings: at24: add new optional power-supply property Eliav Farber
2022-08-22 21:46   ` Rob Herring
2022-08-28 15:45     ` Farber, Eliav
2022-08-30 17:05       ` Krzysztof Kozlowski [this message]
2022-08-22 10:58 ` [PATCH v2 2/2] eeprom: at24: add support for power-supply control Eliav Farber
2022-08-28 14:28   ` Bartosz Golaszewski
2022-08-28 15:47     ` Farber, Eliav

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=8b9f49c6-86fa-b072-9cd0-5e363596593c@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=almogbs@amazon.com \
    --cc=amitlavi@amazon.com \
    --cc=arnd@arndb.de \
    --cc=brgl@bgdev.pl \
    --cc=devicetree@vger.kernel.org \
    --cc=dkl@amazon.com \
    --cc=dwmw@amazon.co.uk \
    --cc=farbere@amazon.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hanochu@amazon.com \
    --cc=hhhawa@amazon.com \
    --cc=itamark@amazon.com \
    --cc=jonnyc@amazon.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh@kernel.org \
    --cc=ronenk@amazon.com \
    --cc=shellykz@amazon.com \
    --cc=shorer@amazon.com \
    --cc=talel@amazon.com \
    /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).