All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Salter <msalter@redhat.com>
To: Chris Metcalf <cmetcalf@tilera.com>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Kconfig cleanup (PARPORT_PC dependencies)
Date: Thu, 12 Sep 2013 15:19:44 -0400	[thread overview]
Message-ID: <1379013584.14495.4.camel@deneb.redhat.com> (raw)
In-Reply-To: <52321022.6060907@tilera.com>

On Thu, 2013-09-12 at 15:04 -0400, Chris Metcalf wrote:
> On 9/12/2013 2:53 PM, Mark Salter wrote:
> > Remove messy dependencies from PARPORT_PC by having it depend on one
> > Kconfig symbol (ARCH_MAY_HAVE_PC_PARPORT) and having architectures
> > which need it declare ARCH_MAY_HAVE_PC_PARPORT in arch/*/Kconfig.
> > New architectures are unlikely to need PARPORT_PC, so this avoids
> > having an ever growing list of architectures to exclude. Those
> > architectures which do declare ARCH_MAY_HAVE_PC_PARPORT in this
> > patch are the ones which have an asm/parport.h.
> >
> > Signed-off-by: Mark Salter <msalter@redhat.com>
> 
> You can actually omit the arch/tile change, since as far as I know there's no way for tile to have PARPORT_PC.
> 

Yeah, I thought that the list of architectures in the patch would end up
being a superset of what was really needed. Especially for those which
used the generic parport.h. I can drop tile from this patch but you may
want to get rid of the parport.h from arch/tile/include/asm/Kbuild.

  reply	other threads:[~2013-09-12 19:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-12 18:53 [PATCH] Kconfig cleanup (PARPORT_PC dependencies) Mark Salter
2013-09-12 19:04 ` Chris Metcalf
2013-09-12 19:04   ` Chris Metcalf
2013-09-12 19:19   ` Mark Salter [this message]
2013-09-12 19:11 ` Geert Uytterhoeven
2013-09-12 19:13 ` Richard Henderson
2013-09-12 20:07 ` H. Peter Anvin
2013-09-12 20:53   ` Ingo Molnar
2013-09-12 20:55     ` H. Peter Anvin
2013-09-12 20:32 ` Sam Ravnborg
2013-09-12 20:49   ` Russell King - ARM Linux
2013-09-12 21:21   ` Mark Salter
2013-09-13 16:40     ` Sam Ravnborg

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=1379013584.14495.4.camel@deneb.redhat.com \
    --to=msalter@redhat.com \
    --cc=cmetcalf@tilera.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.