From: "Rafał Miłecki" <rafal@milecki.pl>
To: Vinod Koul <vkoul@kernel.org>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
"Kishon Vijay Abraham I" <kishon@ti.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
"Hauke Mehrtens" <hauke@hauke-m.de>,
bcm-kernel-feedback-list@broadcom.com,
linux-phy@lists.infradead.org,
"Vivek Unune" <npcomplete13@gmail.com>
Subject: Re: [PATCH] dt-bindings: phy: bcm-ns-usb3-phy: convert to yaml
Date: Mon, 15 Mar 2021 18:27:46 +0100 [thread overview]
Message-ID: <97981a899fe74c534d29d11485a2dbd2@milecki.pl> (raw)
In-Reply-To: <YE85xs+HX5UUXlXo@vkoul-mobl>
On 2021-03-15 11:41, Vinod Koul wrote:
> On 11-03-21, 21:31, Rafał Miłecki wrote:
>> Hi,
>>
>> On 16.11.2020 08:46, Rafał Miłecki wrote:
>> > From: Rafał Miłecki <rafal@milecki.pl>
>> >
>> > 1. Change syntax from txt to yaml
>> > 2. Drop "Driver for" from the title
>> > 3. Drop "reg = <0x0>;" from example (noticed by dt_binding_check)
>> > 4. Specify license
>> >
>> > Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
>> > ---
>> > I think this should go through linux-phy tree. Kishon, Vinod, can you
>> > take this patch?
>> >
>> > This patch generates a false positive checkpatch.pl warning [0].
>> > Please ignore:
>> > WARNING: DT binding docs and includes should be a separate patch. See: Documentation/devicetree/bindings/submitting-patches.rst
>> >
>> > [0] https://lkml.org/lkml/2020/2/18/1084
>>
>> Kishon, Vinod: I sent this patch back in December, it was Reviewed-by
>> Rob, but never accepted.
>>
>> Could you push this patch to the linux-phy.git?
>
> Can you please rebase and resent me this patch. I am trying to
> streamline patches now using phy ml and pw instance so that we dont
> miss
> anything..
Both patches apply cleanly. Maybe your mail client malformed them for
you?
They are accessible in the devicetree-bindings patchwork:
https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20201116074650.16070-1-zajec5@gmail.com/
https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20201116074650.16070-2-zajec5@gmail.com/
You can apply both patches doing e.g.:
curl
https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20201116074650.16070-1-zajec5@gmail.com/mbox/
| git am
curl
https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20201116074650.16070-2-zajec5@gmail.com/mbox/
| git am
prev parent reply other threads:[~2021-03-15 18:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 7:46 [PATCH] dt-bindings: phy: bcm-ns-usb3-phy: convert to yaml Rafał Miłecki
2020-11-16 7:46 ` [PATCH] dt-bindings: phy: bcm-ns-usb2-phy: " Rafał Miłecki
2020-12-07 19:21 ` Rob Herring
2021-03-11 20:33 ` Rafał Miłecki
2020-11-19 6:30 ` [PATCH] dt-bindings: phy: bcm-ns-usb3-phy: " Vinod Koul
2020-11-30 15:43 ` Vinod Koul
2020-11-30 15:58 ` Rafał Miłecki
2020-11-30 16:01 ` Rafał Miłecki
2020-12-07 19:20 ` Rob Herring
2021-03-11 20:31 ` Rafał Miłecki
2021-03-15 10:41 ` Vinod Koul
2021-03-15 17:27 ` Rafał Miłecki [this message]
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=97981a899fe74c534d29d11485a2dbd2@milecki.pl \
--to=rafal@milecki.pl \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=npcomplete13@gmail.com \
--cc=vkoul@kernel.org \
--cc=zajec5@gmail.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).