From: David Miller <davem@davemloft.net>
To: clabbe.montjoie@gmail.com
Cc: 3chas3@gmail.com, linux-atm-general@lists.sourceforge.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] atm: fore200e: Do not drop const qualifier
Date: Thu, 18 Aug 2016 23:50:42 -0700 (PDT) [thread overview]
Message-ID: <20160818.235042.671072416951678843.davem@davemloft.net> (raw)
In-Reply-To: <1471442205-11364-1-git-send-email-clabbe.montjoie@gmail.com>
From: LABBE Corentin <clabbe.montjoie@gmail.com>
Date: Wed, 17 Aug 2016 15:56:45 +0200
> The data member of structure firmware is const and this constness is
> dropped by some cast.
> This patch add some const for keeping the const information.
>
> Signed-off-by: LABBE Corentin <clabbe.montjoie@gmail.com>
Applied.
prev parent reply other threads:[~2016-08-19 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 13:56 [PATCH] atm: fore200e: Do not drop const qualifier LABBE Corentin
2016-08-19 6:50 ` 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=20160818.235042.671072416951678843.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=3chas3@gmail.com \
--cc=clabbe.montjoie@gmail.com \
--cc=linux-atm-general@lists.sourceforge.net \
--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).