From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Russell King <rmk@armlinux.org.uk>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: unable to fetch the arm tree
Date: Mon, 14 Nov 2016 21:42:49 +1100 [thread overview]
Message-ID: <20161114214249.21ebfb09@canb.auug.org.au> (raw)
In-Reply-To: <20161114102219.GE17314@flint.armlinux.org.uk>
Hi Russell,
On Mon, 14 Nov 2016 10:22:19 +0000 Russell King <rmk@armlinux.org.uk> wrote:
>
> Gah, that's down to selinux having an argument over how the repository
> should be labelled - different parts of the system want different
> labels on that. selinux is sometimes a nightmare.
>
> Should be fixed now.
Yep, looks good, thanks.
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2016-11-14 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 22:29 linux-next: unable to fetch the arm tree Stephen Rothwell
2016-11-14 10:22 ` Russell King
2016-11-14 10:42 ` Stephen Rothwell [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=20161114214249.21ebfb09@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rmk@armlinux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).