public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: khoroshilov@ispras.ru, linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] sm501fb: Silence a coccinelle script warning.
Date: Thu, 15 Jun 2017 04:26:17 +0000	[thread overview]
Message-ID: <be213113-de88-387b-e9b0-e85b556af1f2@wanadoo.fr> (raw)
In-Reply-To: <3551083.sIQ6JeN0q9@amdc3058>

Le 14/06/2017 à 12:54, Bartlomiej Zolnierkiewicz a écrit :
> Hi,
>
> On Monday, May 08, 2017 08:11:16 AM Christophe JAILLET wrote:
>> According to surrounding goto, it is likely that 'goto err_probed_panel' is
>> expected here.
>> This change is just done in order to silence some coccinelle scripts
>> which try to detect wrongly ordered goto.
>>
>> If 'info->fb[HEAD_PANEL]' and' 'info->fb[HEAD_CRT]' are both NULL, this
>> means that no 'framebuffer_alloc' has been performed, so 'goto err_alloc'
>> looks fine.
>> Anyway, it is also harmless in this case to call 'framebuffer_release'.
>> The code looks more straight forward.
>>
>> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> It seems that the code for supporting only selected framebuffers
> (only HEAD_PANEL fb or only HEAD_CRT fb) is broken anyway as at least
> the suspend/resume support assumes that both framebuffers are always
> present. Also all sm501fb driver users always try try to initialize
> both framebuffers. Therefore I would prefer the removal of non-working
> individual framebuffers support (the code that your patch modifies
> would be removed as well). Could you please look into it?
Thx for the feedback, but no, I won't be able to go further.
I don't know the code enough in this area.
Sorry.

Best regards,
CJ

--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-06-15  4:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170508061141epcas3p4d89f8f964dbe8a327de1abf80da94e6a@epcas3p4.samsung.com>
2017-05-08  6:11 ` [PATCH] sm501fb: Silence a coccinelle script warning Christophe JAILLET
2017-06-14 10:54   ` Bartlomiej Zolnierkiewicz
2017-06-15  4:26     ` Christophe JAILLET [this message]
2017-06-20 21:41     ` Sudip Mukherjee

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=be213113-de88-387b-e9b0-e85b556af1f2@wanadoo.fr \
    --to=christophe.jaillet@wanadoo.fr \
    --cc=b.zolnierkie@samsung.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=khoroshilov@ispras.ru \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@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