From: rkuo@codeaurora.org
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Richard Kuo <rkuo@codeaurora.org>,
Jonas Bonn <jonas@southpole.se>,
linux-hexagon@vger.kernel.org, linux@lists.openrisc.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch: remove CONFIG_GENERIC_FIND_NEXT_BIT again
Date: Mon, 25 Mar 2013 19:53:37 -0700 [thread overview]
Message-ID: <ed19f23c22d5a92cda8e3622060bed61.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <1363872898.1390.143.camel@x61.thuisdomein>
> CONFIG_GENERIC_FIND_NEXT_BIT was removed in v3.0, but reappeared in two
> architectures. Remove it again.
>
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> ---
> 0) Untested.
>
> 1) See commit 63e424c84429903c92a0f1e9654c31ccaf6694d0 ("arch: remove
> CONFIG_GENERIC_FIND_{NEXT_BIT,BIT_LE,LAST_BIT}") for the removal of this
> Kconfig symbol.
>
> 2) Sent as one patch. Feel free to tell me to split it up in two
> patches.
>
> arch/hexagon/Kconfig | 3 ---
> arch/openrisc/Kconfig | 3 ---
> 2 files changed, 6 deletions(-)
>
I'd be fine pulling these into my tree to go with my next batch of
changes, or the OpenRISC folks can if they want. Ack would be nice.
Just in case:
Acked-by: Richard Kuo <rkuo@codeaurora.org>
Thanks,
Richard Kuo
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-03-26 2:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 13:34 [PATCH] arch: remove CONFIG_GENERIC_FIND_NEXT_BIT again Paul Bolle
2013-03-26 2:53 ` rkuo [this message]
2013-03-28 15:04 ` Jonas Bonn
2013-03-30 9:06 ` [PATCH] [RESEND] " Paul Bolle
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=ed19f23c22d5a92cda8e3622060bed61.squirrel@www.codeaurora.org \
--to=rkuo@codeaurora.org \
--cc=jonas@southpole.se \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@lists.openrisc.net \
--cc=pebolle@tiscali.nl \
/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).