linux-kernel - Re: [GIT PATCH] block: cleanup patches

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]

Date:	Mon, 16 Mar 2009 08:57:52 +0100
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [GIT PATCH] block: cleanup patches

On Mon, Mar 16 2009, Tejun Heo wrote:
> Jens Axboe wrote:
> > On Mon, Mar 16 2009, Tejun Heo wrote:
> >> Jens Axboe wrote:
> >>> On Sat, Mar 14 2009, Tejun Heo wrote:
> >>>> Tejun Heo wrote:
> >>>>> Hello,
> >>>>>
> >>>>> This patchset is available in the following git tree.
> >>>>>
> >>>>>  git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git block-cleanup
> >>>>>
> >>>>> This patchset contains the following 14 cleanup patches.
> >>>> Jens, once you're okay with the rest of the changes, I'll remove IDE
> >>>> related stuff and repost the patchset.
> >>> I only gave it a quick glance, looks mostly OK. Though I don't like
> >>> putting elv_ prefixed stuff in blk-core. I agree it belongs there
> >>> though, it's really block layer functionality and not io scheduler
> >>> interfacing. So rename it blk_ instead and put compatability names in
> >>> the header file instead.
> >> Yeap, that exactly is what's planned (the peek/fetch patches :-).
> > 
> > I figured that is where it's going :-)
> > How far along with that are you? We are getting really close to the
> > merge window, so it basically has to be ready _now_ to hit 2.6.30.
> 
> The peek/fetch patchset is almost ready.  They just need to be
> refreshed for for-2.6.30.  I'm currently trying to clean up rq->data,
> ->buffer and data length handling and was thinking about putting
> peek/fetch patchset on top of those, which I don't think will be ready
> soon enough for 2.6.30 merge window.  Given the nature of these
> patches, I think we can wait for 31 window?

Yeah, lets hold those off for 2.6.31. We definitely want plenty of time
to review and test such patches.

-- 
Jens Axboe

--
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/