linux-ext4 - linux-2.6-block/for-next: Removal of BLKDEV_IFL_BARRIER and BLKDEV_IFL

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTi=EiCvRxAqnbWoPMhqYAZDQmsjaDRt+0dK-fRcV@mail.gmail.com>
Date:	Mon, 18 Oct 2010 02:11:25 +0200
From:	Sedat Dilek <sedat.dilek@...glemail.com>
To:	linux-ext4@...r.kernel.org
Cc:	axboe@...nel.dk, "Theodore Ts'o" <tytso@....edu>
Subject: linux-2.6-block/for-next: Removal of BLKDEV_IFL_BARRIER and BLKDEV_IFL_WAIT

Hi,

today, I pulled linux-2.6-block/for-next GIT branch [1] on top of
Linus-tree (2.6.36-rc8-git3).

Unfortunately, ext4/next GIT branch [2] is not "GIT-pull-able" on top
of this local GIT repository.
The cause for this is the removal of BLKDEV_IFL_BARRIER and
BLKDEV_IFL_WAIT in linux-2.6-block/for-next.

As there are few days left for 2.6.36-final, it would be great when
ext4/next could be prepared to work with linux-2.6-block/for-next.
Thanks in advance.

Kind Regards,
- Sedat -

[1] http://git.kernel.org/?p=linux/kernel/git/axboe/linux-2.6-block.git;a=shortlog;h=refs/heads/for-next
[2] http://git.kernel.org/?p=linux/kernel/git/tytso/ext4.git;a=shortlog;h=refs/heads/next
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html