linux-hexagon.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Richard Kuo <rkuo@codeaurora.org>
Cc: linux-hexagon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Hexagon: Remove useless select of NO_IOPORT_MAP
Date: Thu, 25 Sep 2014 12:11:42 +0200	[thread overview]
Message-ID: <1411639902.7866.2.camel@x220> (raw)
In-Reply-To: <1411586511.19525.38.camel@x220>

On Wed, 2014-09-24 at 21:21 +0200, Paul Bolle wrote:
> Actually, the only difference I found in the .config file was that after
> this patch the .config file contained
>     CONFIG_HEXAGON=y
> 
> I have no idea why. Did I botch my test?

Apparently I did. Retested using next-20140925. There's no difference in
the .config file before and after the patch. That's a good thing! This
select really is useless.


Paul Bolle

  reply	other threads:[~2014-09-25 10:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24 19:21 [PATCH] Hexagon: Remove useless select of NO_IOPORT_MAP Paul Bolle
2014-09-25 10:11 ` Paul Bolle [this message]
2014-09-30  1:25 ` rkuo

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=1411639902.7866.2.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkuo@codeaurora.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;
as well as URLs for NNTP newsgroup(s).