linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Tim Small <tim@buttersideup.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EDAC: Remove the i82443bxgx_edac driver
Date: Tue, 28 Aug 2018 10:59:03 +0200	[thread overview]
Message-ID: <20180828085903.GA32231@nazgul.tnic> (raw)
In-Reply-To: <56b161bc-9b5e-63c9-b815-8b3ff8214887@buttersideup.com>

On Mon, Aug 27, 2018 at 08:30:23PM +0100, Tim Small wrote:
> On that basis, I don't see a problem with removing it, but if there's a
> preference for me to fix it, (and if I still have some old hardware
> somewhere that I can test it on), I'll be happy to do that instead.

Well, if you don't have the hardware anymore, fixing it would be moot
and the only thing we can do is remove it. So, the question is, do you
still have a functioning box and you want to waste your time with it?

I mean, this is pentium III, it probably takes forever to build the
latest kernel on it and if it were me, I'd simply buy new hardware.
Because IMO, it is not worth the energy to even power such ancient crap
and waste money on the electricity it is going to consume...

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--

      reply	other threads:[~2018-08-28  9:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-10 14:15 [PATCH] EDAC: i82443bxgx: Fix invalid memory type assignment Takashi Iwai
2018-08-15 15:57 ` Borislav Petkov
2018-08-15 16:01   ` Takashi Iwai
2018-08-15 16:12     ` Borislav Petkov
2018-08-27 16:45       ` [PATCH] EDAC: Remove the i82443bxgx_edac driver Borislav Petkov
2018-08-27 19:30         ` Tim Small
2018-08-28  8:59           ` Borislav Petkov [this message]

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=20180828085903.GA32231@nazgul.tnic \
    --to=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=tim@buttersideup.com \
    --cc=tiwai@suse.de \
    /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).