From: Steven Whitehouse <swhiteho@redhat.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-next@vger.kernel.org, cluster-devel@redhat.com
Subject: Re: linux-next: commit "GFS2: Clean up log write code path" breakage
Date: Thu, 19 Apr 2012 10:34:54 +0100 [thread overview]
Message-ID: <1334828094.2718.1.camel@menhir> (raw)
In-Reply-To: <CAP=VYLoD6yLQkLO0Q=wGQ5yag9e9qw-5iwHLGgcck60Efy5-Vg@mail.gmail.com>
Hi,
On Wed, 2012-04-18 at 21:26 -0400, Paul Gortmaker wrote:
> Hi Steven,
>
> When you have a chance can you look at this? Git bisect says that
> this commit:
>
Yes, I can see what that is... the most amazing thing is that it ever
worked in the first place. I'm cooking up a patch to fix it which should
be ready very shortly,
Steve.
> ----------
> commit e80623efc450fb615d1496774c8d5c063a50fb3a
> Author: Steven Whitehouse <swhiteho@redhat.com>
> Date: Mon Apr 16 09:28:31 2012 +0100
>
> GFS2: Clean up log write code path
> ----------
>
> has caused the failure seen in several allmodconfigs (sparc, m68k).
>
> fs/gfs2/lops.c:379:42: error: request for member 'virtual' in
> something not a structure or union
> make[3]: *** [fs/gfs2/lops.o] Error 1
>
> Here are some examples:
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/6131431/
> http://kisskb.ellerman.id.au/kisskb/buildresult/6131694/
> http://kisskb.ellerman.id.au/kisskb/buildresult/6131511/
>
> Thanks,
> Paul.
WARNING: multiple messages have this Message-ID (diff)
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] linux-next: commit "GFS2: Clean up log write code path" breakage
Date: Thu, 19 Apr 2012 10:34:54 +0100 [thread overview]
Message-ID: <1334828094.2718.1.camel@menhir> (raw)
In-Reply-To: <CAP=VYLoD6yLQkLO0Q=wGQ5yag9e9qw-5iwHLGgcck60Efy5-Vg@mail.gmail.com>
Hi,
On Wed, 2012-04-18 at 21:26 -0400, Paul Gortmaker wrote:
> Hi Steven,
>
> When you have a chance can you look at this? Git bisect says that
> this commit:
>
Yes, I can see what that is... the most amazing thing is that it ever
worked in the first place. I'm cooking up a patch to fix it which should
be ready very shortly,
Steve.
> ----------
> commit e80623efc450fb615d1496774c8d5c063a50fb3a
> Author: Steven Whitehouse <swhiteho@redhat.com>
> Date: Mon Apr 16 09:28:31 2012 +0100
>
> GFS2: Clean up log write code path
> ----------
>
> has caused the failure seen in several allmodconfigs (sparc, m68k).
>
> fs/gfs2/lops.c:379:42: error: request for member 'virtual' in
> something not a structure or union
> make[3]: *** [fs/gfs2/lops.o] Error 1
>
> Here are some examples:
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/6131431/
> http://kisskb.ellerman.id.au/kisskb/buildresult/6131694/
> http://kisskb.ellerman.id.au/kisskb/buildresult/6131511/
>
> Thanks,
> Paul.
next prev parent reply other threads:[~2012-04-19 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 1:26 linux-next: commit "GFS2: Clean up log write code path" breakage Paul Gortmaker
2012-04-19 9:34 ` Steven Whitehouse [this message]
2012-04-19 9:34 ` [Cluster-devel] " Steven Whitehouse
2012-04-19 10:12 ` Steven Whitehouse
2012-04-19 10:12 ` [Cluster-devel] " Steven Whitehouse
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=1334828094.2718.1.camel@menhir \
--to=swhiteho@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=linux-next@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/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.