Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762574AbYALVVg (ORCPT ); Sat, 12 Jan 2008 16:21:36 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758231AbYALVV2 (ORCPT ); Sat, 12 Jan 2008 16:21:28 -0500 Received: from ug-out-1314.google.com ([66.249.92.171]:21558 "EHLO ug-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757773AbYALVV1 (ORCPT ); Sat, 12 Jan 2008 16:21:27 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=QP9PdGUM2T+lr1AEHqbxFWMwx1XDbzCxY3Cjy/5fyZkEVhij9qw7G8bLfBvoxmVFHtBxnBcXJm3lLw1yeKJq84lMvnDzm5DiXGa5jG4VmDH0KwfxQxBFRuidMQ5HnU9PDabNPFM7e7blviGjUq3viqjE5vix0XC52Tu+h7jdQLo= From: Bartlomiej Zolnierkiewicz To: bbpetkov@yahoo.de Subject: Re: [PATCH 06/21] ide-floppy: remove struct idefloppy_flexible_disk_page Date: Sat, 12 Jan 2008 22:32:48 +0100 User-Agent: KMail/1.9.6 (enterprise 0.20071123.740460) Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org References: <1200052699-28420-1-git-send-email-bbpetkov@yahoo.de> <200801120158.57895.bzolnier@gmail.com> <20080112203848.GA31954@gollum.tnic> In-Reply-To: <20080112203848.GA31954@gollum.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801122232.48382.bzolnier@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2654 Lines: 55 On Saturday 12 January 2008, Borislav Petkov wrote: [...] > > > set_disk_ro(floppy->disk, floppy->wp); > > > - page = (idefloppy_flexible_disk_page_t *) (header + 1); > > > - > > > - page->transfer_rate = be16_to_cpu(page->transfer_rate); > > > - page->sector_size = be16_to_cpu(page->sector_size); > > > - page->cyls = be16_to_cpu(page->cyls); > > > - page->rpm = be16_to_cpu(page->rpm); > > > - capacity = page->cyls * page->heads * page->sectors * page->sector_size; > > > - if (memcmp (page, &floppy->flexible_disk_page, sizeof (idefloppy_flexible_disk_page_t))) > > > + > > > + transfer_rate = be16_to_cpu(*(u16 *)&pc.buffer[8 + 2]); > > > + sector_size = be16_to_cpu(*(u16 *)&pc.buffer[8 + 6]); > > > + cyls = be16_to_cpu(*(u16 *)&pc.buffer[8 + 8]); > > > + rpm = be16_to_cpu(*(u16 *)&pc.buffer[8 + 28]); > > > + heads = pc.buffer[8 + 4]; > > > + sectors = pc.buffer[8 + 5]; > > > + > > > + capacity = cyls * heads * sectors * sector_size; > > > + > > > + if ((1UL << IDEFLOPPY_MEDIA_CHANGED) & floppy->flags) > > > > IDEFLOPPY_MEDIA_CHANGED is set when block device is opened for the first > > time (please check idefloppy_open() for details) so I don't think it is > > the right change. 'Flexible Disk Page' is only 32 bytes so we are better > > off with leaving 'u8 flexible_disk_page[32]' in idefloppy_floppy_t and > > doing things the old way. > > > > Besides please do not intermix real changes like the above one with purely > > cleanup ones like idefloppy_flexible_disk_page_t removal. This is bad from > > maintainability point of view. If some patch causes problems it is easier > > to narrow it down by heaving purely cleanup changes separated out + if we > > would need to revert the real change we would have to make a separate patch > > doing it instead of just reverting the guilty commit (given that we don't > > want cleanup changes to be reverted as well). > > How about we get rid of that chunk altogether? floppy->flexible_disk_page is > used only here for the purpose of printk-ing to the syslog and has no "real" > purpose otherwise. Do we need that info spewed into the syslog at all? Well, it has some debugging value since drive's capabilities are given in 'Flexible Disk Page' but fine with me given that this change is separated out from idefloppy_flexible_disk_page_t removal and pushed at the end of patch series. Thanks, Bart -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/