From: Alessandro Rubini <rubini@gnudd.com>
To: paul.gortmaker@windriver.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fmc: don't include moduleparam.h in include/linux header files.
Date: Fri, 9 Sep 2016 16:55:17 +0200 [thread overview]
Message-ID: <20160909145517.GA11698@mail.gnudd.com> (raw)
In-Reply-To: <20160909142701.14057-1-paul.gortmaker@windriver.com>
> So move the include to the one and only driver to use these macros and
> ensure we keep setting the proper example in include/linux headers.
>
> Cc: Alessandro Rubini <rubini@gnudd.com>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Thanks.
Acked-by: Alessandro Rubini <rubini@gnudd.com>
prev parent reply other threads:[~2016-09-09 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 14:27 Paul Gortmaker
2016-09-09 14:55 ` Alessandro Rubini [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=20160909145517.GA11698@mail.gnudd.com \
--to=rubini@gnudd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.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
Powered by JetHome