From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Naveen Kumar M <mnkumar@google.com>,
Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
royluo@google.com, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: usb: add no-64-bit-support property
Date: Wed, 1 Nov 2023 08:06:51 +0100 [thread overview]
Message-ID: <eb409c0c-14d2-465c-8cc8-1fccae4c6757@linaro.org> (raw)
In-Reply-To: <CA+Hc5+4Gh6gDuD_NORmJR0zHx3qK6oTagx=wQ_EWf=_NJ0qy6A@mail.gmail.com>
On 01/11/2023 05:20, Naveen Kumar M wrote:
> Adding the reviewers/maintainers I missed in the previous mail to this patch
Nope, it does not work like this.
1. I don't have the patch in mailbox.
2. How can I be sure it was even tested by automation?
I won't be reviewing it. Follow Linux kernel submission process.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-11-01 7:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 4:40 [PATCH 0/2] Add a quirk in xhci-plat for parent nodes to specify no 64 bit support Naveen Kumar
2023-10-31 4:40 ` [PATCH 1/2] usb: host: xhci-plat: Add quirk-no-64-bit-support Naveen Kumar
2023-11-01 4:43 ` Naveen Kumar M
2023-11-01 6:27 ` Greg Kroah-Hartman
2023-10-31 4:40 ` [PATCH 2/2] dt-bindings: usb: add no-64-bit-support property Naveen Kumar
2023-10-31 5:54 ` Greg Kroah-Hartman
2023-10-31 16:52 ` Krzysztof Kozlowski
[not found] ` <CA+Hc5+4Gh6gDuD_NORmJR0zHx3qK6oTagx=wQ_EWf=_NJ0qy6A@mail.gmail.com>
2023-11-01 4:36 ` Naveen Kumar M
2023-11-01 7:06 ` Krzysztof Kozlowski [this message]
2023-11-01 4:42 ` [PATCH 0/2] Add a quirk in xhci-plat for parent nodes to specify no 64 bit support Naveen Kumar M
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=eb409c0c-14d2-465c-8cc8-1fccae4c6757@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=mnkumar@google.com \
--cc=robh+dt@kernel.org \
--cc=royluo@google.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
all inboxes | Powered by JetHome®