From: Steven Whitehouse <swhiteho@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, cluster-devel@redhat.com,
Bob Peterson <rpeterso@redhat.com>
Subject: Re: linux-next: Tree for Apr 20 (gfs2)
Date: Mon, 20 Apr 2015 16:44:31 +0100 [thread overview]
Message-ID: <55351EDF.6000708@redhat.com> (raw)
In-Reply-To: <55351DDC.9060409@infradead.org>
Hi,
On 20/04/15 16:40, Randy Dunlap wrote:
> On 04/19/15 22:45, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do not add any v4.2 material to your linux-next included trees
>> until after v4.1-rc1 is released.
>>
>> Changes since 20150415:
>>
> on i386:
>
> ERROR: "__divdi3" [fs/gfs2/gfs2.ko] undefined!
>
>
>
These notices should go to Bob as well now, since he is looking after
the tree that you are pulling from. I suspect that might be from one of
his patches too,
Steve.
next prev parent reply other threads:[~2015-04-20 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 5:45 linux-next: Tree for Apr 20 Stephen Rothwell
2015-04-20 15:40 ` linux-next: Tree for Apr 20 (gfs2) Randy Dunlap
2015-04-20 15:44 ` Steven Whitehouse [this message]
2015-04-24 12:45 ` [Cluster-devel] " Bob Peterson
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=55351EDF.6000708@redhat.com \
--to=swhiteho@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rpeterso@redhat.com \
--cc=sfr@canb.auug.org.au \
/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).