On 04/10/14 09:35, Stefan Assmann wrote:
On 08.04.2014 09:39, Stefan Assmann wrote:
On 08.04.2014 02:37, Luis R. Rodriguez wrote:
On Mon, Apr 7, 2014 at 6:57 AM, Stefan Assmann<sassmann@xxxxxxxxx> wrote:
next-20140221
Did you git reset --hard backports-20140221 ? The respective dated tag
for backports must be used for a specific dated tag for linux-next.
Likewise for the stable releases.
Luis
My backports tree is at 8e946501aef6e3dd5bac12eb45d24df8248672b0 which
should be the same as backports-20140221.
Stefan
I tried the same again in a newly installed VM and don't see any issues
there. Probably an issue with my build env then. Please ignore.
It may related to the used gcc version. I recall a similar issue with
mcount when I had a kernel build with a different gcc than the driver
module.
Regards,
Arend
Stefan
--
To unsubscribe from this list: send the line "unsubscribe backports" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe backports" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
