| 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
| ||
|
Message-ID: <4B1283C9.1030002@panasas.com> Date: Sun, 29 Nov 2009 16:23:05 +0200 From: Boaz Harrosh <bharrosh@...asas.com> To: James Bottomley <James.Bottomley@...senPartnership.com> CC: open-osd <osd-dev@...n-osd.org>, Stephen Rothwell <sfr@...b.auug.org.au>, linux-next@...r.kernel.org, linux-kernel@...r.kernel.org, linux-scsi <linux-scsi@...r.kernel.org> Subject: Re: linux-next: manual merge of the osd tree with the scsi tree On 11/29/2009 03:46 PM, James Bottomley wrote: >> >> Should I repost the correct two patches (my preference)? should I send in a fix to >> current scsi-misc tree? or should I send two SQUASH-ME patches to the two bad commits >> in your tree? >> >> How do you want to proceed? > > Send me the replacement patch (and tell me which commit id in my tree > it's replacing). > Thank you James. I'm posting two patches as reply to this mail. [PATCH 1/2] osduld: Use device->release instead of internal kref which replaces: f89b9ee [SCSI] osduld: Use device->release instead of internal kref and [PATCH 2/2] libosd: osd_dev_info: Unique Identification of an OSD device which replaces: 3b616d4 [SCSI] libosd: osd_dev_info: Unique Identification of an OSD device > Thanks, > > James > > Boaz -- 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/
Powered by blists - more mailing lists