linux-kernel - Re: [RFC PATCH 0/12] ide-atapi remove pc->buf

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4A0763A5.4050600@kernel.org>
Date:	Mon, 11 May 2009 08:30:45 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
CC:	Borislav Petkov <petkovbb@...glemail.com>,
	linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jens Axboe <axboe@...nel.dk>
Subject: Re: [RFC PATCH 0/12] ide-atapi remove pc->buf

Hello, Bartlomiej.

Bartlomiej Zolnierkiewicz wrote:
> Good question, how's about:
> 
> Once tj/block-unify-sector-and-data_len is in block/for-2.6.31 and your tree
> is ready I will pull it into the separate branch.  This branch can be then
> pulled into ide/for-next or into new ide/all branch (replacing ide/for-next
> in linux-next).
> 
> This means that I'll have to synchronize merge window merges with Jens but
> this is needed already and shouldn't be a problem.
> 
> If somebody [ Tejun/Jens: I'm talking to you :) ] has a better idea how to
> handle this please stand-up.

There needs to be a sync point anyway and there's one more patchset on
top of block-unify-sector-and-data_len involving ide changes (the
block-peek-fetch one), so if both get acked by Jens, it would be
easier to simply branch out from there.  From there on, I don't expect
too much disruption to ide from further block layer changes, so things
should be okay.

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/