From: Mark Brown <broonie@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Jean Delvare <jdelvare@suse.de>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: jdelvare-hwmon tree unfetchable
Date: Mon, 1 Sep 2014 16:53:50 +0100 [thread overview]
Message-ID: <20140901155350.GF29327@sirena.org.uk> (raw)
In-Reply-To: <54049590.6060500@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
On Mon, Sep 01, 2014 at 08:49:36AM -0700, Guenter Roeck wrote:
> On 09/01/2014 05:28 AM, Mark Brown 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.
> Jean dropped the linux-fr.org domain, and his old e-mail address probably
> won't work anymore. The alternate (and temporary) pointer he gave me
> is http://jdelvare.nerim.net/devel/linux-3/jdelvare-hwmon/. It is empty,
> so you did not miss anything.
I figured it was something like that - the address definitely does
bounce. Thanks for letting me know, I'll update for tomorrow.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-09-01 15:54 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 [this message]
2014-09-02 7:54 ` Jean Delvare
2014-09-08 0:55 ` Stephen Rothwell
2014-09-01 16:57 ` Geert Uytterhoeven
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=20140901155350.GF29327@sirena.org.uk \
--to=broonie@kernel.org \
--cc=jdelvare@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.