All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: dri-devel@lists.freedesktop.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] video: fbdev: au1200fb: Fix error handling path of 'au1200fb_drv_probe()'
Date: Thu, 9 Nov 2017 20:32:52 +0100	[thread overview]
Message-ID: <ou2ags$v16$1@blaine.gmane.org> (raw)
In-Reply-To: <3843760.j1Dl9T2ZgC@amdc3058>

Le 09/11/2017 à 14:12, Bartlomiej Zolnierkiewicz a écrit :
>
> [...]
> * patch description was changed to silence issues reported by checkpatch.pl:
>
> WARNING: 'succesful' may be misspelled - perhaps 'successful'?
> #4:
> 'au1200fb_drv_probe()' can not fail after a succesful call to
Odd. Even if I can not compile, I checkpatch.pl all patches I send.

> ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 1630d85a8312 ("au1200fb: fix hardcoded IRQ")'
> #9:
> 1630d85a8312 ("au1200fb: fix hardcoded IRQ")
Seen and left as-is. The warning was just because the 'commit' was not 
on the same line of the tag. I didn't think it was important at all.

I guess that I only read the output of this 2nd warning and didn't see 
the first one.


Thanks for the review, correction and acknowledgement.

CJ



_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2017-11-09 19:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20171016190602epcas2p1c54546e982659187188f178846c54531@epcas2p1.samsung.com>
2017-10-16 19:04 ` [PATCH 0/8] video: fbdev: au1200fb: Fix error handling path of 'au1200fb_drv_probe()' Christophe JAILLET
2017-10-16 19:04   ` Christophe JAILLET
2017-10-16 19:04   ` [PATCH 1/8] video: fbdev: au1200fb: Fix a potential double free Christophe JAILLET
2017-10-16 19:04     ` Christophe JAILLET
2017-10-16 19:04   ` [PATCH 2/8] video: fbdev: au1200fb: Return an error code if a memory allocation fails Christophe JAILLET
2017-10-16 19:04     ` Christophe JAILLET
2017-10-16 19:04   ` [PATCH 3/8] video: fbdev: au1200fb: Release some resources " Christophe JAILLET
2017-10-16 19:04     ` Christophe JAILLET
2017-10-16 19:04   ` [PATCH 4/8] video: fbdev: au1200fb: Fix error handling path Christophe JAILLET
2017-10-16 19:04     ` Christophe JAILLET
2017-10-16 19:04   ` [PATCH 5/8] " Christophe JAILLET
2017-10-16 19:04     ` Christophe JAILLET
2017-10-17 10:35     ` walter harms
2017-10-17 10:35       ` walter harms
2017-10-16 19:04   ` [PATCH 6/8] video: fbdev: au1200fb: Remove some dead code Christophe JAILLET
2017-10-16 19:04     ` Christophe JAILLET
2017-10-17 11:33     ` Dan Carpenter
2017-10-17 11:33       ` Dan Carpenter
2017-10-16 19:04   ` [PATCH 7/8] video: fbdev: au1200fb: Propagate an error code Christophe JAILLET
2017-10-16 19:04     ` Christophe JAILLET
2017-10-16 19:04   ` [PATCH 8/8] video: fbdev: au1200fb: Style clean up Christophe JAILLET
2017-10-16 19:04     ` Christophe JAILLET
2017-11-09 13:12   ` [PATCH 0/8] video: fbdev: au1200fb: Fix error handling path of 'au1200fb_drv_probe()' Bartlomiej Zolnierkiewicz
2017-11-09 13:12     ` Bartlomiej Zolnierkiewicz
2017-11-09 13:12     ` Bartlomiej Zolnierkiewicz
2017-11-09 19:32     ` Christophe JAILLET [this message]

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='ou2ags$v16$1@blaine.gmane.org' \
    --to=christophe.jaillet@wanadoo.fr \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.