linux-kernel - Re: [GIT PULL] block changes for 2.6.28

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: <20081010.115108.199149570.davem@davemloft.net>
Date:	Fri, 10 Oct 2008 11:51:08 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jens.axboe@...cle.com
Cc:	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	James.Bottomley@...senPartnership.com
Subject: Re: [GIT PULL] block changes for 2.6.28

From: Jens Axboe <jens.axboe@...cle.com>
Date: Fri, 10 Oct 2008 19:49:31 +0200

> On Fri, Oct 10 2008, David Miller wrote:
> > From: Jens Axboe <jens.axboe@...cle.com>
> > Date: Fri, 10 Oct 2008 10:09:16 +0200
> > 
> > > This is the bulk of the block layer changes for 2.6.28. As other git
> > > trees are based on this (like SCSI), it would be good if you could merge
> > > it sooner rather than later.
> > > 
> > > Please pull from:
> > > 
> > >         git://git.kernel.dk/linux-2.6-block.git for-2.6.28
> > 
> > Did you merge in my generic remote softirq bits or are you going
> > to do that later?
> 
> I did not, I thought you would merge them youself (I acked the patchset,
> iirc). So either do that, or I can take it through the second (and
> smaller) merge of block bits. Either way, I'm fine with it for 2.6.28
> :-)

Please take it in.

In my final posting of those changes I made it clear that the way
to do this is to have any users of the infrastructure pull my GIT
tree in:

	master.kernel.org:/pub/scm/linux/kernel/git/davem/softirq-2.6.git

and whoever went first into Linus's tree would get it there.

I'm not at the point where I can use this in the networking and likely
won't have such work ready for 2.6.28 so it's imperative that you do
this at this point :-)
--
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/