Date: Mon, 25 May 2015 02:31:09 +0000 (GMT) From: jenkins-admin@freebsd.org To: gonzo@FreeBSD.org, rodrigc@FreeBSD.org, ngie@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-current@freebsd.org Subject: FreeBSD_HEAD_amd64_gcc4.9 - Build #19 - Fixed Message-ID: <1615505720.59.1432521070110.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <1829450674.55.1432508914721.JavaMail.jenkins@jenkins-9.freebsd.org> References: <1829450674.55.1432508914721.JavaMail.jenkins@jenkins-9.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
FreeBSD_HEAD_amd64_gcc4.9 - Build #19 - Fixed: Check console output at https://jenkins.freebsd.org/job/FreeBSD_HEAD_amd64_gcc4.9/19/ to view the results. From owner-freebsd-current@FreeBSD.ORG Mon May 25 12:30:35 2015 Return-Path: <owner-freebsd-current@FreeBSD.ORG> Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 760BFBFF; Mon, 25 May 2015 12:30:35 +0000 (UTC) (envelope-from jenkins-admin@freebsd.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 653D1D3D; Mon, 25 May 2015 12:30:35 +0000 (UTC) (envelope-from jenkins-admin@freebsd.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id DB65155B; Mon, 25 May 2015 12:30:32 +0000 (UTC) Date: Mon, 25 May 2015 12:30:29 +0000 (GMT) From: jenkins-admin@freebsd.org To: jenkins-admin@FreeBSD.org, freebsd-current@freebsd.org Message-ID: <220719432.61.1432557030532.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <64154000.57.1432515549964.JavaMail.jenkins@jenkins-9.freebsd.org> References: <64154000.57.1432515549964.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_HEAD-tests - Build #1057 - Fixed MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_HEAD-tests X-Jenkins-Result: SUCCESS Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 25 May 2015 12:30:35 -0000 FreeBSD_HEAD-tests - Build #1057 - Fixed: Check console output at https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1057/ to view the results. From owner-freebsd-current@FreeBSD.ORG Mon May 25 14:37:52 2015 Return-Path: <owner-freebsd-current@FreeBSD.ORG> Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DABFFC48 for <freebsd-current@freebsd.org>; Mon, 25 May 2015 14:37:52 +0000 (UTC) (envelope-from kda@semihalf.com) Received: from mail-lb0-f178.google.com (mail-lb0-f178.google.com [209.85.217.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 95540F99 for <freebsd-current@freebsd.org>; Mon, 25 May 2015 14:37:52 +0000 (UTC) (envelope-from kda@semihalf.com) Received: by lbcmx3 with SMTP id mx3so52868119lbc.1 for <freebsd-current@freebsd.org>; Mon, 25 May 2015 07:37:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=wxpajy7MyrVWuUW1z75JGzFh/3EZ3AO/5u199GpZNp0=; b=HLL87on6wzN2d4HhJ1dFFrnlhbAAAx7Brnw+6pZHQAMW0rnZejly1pF7fOEfvpDhRE 519h+kn7RWZPyXm1aszoPXrD5oHJc1ZD9gQ8VyRKXtzdYxl7FjPWpE1AYhEQyRzNINCy QnqiL36ZgNIbR/qtOmN5o0z1rq7BYr0VlCTBdgDQU8YOCqUFsb3PoyMFyGIebOxjhzsN SL55JGe1+j7LugXNzF1YbFvAYgK+uFqzLLznsvcasGuYP6SaqWq0MV9HLV/fFUgUX6kx z8hluAHXIirPesvrDyGkTHLPCKwpTlKI/NSPIXup9fIQebTneKO8rwlX6c6nsUBhQzdm qkTw== X-Gm-Message-State: ALoCoQm1u+ZbH9QIUO0oFzQ5qRMwkilZYLUG4qKCnfCkW4nvJlqlVQuquIBqYu+ozDDSa+jors8H MIME-Version: 1.0 X-Received: by 10.112.125.33 with SMTP id mn1mr18349472lbb.82.1432564663933; Mon, 25 May 2015 07:37:43 -0700 (PDT) Received: by 10.152.117.138 with HTTP; Mon, 25 May 2015 07:37:43 -0700 (PDT) Date: Mon, 25 May 2015 16:37:43 +0200 Message-ID: <CALVGJW+SW13GOskkP9-mmNys03Cv3rVXq34Qr-116=NZwR_FHA@mail.gmail.com> Subject: Vendor code grouping From: =?UTF-8?Q?Stanis=C5=82aw_Kardach?= <kda@semihalf.com> To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 25 May 2015 14:37:52 -0000 Hi, I'm currently working on a device driver port and given its architecture I would need to add some vendor maintained code to vendor-sys. In this particular case I know that there is some code from this vendor (Cavium) already present in vendor-sys (namely octeon-sdk). It deals with the same hardware as my driver but from a different perspective. The octeon-sdk works with Octeon processor as a FreeBSD host whereas the code I have to put into vendor-sys (let's call it cnnic-sdk) works from a device perspective (Octeon is a PCIe target). Normally I would assume that the correct place to put the new vendor code would be a new directory (i.e. vendor-sys/cnnic-sdk/dist), however in this case I was thinking whether it would make sense (and/or is allowed) to group those two pieces of software as sub-directories of a single vendor directory: "cavium"? If I'm not mistaken there is already something similar done with vendor/NetBSD but each "sub-project" lives inside the same repository (in dist). In my case I would like to have the two Octeon related projects in separate repositories as they are developed and updated separately. At the same time I don't want to re-invent the wheel or do something not in FreeBSD spirit of work. So to sum things up what would make the most sense: 1. Put my vendor code into a new directory in vendor-sys (i.e. vendor-sys/cnnic-sdk/dist), 2. Create vendor-sys/cavium and put octeon-sdk into vendor-sys/cavium/octeon-sdk/dist and my code into vendor-sys/cavium/cnnic-sdk/dist, 3. Create vendor-sys/cavium/dist and put octeon-sdk into vendor-sys/cavium/dist/octeon-sdk and my code into vendor-sys/cavium/dist/cnnic-sdk? Thanks in advance for Your help! -- Best Regards, Stanis=C5=82aw Kardach
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1615505720.59.1432521070110.JavaMail.jenkins>