From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Ben Myers <bpm@sgi.com>, xfs@oss.sgi.com
Subject: Re: [PATCH 0/3] xfs: fixes for 3.7-rc6
Date: Tue, 13 Nov 2012 02:11:47 -0500 [thread overview]
Message-ID: <20121113071147.GA32469@infradead.org> (raw)
In-Reply-To: <20121113030507.GE25039@dastard>
On Tue, Nov 13, 2012 at 02:05:07PM +1100, Dave Chinner wrote:
> Just FYI, the first thing that needs to be done after the userspace
> release is to resync the libxfs/libxlog code with the kernel code.
> That needs to be done before any of the CRC changes can be merged,
> so be prepared for a pretty major update that'll need review soon
> after the release.
>
> IIRC, the last kernel/user resync I did was about 15,000 lines of
> change I don't expect this to be quite as big (the previous one
> contained the btree consolidation changes), but I'd expect it to be
> in the order of 2-3000 lines of change to be needed.
Do we have anyone who has signed up for that work yet?
One thing I'd really love to do is to make the resyncs simpler, e.g.
make sure userspace can use the same #include statements as the kernel
code, and make sure all files are either used entirely in userspace or
not at all. Things like the split of xfs_extent_busy.c are going to
help with that, but I suspect there's more work to do.
> > Thanks for reposting your 3.8 queue, BTW. Sometimes I think that frequent
> > reposts are inconvenient, but in this case I think it will be helpful.
>
> When I'm having trouble tracking of several of my own patch sets for
> the same release, it's time for re-organisation and a repost.
> Besides, it's a habit Christoph and I got into a while back when we
> had lots of work going on and we needed to make sure nothing
> slipped through the cracks..... :)
For anything more than one or two simple patches a complete repost is
they way to spell a ping. Once you're having dozends of patches it's
almost guaranteed there are a few small fixes or context changes by the
time of the ping, and the repost takes care of having an uptodate
version.
And in case anyone wonder, yes I plan to get back to reviewing your bits
soon.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-11-13 7:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 11:09 [PATCH 0/3] xfs: fixes for 3.7-rc6 Dave Chinner
2012-11-12 11:09 ` [PATCH 1/3] xfs: fix attr tree double split corruption Dave Chinner
2012-11-12 19:10 ` Mark Tinguely
2012-11-12 11:09 ` [PATCH 2/3] xfs: fix broken error handling in xfs_vm_writepage Dave Chinner
2012-11-13 14:27 ` Mark Tinguely
2012-11-12 11:09 ` [PATCH 3/3] xfs: drop buffer io reference when a bad bio is built Dave Chinner
2012-11-12 20:51 ` Mark Tinguely
2012-11-13 2:01 ` [PATCH 0/3] xfs: fixes for 3.7-rc6 Ben Myers
2012-11-13 3:05 ` Dave Chinner
2012-11-13 7:11 ` Christoph Hellwig [this message]
2012-11-13 19:46 ` Dave Chinner
2012-11-13 21:20 ` Ben Myers
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=20121113071147.GA32469@infradead.org \
--to=hch@infradead.org \
--cc=bpm@sgi.com \
--cc=david@fromorbit.com \
--cc=xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox