From: Michal Marek <mmarek@suse.cz>
To: Lionel Debroux <lionel_debroux@yahoo.fr>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>
Subject: Re: [PATCH] scripts/checkpatch.pl: add ata_port_operations to the list of ops that ought to be const.
Date: Thu, 25 Nov 2010 15:59:53 +0100 [thread overview]
Message-ID: <4CEE79E9.1060204@suse.cz> (raw)
In-Reply-To: <684104.78681.qm@smtp127.mail.ukl.yahoo.com>
Added Andy and Joe to CC. Lionel, you should consult the MAINTAINERS
file and/or the get_maintainer.pl script and/or the git history to find
suitable addresses to CC.
Michal
On 8.11.2010 07:29, Lionel Debroux wrote:
> Patch against mainline.
>
> ---
>
> Subject: [PATCH] scripts/checkpatch.pl: add ata_port_operations to the list of ops that ought to be const.
>
> I noticed that many ata_port_operations instances are constified
> by the grsecurity patch, so it may be desirable to reduce the
> introduction of non-const instances through checkpatch.pl.
>
> Signed-off-by: Lionel Debroux <lionel_debroux@yahoo.fr>
> ---
> scripts/checkpatch.pl | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index e3c7fc0..33fab2e 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -2810,6 +2810,7 @@ sub process {
> # check for various ops structs, ensure they are const.
> my $struct_ops = qr{acpi_dock_ops|
> address_space_operations|
> + ata_port_operations|
> backlight_ops|
> block_device_operations|
> dentry_operations|
prev parent reply other threads:[~2010-11-25 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 6:29 [PATCH] scripts/checkpatch.pl: add ata_port_operations to the list of ops that ought to be const Lionel Debroux
2010-11-25 14:59 ` Michal Marek [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=4CEE79E9.1060204@suse.cz \
--to=mmarek@suse.cz \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lionel_debroux@yahoo.fr \
/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