From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from 63.mail-out.ovh.net ([91.121.185.56]) by bombadil.infradead.org with smtp (Exim 4.72 #1 (Red Hat Linux)) id 1OwbLw-0008HO-2n for barebox@lists.infradead.org; Fri, 17 Sep 2010 13:51:48 +0000 Date: Fri, 17 Sep 2010 15:50:37 +0200 From: Jean-Christophe PLAGNIOL-VILLARD Message-ID: <20100917135037.GB20438@game.jcrosoft.org> References: <1284290860-32033-1-git-send-email-plagnioj@jcrosoft.com> <20100917134530.GD1473@pengutronix.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20100917134530.GD1473@pengutronix.de> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: barebox-bounces@lists.infradead.org Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: [PATCH 1/4] driver: allow register device with specific id To: Sascha Hauer Cc: barebox@lists.infradead.org On 15:45 Fri 17 Sep , Sascha Hauer wrote: > Hi J, > > On Sun, Sep 12, 2010 at 01:27:37PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote: > > if you specify id = 0 the next available id will be taken > > otherwise fail if already registered > > I think we need a better solution here. Being able to specify an id > is a good idea in general, but since 0 is a valid id we should be able > to specify exactly this id aswell. > An idea is to use -1 for a dynamic id, but of course this needs changes > to all existing devices. I prefer to do it a second step in this case Best Regards, J. _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox