From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alex Elder <aelder@sgi.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [GIT PULL] XFS update for 2.6.33-rc1
Date: Thu, 10 Dec 2009 22:30:48 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0912102228180.3560@localhost.localdomain> (raw)
In-Reply-To: <200912102219.nBAMJRr6028987@stout.americas.sgi.com>
On Thu, 10 Dec 2009, Alex Elder wrote:
>
> git://oss.sgi.com/xfs/xfs for-linus
Hmm. There seems to be a lot of duplicate commits there due to something
odd going on: rebasing _and_ then merging the rebased end result. IOW,
these are all duplicates:
xfs: cleanup data end I/O handlers
xfs: cleanup data end I/O handlers
xfs: cleanup dmapi macros in the umount path
xfs: cleanup dmapi macros in the umount path
xfs: Fix error return for fallocate() on XFS
xfs: Fix error return for fallocate() on XFS
xfs: fix mmap_sem/iolock inversion in xfs_free_eofblocks
xfs: fix mmap_sem/iolock inversion in xfs_free_eofblocks
xfs: I/O completion handlers must use NOFS allocations
xfs: I/O completion handlers must use NOFS allocations
xfs: kill the STATIC_INLINE macro
xfs: kill the STATIC_INLINE macro
xfs: remove incorrect sparse annotation for xfs_iget_cache_miss
xfs: remove incorrect sparse annotation for xfs_iget_cache_miss
xfs: remove IO_ISAIO
xfs: remove IO_ISAIO
xfs: rename xfs_attr_fetch to xfs_attr_get_int
xfs: rename xfs_attr_fetch to xfs_attr_get_int
xfs: reset the i_iolock lock class in the reclaim path
xfs: reset the i_iolock lock class in the reclaim path
xfs: simplify inode teardown
xfs: simplify inode teardown
xfs: simplify xfs_buf_get / xfs_buf_read interfaces
xfs: simplify xfs_buf_get / xfs_buf_read interfaces
xfs: uninline xfs_get_extsz_hint
xfs: uninline xfs_get_extsz_hint
xfs: use WRITE_SYNC_PLUG for synchronous writeout
xfs: use WRITE_SYNC_PLUG for synchronous writeout
xfs: Wrapped journal record corruption on read at recovery
xfs: Wrapped journal record corruption on read at recovery
What's up, doc?
Linus
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-12-11 6:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 22:19 [GIT PULL] XFS update for 2.6.33-rc1 Alex Elder
2009-12-11 6:30 ` Linus Torvalds [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-15 15:01 Alex Elder
2009-12-16 21:26 Alex Elder
2009-12-16 21:55 ` Randy Dunlap
2009-12-17 0:20 ` Dave Chinner
2009-12-17 1:56 ` Randy Dunlap
2009-12-17 3:41 ` Alex Elder
2010-01-08 17:44 ` Randy Dunlap
2010-01-08 18:09 ` Alex Elder
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=alpine.LFD.2.00.0912102228180.3560@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=aelder@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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