linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: suraj1998@gmail.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: net: ipv4: tcp_vegas
Date: Sun, 11 Nov 2018 09:25:13 -0800 (PST)	[thread overview]
Message-ID: <20181111.092513.1189098747245221056.davem@davemloft.net> (raw)
In-Reply-To: <1541956134-14029-1-git-send-email-suraj1998@gmail.com>

From: Suraj Singh <suraj1998@gmail.com>
Date: Sun, 11 Nov 2018 22:38:54 +0530

> I don't think you've been getting my emails because I've been sending them
> in response to the message-id of my patch. 

I got your email, I'm just too busy to reply.

  reply	other threads:[~2018-11-11 17:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08  8:29 [PATCH] staging: net: ipv4: tcp_vegas: fixed checks and warnings Suraj Singh
2018-11-08 18:34 ` David Miller
2018-11-11 17:08   ` net: ipv4: tcp_vegas Suraj Singh
2018-11-11 17:25     ` David Miller [this message]
2018-11-09 12:37 ` Suraj Singh

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=20181111.092513.1189098747245221056.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=suraj1998@gmail.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 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).