From: Andrew Lunn <andrew@lunn.ch>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Linux kernel netdev mailing list <netdev@vger.kernel.org>
Subject: Re: [PATCH] correct comments for flags, priv flags in netdevice.h
Date: Sat, 25 Aug 2018 02:38:49 +0200 [thread overview]
Message-ID: <20180825003849.GC1999@lunn.ch> (raw)
In-Reply-To: <alpine.LFD.2.21.1808241908260.11448@localhost.localdomain>
On Fri, Aug 24, 2018 at 07:10:20PM -0400, Robert P. J. Day wrote:
> Correct the references for both flags and priv flags since they both
> refer to the incorrect file which contains their explanations.
Hi Robert
I'm guessing this is your first patch for Linux?
Please use git send-email to sending patches. That will avoid the
signature being added, and any other mangling your email client may
do.
The subject line should indicate what tree the patch is for:
[PATCH net-next] correct comments for flags, priv flags in netdevice.h
You can do this with git format-patch --subject "PATCH net-next".
And lastly, net-next is closed at the moment, because the merge window
is open. DaveM will send an email when he is read to accept patches, a
few days after -rc1 is out.
Andrew
prev parent reply other threads:[~2018-08-25 4:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 23:10 [PATCH] correct comments for flags, priv flags in netdevice.h Robert P. J. Day
2018-08-25 0:38 ` Andrew Lunn [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=20180825003849.GC1999@lunn.ch \
--to=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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).