From: Raja R Harinath <harinath@hurrynot.org>
To: linux-kernel@vger.kernel.org
Cc: linux-arch@vger.kernel.org
Subject: Re: [RFC][PATCH 2/4] mm: stack based kmap_atomic
Date: Mon, 19 Oct 2009 08:38:12 +0530 [thread overview]
Message-ID: <87tyxw13oj.fsf@hariville.hurrynot.org> (raw)
In-Reply-To: <20091008232528.365592989@chello.nl>
Hi,
Peter Zijlstra <a.p.zijlstra@chello.nl> writes:
> @@ -74,7 +76,10 @@ EXPORT_SYMBOL(kmap_atomic);
> void kunmap_atomic(void *kvaddr, enum km_type type)
> {
> unsigned long vaddr = (unsigned long) kvaddr & PAGE_MASK;
> - unsigned int idx = type + KM_TYPE_NR * smp_processor_id();
> + unsigned int idx;
> +
> + type = kmap_atomic_idx_pop();
> + idx = type + KM_TYPE_NR * smp_processor_id();
Maybe you can avoid the 4/4 patch and preserve clean bisects by renaming
the unused parameter here and elsewhere, and introduce the 'type' local
in this patch.
void kunmap_atomic(void *kvaddr, enum km_type unused)
{
...
unsigned int idx, type;
...
}
That way, patch 3/4 will remove a genuinely unused parameter, and thus
remain compile-able.
- Hari
next prev parent reply other threads:[~2009-10-19 3:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 23:22 [RFC][PATCH 0/4] stack based kmap_atomic -v2 Peter Zijlstra
2009-10-08 23:22 ` [RFC][PATCH 1/4] mm: strictly nested kmap_atomic Peter Zijlstra
2009-10-08 23:22 ` [RFC][PATCH 2/4] mm: stack based kmap_atomic Peter Zijlstra
2009-10-19 3:08 ` Raja R Harinath [this message]
2009-10-08 23:22 ` [RFC][PATCH 3/4] mm: remove KM_type argument Peter Zijlstra
2009-10-08 23:22 ` [RFC][PATCH 4/4] mm: remove KM_type argument fallout Peter Zijlstra
2009-10-09 13:05 ` [RFC][PATCH 0/4] stack based kmap_atomic -v2 Peter Zijlstra
2009-10-09 15:10 ` David Howells
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=87tyxw13oj.fsf@hariville.hurrynot.org \
--to=harinath@hurrynot.org \
--cc=linux-arch@vger.kernel.org \
--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
all inboxes | Powered by JetHome®