From: Paz Zcharya <pazz@chromium.org>
To: Louis Chauvet <louis.chauvet@bootlin.com>
Cc: Sean Paul <seanpaul@google.com>,
Drew Davenport <ddavenport@google.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
David Airlie <airlied@gmail.com>,
Haneen Mohammed <hamohammed.sa@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Melissa Wen <melissa.srw@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH] drm/vkms: Add support for ABGR8888 pixel format
Date: Wed, 29 Jan 2025 14:27:21 +0000 [thread overview]
Message-ID: <Z5o6yRJFrImztKoU@google.com> (raw)
In-Reply-To: <Z5oAcugIxU6zdROD@louis-chauvet-laptop>
On Wed, Jan 29, 2025 at 11:18:26AM +0100, Louis Chauvet wrote:
> And I just noticed that "changes in v2" is in the commit log. It should
> not be there.
>
> To add a changelog, you must put it after ---, so in your case your commit
> should be something like:
>
> drm/vkms: Add support for ABGR8888 pixel format
>
> Add support for [...] adoption.
>
> Signed-off-by: Paz Zcharya <pazz@google.com>
>
> ---
>
> Changes in v2:
> [...]
>
> Can you send a "real" v2 with the correct commit message and the correct
> author?
>
> If you don't know it, you can use b4[1] to help you manage your series and
> iterations.
>
> [1]:https://b4.docs.kernel.org/en/latest/
>
>
Just resent it.
My email server is using pazz@chromium.org, so I went with that.
I really hope I got it done right this time.
I apologize for any additional work or inconvenience I may have caused.
I greatly appreciate your help,
Paz Zcharya
next prev parent reply other threads:[~2025-01-29 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 23:59 [PATCH] drm/vkms: Add support for ABGR8888 pixel format Paz Zcharya
2025-01-28 10:04 ` Louis Chauvet
2025-01-28 15:08 ` Paz Zcharya
2025-01-29 10:18 ` Louis Chauvet
2025-01-29 14:27 ` Paz Zcharya [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-07 14:27 Paz Zcharya
2024-10-07 16:51 ` Louis Chauvet
2024-10-09 8:33 ` Paz Zcharya
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=Z5o6yRJFrImztKoU@google.com \
--to=pazz@chromium.org \
--cc=airlied@gmail.com \
--cc=ddavenport@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=louis.chauvet@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=melissa.srw@gmail.com \
--cc=mripard@kernel.org \
--cc=seanpaul@google.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.