From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Marcelo Mendes <marcelomspessoto@gmail.com>
Cc: harry.wentland@amd.com, sunpeng.li@amd.com,
Rodrigo.Siqueira@amd.com,
Linux AMDGPU <amd-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Removing duplicate copyright text
Date: Wed, 27 Dec 2023 12:52:23 +0700 [thread overview]
Message-ID: <ZYu7l9LiCJWdw0CB@archie.me> (raw)
In-Reply-To: <CAB4W1t5GsDUEUT6m_qHeEBC=gnQxyebY8W0n5uF1GGAh5yLgtw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
On Tue, Dec 26, 2023 at 11:49:09PM -0300, Marcelo Mendes wrote:
> Hello Bagas,
>
> I'm sorry for that. I will send another mail of this patch with your
> recommendations.
>
Please don't top-post; reply inline with appropriate context instead.
And don't send HTML emails as mailing lists don't like such.
When sending v2 (aka rerolling), mark it as such when generating patches
by passing `-v 2` to git-format-patch(1). And don't be rushed to send
the reroll; wait at least a day to allow reviewers to review before
reroll. If there are any comments from them, you should address them too.
See you in v2!
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-12-27 5:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231226235741.4376-1-marcelomspessoto@gmail.com>
2023-12-27 2:30 ` [PATCH] Removing duplicate copyright text Bagas Sanjaya
[not found] ` <CAB4W1t5GsDUEUT6m_qHeEBC=gnQxyebY8W0n5uF1GGAh5yLgtw@mail.gmail.com>
2023-12-27 5:52 ` Bagas Sanjaya [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=ZYu7l9LiCJWdw0CB@archie.me \
--to=bagasdotme@gmail.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelomspessoto@gmail.com \
--cc=sunpeng.li@amd.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