From: Dave Chinner <david@fromorbit.com>
To: xfs-masters@oss.sgi.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [xfs-masters] Re: linux-next: Tree for June 24 (XFS x2)
Date: Wed, 25 Jun 2008 13:43:24 +1000 [thread overview]
Message-ID: <20080625034324.GE11558@disturbed> (raw)
In-Reply-To: <4861A6EB.6050806@sgi.com>
On Wed, Jun 25, 2008 at 12:01:15PM +1000, Lachlan McIlroy wrote:
> Dave Chinner wrote:
> > On Tue, Jun 24, 2008 at 05:18:09PM -0700, Randy Dunlap wrote:
> >> XFS shows 2 build problems today.
> >>
> >> 1. xfs_stats.h problem
> >>
> >> CC fs/xfs/xfs_rtalloc.o
> >> In file included from /local/linsrc/linux-next-20080624/fs/xfs/linux-2.6/xfs_linux.h:91,
> >> from /local/linsrc/linux-next-20080624/fs/xfs/xfs.h:44,
> >> from /local/linsrc/linux-next-20080624/fs/xfs/xfs_rtalloc.c:18:
> >> /local/linsrc/linux-next-20080624/fs/xfs/linux-2.6/xfs_stats.h: In function 'xfs_init_procfs':
> >> /local/linsrc/linux-next-20080624/fs/xfs/linux-2.6/xfs_stats.h:150: error: expected ';' before '}' token
> >> make[3]: *** [fs/xfs/xfs_rtalloc.o] Error 1
> >
> > This will be a !CONFIG_PROC_FS change.
> >
> > Lachlan/Niv - This is the guilty party:
> >
> > http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs-2.6.git;a=commit;h=e0fe783155e4f1c7106f3579c258b9f995330c19
> >
> > The commit log is:
> >
> > [XFS]
> >
> > SGI-PV: 111111
> > SGI-Modid: xfs-linux-melb:xfs-kern:31210a
> >
> > Signed-off-by: Niv Sardi <xaiki@sgi.com>
> > Signed-off-by: Lachlan McIlroy <lachlan@sgi.com>
> > ---
> >
> > What the hell happened here? Where's the commit title, description
> > so this can be tracked back to a real patch? That PV# is also bogus....
> >
> > I suspect that it is this patch:
> >
> > http://oss.sgi.com/archives/xfs/2008-05/msg00322.html
> >
> > Which means that the Signed-Off-By list is incorrect as well as the original
> > patch came from Christoph. This can't go to mainline like this - the commit log
> > needs to be fixed up.
>
> We knew this checkin was stuffed up and I was planning to fix it in the for-linus
> branch before pushing to mainline. The merge tools had kittens when it came across
> it too. I think we need to rip it out of ptools and re-checkin it in with the
> correct details.
It never should have made the merge in that state. Niv, I suggest
you stop using that broken script of yours to do checkins because you
do nothing but break stuff with it. Change logs like:
xiaki pmod2git xfs-linux-melb:xfs-kern:31210a
(http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_stats.h?f=h#rev1.18)
in the CVS tree and busted git logs make it just about impossible to
track where something came from.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-06-25 3:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 7:56 linux-next: Tree for June 24 Stephen Rothwell
2008-06-24 11:51 ` [BUG] linux-next: Tree for June 24 - kernel panic at tg3_reset_hw() on x86_64 Kamalesh Babulal
[not found] ` <20080624175612.cdf29651.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2008-06-24 17:53 ` [BUILD-FAILURE] linux-next: Tree for June 24 - missing files in drivers/media/dvb/ Kamalesh Babulal
2008-06-24 17:53 ` Kamalesh Babulal
2008-06-25 3:28 ` Stephen Rothwell
2008-06-25 3:48 ` Stephen Rothwell
2008-06-29 11:43 ` Mauro Carvalho Chehab
2008-06-29 12:35 ` Stephen Rothwell
2008-06-25 3:31 ` Stephen Rothwell
2008-06-25 0:18 ` linux-next: Tree for June 24 (XFS x2) Randy Dunlap
2008-06-25 0:37 ` [xfs-masters] " Dave Chinner
2008-06-25 1:31 ` Timothy Shimmin
2008-06-25 1:52 ` Timothy Shimmin
2008-06-26 8:17 ` Christoph Hellwig
2008-06-27 7:26 ` Stephen Rothwell
2008-06-25 2:01 ` Lachlan McIlroy
2008-06-25 3:43 ` Dave Chinner [this message]
2008-06-27 13:23 ` Christoph Hellwig
2008-07-16 7:19 ` Christoph Hellwig
2008-07-17 5:26 ` Timothy Shimmin
2008-07-17 8:28 ` Stephen Rothwell
2008-06-27 13:20 ` Christoph Hellwig
2008-06-25 0:24 ` linux-next: Tree for June 24 (ivtv) Randy Dunlap
2008-06-25 6:05 ` Hans Verkuil
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=20080625034324.GE11558@disturbed \
--to=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=xfs-masters@oss.sgi.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.