linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH] video/fbdev: refactor video= cmdline parsing
Date: Wed, 23 Jan 2019 11:12:59 +0000	[thread overview]
Message-ID: <87ef9339vo.fsf@intel.com> (raw)
In-Reply-To: <20190123105830.GF3271@phenom.ffwll.local>

On Wed, 23 Jan 2019, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Jan 23, 2019 at 11:38:17AM +0200, Jani Nikula wrote:
>> Make the video_setup() function slightly easier to read by removing the
>> repeated checks for !global. Remove the misleading return value comment
>> while at it.
>> 
>> I'm slightly hesitant to change any of this, but here goes anyway, with
>> hopes that the next person to have to look at this has it a wee bit
>> easier.
>> 
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>

Thanks.

Just to be clear, I expect Bartlomiej to queue this via the fb tree
(provided he agrees with the change, of course).

BR,
Jani.


>
>> ---
>>  drivers/video/fbdev/core/fb_cmdline.c | 23 ++++++++++-------------
>>  1 file changed, 10 insertions(+), 13 deletions(-)
>> 
>> diff --git a/drivers/video/fbdev/core/fb_cmdline.c b/drivers/video/fbdev/core/fb_cmdline.c
>> index 39509ccd92f1..3b5bd666b952 100644
>> --- a/drivers/video/fbdev/core/fb_cmdline.c
>> +++ b/drivers/video/fbdev/core/fb_cmdline.c
>> @@ -75,36 +75,33 @@ EXPORT_SYMBOL(fb_get_options);
>>   *	NOTE: This function is a __setup and __init function.
>>   *            It only stores the options.  Drivers have to call
>>   *            fb_get_options() as necessary.
>> - *
>> - *	Returns zero.
>> - *
>>   */
>>  static int __init video_setup(char *options)
>>  {
>> -	int i, global = 0;
>> -
>>  	if (!options || !*options)
>> -		global = 1;
>> +		goto out;
>>  
>> -	if (!global && !strncmp(options, "ofonly", 6)) {
>> +	if (!strncmp(options, "ofonly", 6)) {
>>  		ofonly = 1;
>> -		global = 1;
>> +		goto out;
>>  	}
>>  
>> -	if (!global && !strchr(options, ':')) {
>> -		fb_mode_option = options;
>> -		global = 1;
>> -	}
>> +	if (strchr(options, ':')) {
>> +		/* named */
>> +		int i;
>>  
>> -	if (!global) {
>>  		for (i = 0; i < FB_MAX; i++) {
>>  			if (video_options[i] = NULL) {
>>  				video_options[i] = options;
>>  				break;
>>  			}
>>  		}
>> +	} else {
>> +		/* global */
>> +		fb_mode_option = options;
>>  	}
>>  
>> +out:
>>  	return 1;
>>  }
>>  __setup("video=", video_setup);
>> -- 
>> 2.20.1
>> 
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2019-01-23 11:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23  9:38 [PATCH] video/fbdev: refactor video= cmdline parsing Jani Nikula
2019-01-23 10:58 ` Daniel Vetter
2019-01-23 11:12   ` Jani Nikula [this message]
2019-02-08 17:31     ` Bartlomiej Zolnierkiewicz

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=87ef9339vo.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).