From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Mark Brown <broonie@kernel.org>, Jean Delvare <jdelvare@suse.de>
Cc: Jean Delvare <khali@linux-fr.org>,
Linux-Next <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: linux-next: jdelvare-hwmon tree unfetchable
Date: Mon, 1 Sep 2014 18:57:29 +0200 [thread overview]
Message-ID: <CAMuHMdXmP8v3Grj=0Qay9eZ+zkWYTZAe4Qy+T8zJq=NDFU9tjQ@mail.gmail.com> (raw)
In-Reply-To: <20140901132808.c7b08f4ffa7055dc28e6dac7@kernel.org>
CC jean @ suse
On Mon, Sep 1, 2014 at 2:28 PM, Mark Brown <broonie@kernel.org> wrote:
> Today's linux-next merge of the jdelvare-hwmon tree got a conflict with Linus'
> tree which appeared to be due to the hwmon quilt series I got from Stephen being
> based on v3.14-rc3 and subsequent changes from mainline interacting badly with
> it. In addition I'm not able to check the original series since linux-fr.org does
> not resolve for me.
Same here. The domain exists, and seems to have been updated yesterday,
possibly breaking it?
> I'm really confused by what's going on here so I skipped the tree for today.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2014-09-01 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 12:28 linux-next: jdelvare-hwmon tree unfetchable Mark Brown
2014-09-01 13:18 ` Fabio Estevam
2014-09-01 13:46 ` Mark Brown
2014-09-01 15:49 ` Guenter Roeck
2014-09-01 15:53 ` Mark Brown
2014-09-02 7:54 ` Jean Delvare
2014-09-08 0:55 ` Stephen Rothwell
2014-09-01 16:57 ` Geert Uytterhoeven [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='CAMuHMdXmP8v3Grj=0Qay9eZ+zkWYTZAe4Qy+T8zJq=NDFU9tjQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=broonie@kernel.org \
--cc=jdelvare@suse.de \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.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;
as well as URLs for NNTP newsgroup(s).