From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] libdrm: bump to 2.4.52 and remove useless dependencies on libpciaccess
Date: Thu, 27 Feb 2014 23:44:26 +0100 [thread overview]
Message-ID: <20140227234426.324e0e42@skate> (raw)
In-Reply-To: <1393539908-14365-1-git-send-email-sebastien.bourdelin@savoirfairelinux.com>
Dear Sebastien Bourdelin,
On Thu, 27 Feb 2014 17:25:07 -0500, Sebastien Bourdelin wrote:
> Since the version 2.4.32, libdrm no longer requires dependencies on
> the libpciaccess unless for the intel-dri.
>
> For more information :
> http://cgit.freedesktop.org/mesa/drm/commit/?id=be30d350b64c1a83473a9ffbedf8e2c680a65fcd
>
> Signed-off-by: Sebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com>
> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> (PATCH v1)
> ---
> Changes v1 -> v2:
> - bump to version 2.4.52
Thanks a lot for your contribution!
However, the patch has two problems:
*) You added a significant change (bumping the version number), but
you kept the Reviewed-by tag of another person. This is typically
considered as a bad practice: Arnout had endorsed your previous
version, and maybe not this one.
*) When your commit log title contains something like "do this *AND*
do that", it's a strong indication that your patch is not correct, and
should instead be split in two patches: one "doing this" and the other
"doing that". In this case, the patch "doing that" could carry
Arnout's Reviewed-by, since it wouldn't have changed since Arnout's
review.
Would you mind resending an updated version that takes into account
those comments?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-27 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 22:25 [Buildroot] [PATCH v2] libdrm: bump to 2.4.52 and remove useless dependencies on libpciaccess Sebastien Bourdelin
2014-02-27 22:44 ` Thomas Petazzoni [this message]
2014-02-28 16:29 ` Sebastien Bourdelin
2014-02-27 23:04 ` Bernd Kuhls
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=20140227234426.324e0e42@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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