From: Dave Jones <davej@redhat.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Douglas Thompson <dougthompson@xmission.com>
Subject: Re: drivers/edac: add mips and ppc visibility
Date: Fri, 20 Jul 2007 15:47:37 -0400 [thread overview]
Message-ID: <20070720194737.GA30184@redhat.com> (raw)
In-Reply-To: <200707191759.l6JHxG4c022643@hera.kernel.org>
On Thu, Jul 19, 2007 at 05:59:16PM +0000, Linux Kernel wrote:
> Gitweb: http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b113a3f7e85d7f97c8383a88a5bc7c2ea8daeb2f
> Commit: b113a3f7e85d7f97c8383a88a5bc7c2ea8daeb2f
> Parent: 052dfb45ccb5ea354a426b52556bcfee75b9d2f5
> Author: Douglas Thompson <dougthompson@xmission.com>
> AuthorDate: Thu Jul 19 01:50:15 2007 -0700
> Committer: Linus Torvalds <torvalds@woody.linux-foundation.org>
> CommitDate: Thu Jul 19 10:04:55 2007 -0700
>
> drivers/edac: add mips and ppc visibility
>
> 1) Remove an old CVS ID string
>
> 2) change EDAC from a tristate option to a simple bool option
>
> 3) In addition to the X86 arch, PPC and MIPS also have drivers in the
> submission queue. This patch turns on the EDAC flag for those archs. Each
> driver will have its respective 'depends on ARCH' set.
>
> Signed-off-by: Douglas Thompson <dougthompson@xmission.com>
> Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
What was the reasoning behind 2) ?
Now everyone's distro kernel has bits of EDAC in it even if they
don't use it. (Admittedly only a small amount, but these things
tend to creep in bit by bit).
Dave
--
http://www.codemonkey.org.uk
next parent reply other threads:[~2007-07-20 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200707191759.l6JHxG4c022643@hera.kernel.org>
2007-07-20 19:47 ` Dave Jones [this message]
2007-07-23 22:29 ` drivers/edac: add mips and ppc visibility Doug Thompson
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=20070720194737.GA30184@redhat.com \
--to=davej@redhat.com \
--cc=dougthompson@xmission.com \
--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.