From owner-freebsd-bugs@FreeBSD.ORG Sat Dec 9 19:52:24 2006 Return-Path: X-Original-To: freebsd-bugs@FreeBSD.org Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1C63B16A403; Sat, 9 Dec 2006 19:52:24 +0000 (UTC) (envelope-from nork@FreeBSD.org) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CD2643CB4; Sat, 9 Dec 2006 19:51:12 +0000 (GMT) (envelope-from nork@FreeBSD.org) Received: from nadesico.ninth-nine.com (nadesico.ninth-nine.com [219.127.74.122]) by sakura.ninth-nine.com (8.13.8/8.13.8/NinthNine) with SMTP id kB9JqFAs041604; Sun, 10 Dec 2006 04:52:16 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Sun, 10 Dec 2006 04:52:15 +0900 From: Norikatsu Shigemura To: Maxim Konovalov Message-Id: <20061210045215.e87a0992.nork@FreeBSD.org> In-Reply-To: <200612091920.kB9JKDFw064827@freefall.freebsd.org> References: <200612091920.kB9JKDFw064827@freefall.freebsd.org> X-Mailer: Sylpheed version 2.3.0beta5 (GTK+ 2.10.6; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (sakura.ninth-nine.com [219.127.74.121]); Sun, 10 Dec 2006 04:52:16 +0900 (JST) Cc: freebsd-bugs@FreeBSD.org, Norikatsu Shigemura Subject: Re: kern/105989: [ciss] kldload ciss(4) didn't work. X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Dec 2006 19:52:24 -0000 On Sat, 9 Dec 2006 19:20:13 GMT Maxim Konovalov wrote: > > > Synopsis: [ciss] kldload ciss(4) didn't work. > > > State-Changed-From-To: open->patched > > > State-Changed-By: maxim > > > State-Changed-When: Thu Nov 30 15:14:52 UTC 2006 > > > State-Changed-Why: > > > Committed to HEAD. Thanks! > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=105989 > > How about MFC to RELENG_6 and RELENG_6_2? > Not sure about RELENG_6_2 but RELENG_6 definitly. I do hope to MFC to RELENG_6_2. Please please contact to re@:-).