From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Steffen Sledz <sledz@dresearch-fe.de>
Cc: Lianhao Lu <lianhao.lu@intel.com>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: hash generation/PR service problem with xuser-account and other packages
Date: Wed, 24 Sep 2014 14:34:31 +0100 [thread overview]
Message-ID: <1411565671.4189.55.camel@ted> (raw)
In-Reply-To: <5422C59E.4090107@dresearch-fe.de>
On Wed, 2014-09-24 at 15:22 +0200, Steffen Sledz wrote:
> This patch fixes the cpufreq-tweaks (from meta-angstrom) problem too. :)
>
> So there's still linux-firmware pending from the packages i mentioned.
Actually, I pushed a patch for that last night. It was the same debug
approach as the second case I mentioned, diff the sigs and the issue
became clear.
Cheers,
Richard
prev parent reply other threads:[~2014-09-24 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 12:07 hash generation/PR service problem with xuser-account and other packages Steffen Sledz
2014-09-23 13:21 ` Richard Purdie
2014-09-23 14:51 ` Steffen Sledz
2014-09-23 16:16 ` Richard Purdie
2014-09-24 13:22 ` Steffen Sledz
2014-09-24 13:34 ` Richard Purdie [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=1411565671.4189.55.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=lianhao.lu@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sledz@dresearch-fe.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox