public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michał Nazarewicz" <m.nazarewicz@samsung.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Alan Stern <stern@rowland.harvard.edu>
Cc: linux-kernel@vger.kernel.org,
	Andy Shevchenko <ext-andriy.shevchenko@nokia.com>,
	David Brownell <dbrownell@users.sourceforge.net>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	linux-usb@vger.kernel.org
Subject: Re: [PATCHv4 1/2] usb: gadget: storage: strict coversion of 'ro' parameter
Date: Thu, 22 Jul 2010 16:17:34 +0200	[thread overview]
Message-ID: <op.vf80nklo7p4s8u@pikus> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1007221002510.1725-100000@iolanthe.rowland.org>

> On Thu, 22 Jul 2010, Andy Shevchenko wrote:
>> @@ -735,8 +735,8 @@ static ssize_t fsg_store_ro(struct device *dev, struct device_attribute *attr,
>>  		LDBG(curlun, "read-only status change prevented\n");
>>  		rc = -EBUSY;
>>  	} else {
>> -		curlun->ro = !!i;
>> -		curlun->initially_ro = !!i;
>> +		curlun->ro = ro;
>> +		curlun->initially_ro = ro;
>>  		LDBG(curlun, "read-only status set to %d\n", curlun->ro);
>>  	}
>>  	up_read(filesem);

On Thu, 22 Jul 2010 16:07:14 +0200, Alan Stern <stern@rowland.harvard.edu> wrote:
> Strictly speaking, this changes the behavior when a non-binary value is
> specified.  For example, if somebody were to write "10" then the old
> code would set the value to True and the new code would set the value
> to False -- and neither would reject it as they probably should.
> That's okay; people who write ambiguous or invalid values deserve what
> they get.

If anyone considers that an issue, it would be solved by:

+		curlun->ro = !!ro;
+		curlun->initially_ro = !!ro;

The "!!" where there for that purpose in the first place.

-- 
Best regards,                                        _     _
| Humble Liege of Serenely Enlightened Majesty of  o' \,=./ `o
| Computer Science,  Michał "mina86" Nazarewicz       (o o)
+----[mina86*mina86.com]---[mina86*jabber.org]----ooO--(_)--Ooo--

  reply	other threads:[~2010-07-22 14:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-13  8:36 [PATCH] usb: gadget: storage: optional SCSI WRITE FUA bit Andy Shevchenko
2010-07-13 14:09 ` Alan Stern
2010-07-14  9:05   ` [PATCHv2] " Andy Shevchenko
2010-07-14 12:38     ` Michał Nazarewicz
2010-07-14 13:44       ` Andy Shevchenko
2010-07-14 13:55         ` Roger Quadros
2010-07-16  7:54           ` Felipe Balbi
2010-07-16  8:38             ` Roger Quadros
2010-07-14 14:24         ` Michał Nazarewicz
2010-07-14 15:05           ` Andy Shevchenko
2010-07-14 17:12             ` Michał Nazarewicz
2010-07-15  9:07           ` [PATCHv3 1/2] usb: gadget: storage: strict coversion of 'ro' parameter Andy Shevchenko
2010-07-15  9:07             ` [PATCHv3 2/2] usb: gadget: storage: optional SCSI WRITE FUA bit Andy Shevchenko
2010-07-21 19:17               ` Greg KH
2010-07-22  8:58                 ` [PATCHv4 1/2] usb: gadget: storage: strict coversion of 'ro' parameter Andy Shevchenko
2010-07-22  8:58                   ` [PATCHv4 2/2] usb: gadget: storage: optional SCSI WRITE FUA bit Andy Shevchenko
2010-07-22 14:13                     ` Alan Stern
2010-07-22 14:27                       ` Andy Shevchenko
2010-07-22 14:53                       ` [PATCHv5] " Andy Shevchenko
2010-07-22 14:07                   ` [PATCHv4 1/2] usb: gadget: storage: strict coversion of 'ro' parameter Alan Stern
2010-07-22 14:17                     ` Michał Nazarewicz [this message]
2010-07-21 19:17             ` [PATCHv3 " Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=op.vf80nklo7p4s8u@pikus \
    --to=m.nazarewicz@samsung.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=dbrownell@users.sourceforge.net \
    --cc=ext-andriy.shevchenko@nokia.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox