All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: The development of GNU GRUB <grub-devel@gnu.org>,
	Olaf Hering <olaf@aepfle.de>, Daniel Kiper <dkiper@net-space.pl>
Subject: Re: [PATCH 1/2] build: Fix option to explicitly disable memory debugging
Date: Mon, 9 Mar 2020 13:22:34 +0100	[thread overview]
Message-ID: <20200309122234.GA5843@ncase> (raw)
In-Reply-To: <ed3b287c-2648-1ae4-61b5-518f594d78c7@molgen.mpg.de>

[-- Attachment #1: Type: text/plain, Size: 594 bytes --]

On Mon, Mar 09, 2020 at 12:18:41PM +0100, Paul Menzel wrote:
> Dear Patrick,
> 
> 
> On 2020-03-07 17:29, Patrick Steinhardt wrote:
> > The memory management system supports a debug mode that can be enabled
> > at build time by passing "--enable-mm-debug" to the configure script.
> > Passing the option will cause us define MM_DEBUG as expected, but in
> > fact the reverse option "--disable-mm-deubg" will do the exact same
> 
> s/deubg/debug/

Thanks for pointing this out! Daniel, you want me to send out a v2 of
this to fix the typo or will you fix it up locally?

Patrick

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-03-09 12:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-07 16:29 [PATCH 0/2] build: Fixes for memory-debugging builds Patrick Steinhardt
2020-03-07 16:29 ` [PATCH 1/2] build: Fix option to explicitly disable memory debugging Patrick Steinhardt
2020-03-09 11:09   ` Daniel Kiper
2020-03-09 11:18   ` Paul Menzel
2020-03-09 12:22     ` Patrick Steinhardt [this message]
2020-03-09 12:31       ` Daniel Kiper
2020-03-07 16:29 ` [PATCH 2/2] gnulib: Fix build of base64 when compiling with " Patrick Steinhardt
2020-03-09 11:19   ` Daniel Kiper
2020-03-09 12:01     ` Patrick Steinhardt
2020-03-09 12:14       ` Daniel Kiper

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=20200309122234.GA5843@ncase \
    --to=ps@pks.im \
    --cc=dkiper@net-space.pl \
    --cc=grub-devel@gnu.org \
    --cc=olaf@aepfle.de \
    --cc=pmenzel@molgen.mpg.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 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.