All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: hardcode value of YACC&LEX for aic7-triple-x
Date: Tue, 01 Aug 2006 15:00:34 -0700	[thread overview]
Message-ID: <44CFCF02.7080400@zytor.com> (raw)
In-Reply-To: <20060730193113.GB31690@mars.ravnborg.org>

Sam Ravnborg wrote:
> Other places in kernel hardcode bison/flex so to be consistent aic7xxx
> does the same.

It would be better if this was centralized.

	-hpa

  reply	other threads:[~2006-08-01 22:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-29  7:15 [PATCH 0/18] kbuild fixes Sam Ravnborg
2006-07-29  7:19 ` [PATCH] kbuild: hardcode value of YACC&LEX for aic7-triple-x sam
2006-07-29  7:19   ` [PATCH] kbuild: version.h and new headers_* targets does not require a kernel config sam
2006-07-29  7:19     ` [PATCH] kbuild: .gitignore utsrelease.h sam
2006-07-29  7:19       ` [PATCH] kbuild: improve error from file2alias sam
2006-07-29  7:19         ` [PATCH] kbuild: fix typo in modpost sam
2006-07-29  7:19           ` [PATCH] kbuild: -fno-stack-protector is not good sam
2006-07-29  7:19             ` [PATCH] kconfig: correct oldconfig for unset choice options sam
2006-07-29  7:19               ` [PATCH] kconfig: support DOS line endings sam
2006-07-29  7:19                 ` [PATCH] kbuild: consistently decide when to rebuild a target sam
2006-07-29  9:07   ` [PATCH] kbuild: hardcode value of YACC&LEX for aic7-triple-x Alexey Dobriyan
2006-07-30 19:31     ` Sam Ravnborg
2006-08-01 22:00       ` H. Peter Anvin [this message]
2006-08-01 22:00     ` H. Peter Anvin

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=44CFCF02.7080400@zytor.com \
    --to=hpa@zytor.com \
    --cc=adobriyan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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.