All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vadim Lomovtsev <Vadim.Lomovtsev@caviumnetworks.com>
To: linux-kernel@vger.kernel.org
Cc: vadim.lomovtsev@cavium.com
Subject: [Question] patch posting process
Date: Fri, 6 Apr 2018 11:29:16 -0700	[thread overview]
Message-ID: <20180406182916.GA15772@localhost.localdomain> (raw)

Hi all,

I bring my Apologise for wasting your time, but ..

May I ask for some clarification.. When we're speaking of 'posting patches shortly'
does it mean to send them in next few hours ?
Or would it be more acceptable to post one version per day
even for very small changes in between ?

Kernel posting guides says that one should wait for about a week for respond,
but in my case I've got feedback rather quickly (thanks a lot for that!)
and I'd assume that I can proceed with posting next version.

So, what is the proper approach here - should one wait day or two
before posting next version even if changes are very simple ?

WBR,
Vadim

             reply	other threads:[~2018-04-06 18:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06 18:29 Vadim Lomovtsev [this message]
2018-04-06 19:21 ` [Question] patch posting process Willy Tarreau
2018-04-06 20:00   ` Vadim Lomovtsev

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=20180406182916.GA15772@localhost.localdomain \
    --to=vadim.lomovtsev@caviumnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vadim.lomovtsev@cavium.com \
    /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.