From: David Miller <davem@davemloft.net>
To: Julia.Lawall@lip6.fr
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 0/3] constify net_device_ops structures
Date: Sat, 17 Sep 2016 10:07:56 -0400 (EDT) [thread overview]
Message-ID: <20160917.100756.290979316447041668.davem@davemloft.net> (raw)
In-Reply-To: <1473971006-2074-1-git-send-email-Julia.Lawall@lip6.fr>
From: Julia Lawall <Julia.Lawall@lip6.fr>
Date: Thu, 15 Sep 2016 22:23:23 +0200
> Constify net_device_ops structures.
All applied, thanks.
prev parent reply other threads:[~2016-09-17 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 20:23 [PATCH 0/3] constify net_device_ops structures Julia Lawall
2016-09-15 20:23 ` [PATCH 1/3] hisilicon: " Julia Lawall
2016-09-15 20:23 ` [PATCH 2/3] dwc_eth_qos: " Julia Lawall
2016-09-15 20:23 ` [PATCH 3/3] l2tp: " Julia Lawall
2016-09-17 14:07 ` 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=20160917.100756.290979316447041668.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Julia.Lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).