[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1541767068-3432-1-git-send-email-suraj1998@gmail.com>
Date: Fri, 9 Nov 2018 18:07:48 +0530
From: Suraj Singh <suraj1998@...il.com>
To: davem@...emloft.net
Cc: kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
suraj1998@...il.com
Subject: Re: net: ipv4: tcp_vegas
Hi,
I'm extremely sorry if I have seemed unresponsive to you but it took me a
while to figure out how to respond to threads using the corresponding mail
-id. I think the first two comments that you wrote on my initial patch with
message-id: 1541425985-31869-1-git-send-email-suraj1998@...il.com were being
redirected to my spam folder and since I didn't have mutt configured
then, I didn't see them,
The reason I've been prefixing all the subject of my mails with "staging: "
is because I was following Greg Kroah-Hartman's YouTube video on how to
submit your first kernel patch. I didn't realise the significance of using
it and didn't take the time out to understand what it really meant and that
is my bad. I've got clarifications for the same in comments to the patch with
message-id: 1541670377-17483-1-git-send-email-suraj1998@...il.com
I think what I will do is first figure out how to use mutt effectively before
sending subsequent patches and emails because all the emails that I have sent
(including this one), I've done so by manually writing git send-mail commands
in response to the corresponding message-id.
Other than unwarranted "staging: " in the subject, are there any other changes
that need to be made before I submit [v3] of the second tcp_westwood patch
(1541670377-17483-1-git-send-email-suraj1998@...il.com)?
Regards,
Suraj
Powered by blists - more mailing lists