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
| ||
|
Date: Wed, 18 Apr 2012 00:17:26 -0700 From: "Nicholas A. Bellinger" <nab@...ux-iscsi.org> To: Chris Boot <bootc@...tc.net> Cc: linux1394-devel@...ts.sourceforge.net, target-devel@...r.kernel.org, linux-kernel@...r.kernel.org, agrover@...hat.com, clemens@...isch.de, stefanr@...6.in-berlin.de, Christoph Hellwig <hch@....de> Subject: Re: [PATCH v3 00/11] firewire-sbp-target: FireWire SBP-2 SCSI target On Tue, 2012-04-17 at 11:48 +0100, Chris Boot wrote: > On 14/04/2012 02:23, Nicholas A. Bellinger wrote: <SNIP> > > I was eager to see this change, so I decided to go ahead and do the > > mechanical conversion myself in the following branch: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/nab/lio-core.git sbp-merge > > > > As mentioned, it converts drivers/target/sbp/ to use a single sbp_target.[c,h] > > source/header file following mainline convention for new target fabric > > drivers. Also make as many functions as possible statically defined and > > add inline prototypes where necessary. > > > > This patch also renames the sbp-target config entry from: > > > > FIREWIRE_SBP_TARGET -> SBP_TARGET > > > > and also renames the final generated module name from: > > > > fireware-sbp-target.ko -> sbp_target.ko > > Nick, > > I only just noticed this, but it looks like your merge lost my changed > to the MAINTAINERS file. Want me to send a fixup patch? > Whoops, sorry about that Chris. I'll be sure to get this fixed up in the next target-pending update. Thanks! --nab -- 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