From: Saul Wold <sgw@linux.intel.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libdrm: Upgrade to 2.4.64
Date: Wed, 16 Dec 2015 13:54:06 -0800 [thread overview]
Message-ID: <1450302846.3199.211.camel@linux.intel.com> (raw)
In-Reply-To: <CAP71Wjz2XDTzzd0pO6FAXAc715QDaxY+FyOk_NoFOfoCoaOptg@mail.gmail.com>
On Wed, 2015-12-16 at 21:32 +0100, Nicolas Dechesne wrote:
> On Wed, Dec 16, 2015 at 8:26 PM, Saul Wold <sgw@linux.intel.com>
> wrote:
> > Signed-off-by: Saul Wold <sgw@linux.intel.com>
> > ---
> > meta/recipes-graphics/drm/{libdrm_2.4.62.bb => libdrm_2.4.64.bb} |
> > 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> > rename meta/recipes-graphics/drm/{libdrm_2.4.62.bb =>
> > libdrm_2.4.64.bb} (92%)
> >
> > diff --git a/meta/recipes-graphics/drm/libdrm_2.4.62.bb
> > b/meta/recipes-graphics/drm/libdrm_2.4.64.bb
> > similarity index 92%
> > rename from meta/recipes-graphics/drm/libdrm_2.4.62.bb
> > rename to meta/recipes-graphics/drm/libdrm_2.4.64.bb
> > index ea6305e..cb0efe1 100644
> > --- a/meta/recipes-graphics/drm/libdrm_2.4.62.bb
> > +++ b/meta/recipes-graphics/drm/libdrm_2.4.64.bb
>
> why not 2.4.65 which is the current most recent release?
>
My bad, will refresh for 2.4.65, looked in the wrong place!
> > @@ -12,8 +12,9 @@ DEPENDS = "libpthread-stubs udev libpciaccess"
> >
> > SRC_URI = "http://dri.freedesktop.org/libdrm/${BP}.tar.bz2 \
> > file://installtests.patch "
> > -SRC_URI[md5sum] = "c9291bae0e5ca65d1483821d3698d3ab"
> > -SRC_URI[sha256sum] =
> > "906c294bdbe1c94c3ca084305d61a6e5a8367f3b4986e6cc13b1e9b3f75931dc"
> > +
>
> Is this extra line intentional?
>
Yes, we would typically separate the SRC_URI from the checksums for
easier reading. A predominant number of recipes have the space.
Sau!
> > +SRC_URI[md5sum] = "543b2d28359cf33974fa0e772dd61732"
> > +SRC_URI[sha256sum] =
> > "b60786fe7d6e42adb3966ce1a658f63fec528d537396381cbda93bcc99a934b6"
> >
> > inherit autotools pkgconfig
> >
> > --
> > 2.5.0
> >
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2015-12-16 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 19:26 [PATCH] libdrm: Upgrade to 2.4.64 Saul Wold
2015-12-16 20:32 ` Nicolas Dechesne
2015-12-16 21:54 ` Saul Wold [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=1450302846.3199.211.camel@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=nicolas.dechesne@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
/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