From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Amerigo Wang <amwang@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Herbert Xu <herbert@gondor.hengli.com.au>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/4] kmap_atomic: remove the second parameter
Date: Mon, 31 Jan 2011 10:56:06 +0100 [thread overview]
Message-ID: <1296467766.15234.342.camel@laptop> (raw)
In-Reply-To: <1296380820-8801-1-git-send-email-amwang@redhat.com>
On Sun, 2011-01-30 at 17:46 +0800, Amerigo Wang wrote:
>
> Now the second parameter of kmap_atomic() are totally unused,
> this patch removes it from all callers.
>
> Most of this patch is generated by the following commands:
>
> find . -name '*.[c|h]' -exec sed -i -e 's#\bkmap_atomic(\(.*\),.*)#kmap_atomic(\1)#' '{}' \;
> find . -name '*.[c|h]' -exec sed -i -e 's#\bkunmap_atomic(\(.*\),.*)#kunmap_atomic(\1)#' '{}' \;
>
> However, there are some exceptions:
>
> 1) When the second parameter of kmap_atomic() is a variable
> 2) When the second parameter of kmap_atomic() is not in the same line
>
> For 1), they are mostly in btrfs and crypto code, have to fix
> one by one;
> For 2), I fixed them by hands too.
>
> This patch passes 'make allyesconfig' test on both i386 and x86_64.
Right, I had a mostly scripted patch like this as well, IIRC akpm didn't
particularly like the huge patch (in part because it was a flag day
thing).
Maybe cut the patch into slightly smaller bits, like arch/asm,
drivers/gpu, fs/btrfs etc..
prev parent reply other threads:[~2011-01-31 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 9:46 [PATCH 1/4] kmap_atomic: remove the second parameter Amerigo Wang
2011-01-30 9:46 ` [PATCH 2/4] kmap_atomic: remove dead code in ieee80211 staging code Amerigo Wang
2011-01-30 9:46 ` [PATCH 3/4] kmap_atomic: Remove some function parameters of enum km_type Amerigo Wang
2011-01-30 9:47 ` [PATCH 4/4] kmap_atomic: remove KM_* types except KM_TYPE_NR Amerigo Wang
2011-01-30 10:33 ` [PATCH 1/4] kmap_atomic: remove the second parameter Marcin Slusarz
2011-01-31 2:24 ` Cong Wang
2011-01-31 9:56 ` Peter Zijlstra [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=1296467766.15234.342.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-kernel@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