All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: f.fainelli@gmail.com
Cc: netdev@vger.kernel.org, andrew@lunn.ch, pthombar@cadence.com,
	hkallweit1@gmail.com
Subject: Re: [PATCH net] Documentation: networking: Update netdev-FAQ regarding patches
Date: Mon, 18 Mar 2019 20:10:14 -0700 (PDT)	[thread overview]
Message-ID: <20190318.201014.1078741662733171222.davem@davemloft.net> (raw)
In-Reply-To: <20190318180733.31333-1-f.fainelli@gmail.com>

From: Florian Fainelli <f.fainelli@gmail.com>
Date: Mon, 18 Mar 2019 11:07:33 -0700

> Provide an explanation of what is expected with respect to sending new
> versions of specific patches within a patch series, as well as what
> happens if an earlier patch series accidentally gets merged).
> 
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>

Applied, thanks Florian.

      reply	other threads:[~2019-03-19  3:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 18:07 [PATCH net] Documentation: networking: Update netdev-FAQ regarding patches Florian Fainelli
2019-03-19  3:10 ` David Miller [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=20190318.201014.1078741662733171222.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andrew@lunn.ch \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pthombar@cadence.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.