From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Tomer Maimon <tmaimon77@gmail.com>, Greg KH <gregkh@linuxfoundation.org>
Cc: peter.chen@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, xu.yang_2@nxp.com,
peng.fan@nxp.com, avifishman70@gmail.com, tali.perry1@gmail.com,
joel@jms.id.au, venture@google.com, yuenn@google.com,
benjaminfair@google.com, j.neuschaefer@gmx.net,
openbmc@lists.ozlabs.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH RESEND v3 0/3] usb: ChipIdea: add Nuvoton NPCM UDC support
Date: Tue, 3 Oct 2023 10:32:49 +0200 [thread overview]
Message-ID: <0298e4a7-0f40-41d6-82f3-327d2fe493cc@linaro.org> (raw)
In-Reply-To: <CAP6Zq1jHzRP1Ytzk8YXyR8ppAP=ZoPvPkYvC2yMRfTt5140zqw@mail.gmail.com>
On 03/10/2023 08:56, Tomer Maimon wrote:
> Hi Greg,
>
> Forgot to add in Acked-by: Peter Chen <peter.chen@kernel.org> in V3,
> Resend the patch set with the Ack.
>
> Should I do it differently?
If it is RESEND after some time (min. 2 weeks), then it is fine. If you
added tags or changed something, make a new version. If you resend for
any other reason (assuming resend is valid), please mention shortly why
do you resend (e.g. "My company email servers maybe blocked it, so
resending without changes").
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-10-03 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 16:13 [PATCH RESEND v3 0/3] usb: ChipIdea: add Nuvoton NPCM UDC support Tomer Maimon
2023-10-02 16:13 ` [PATCH RESEND v3 1/3] usb: chipidea: add CI_HDRC_FORCE_VBUS_ACTIVE_ALWAYS flag Tomer Maimon
2023-10-02 16:13 ` [PATCH RESEND v3 2/3] dt-bindings: usb: ci-hdrc-usb2: add npcm750 and npcm845 compatible Tomer Maimon
2023-10-02 16:13 ` [PATCH RESEND v3 3/3] usb: chipidea: Add support for NPCM Tomer Maimon
2023-10-03 6:50 ` [PATCH RESEND v3 0/3] usb: ChipIdea: add Nuvoton NPCM UDC support Greg KH
2023-10-03 6:56 ` Tomer Maimon
2023-10-03 7:05 ` Greg KH
2023-10-03 7:12 ` Tomer Maimon
2023-10-03 8:32 ` Krzysztof Kozlowski [this message]
2023-10-03 9:23 ` Tomer Maimon
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=0298e4a7-0f40-41d6-82f3-327d2fe493cc@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=j.neuschaefer@gmx.net \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=peng.fan@nxp.com \
--cc=peter.chen@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=xu.yang_2@nxp.com \
--cc=yuenn@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