linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel Ravier <gabravier@gmail.com>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	linux-gpio <linux-gpio@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gpio-hammer: Avoid potential overflow in main
Date: Thu, 12 Mar 2020 15:39:20 +0100	[thread overview]
Message-ID: <ba18951f-abf9-06eb-22a5-3f92d3c89fa2@gmail.com> (raw)
In-Reply-To: <CAMpxmJXUa7rk51XXvLjgueD9i1k98A+5gLx9WowChRb64k1mPQ@mail.gmail.com>

On 3/12/20 3:36 PM, Bartosz Golaszewski wrote:
> czw., 12 mar 2020 o 15:33 Gabriel Ravier <gabravier@gmail.com> napisał(a):
>> Ah, seems like I didn't read the guide to getting code into the kernel
>> thoroughly enough. Should I send the patch yet again just with a v2 in
>> the subject header or is there no need to bother with that ?
>>
> Please do so that patchwork picks it up. Also: please don't top-post
> on LKML ie. respond below others' text.
>
> Bart

Ok, will send it with s/PATCH/PATCH v2 ASAP.

Btw, is the "top-posting" the reason why lkml.org doesn't seem to be 
able to find my replies to your posts ?


      reply	other threads:[~2020-03-12 14:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-12  9:40 [PATCH] gpio-hammer: Avoid potential overflow in main Gabriel Ravier
2020-03-12 13:54 ` Bartosz Golaszewski
2020-03-12 14:21   ` Gabriel Ravier
2020-03-12 14:21     ` Gabriel Ravier
2020-03-12 14:29     ` Bartosz Golaszewski
2020-03-12 14:33       ` Gabriel Ravier
2020-03-12 14:36         ` Bartosz Golaszewski
2020-03-12 14:39           ` Gabriel Ravier [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=ba18951f-abf9-06eb-22a5-3f92d3c89fa2@gmail.com \
    --to=gabravier@gmail.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@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;
as well as URLs for NNTP newsgroup(s).