Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Arvind Sankar <nivedita@alum.mit.edu>
Date:   Wed, 19 Feb 2020 12:57:17 -0500
To:     Borislav Petkov <bp@alien8.de>
Cc:     Arvind Sankar <nivedita@alum.mit.edu>,
        Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@redhat.com>,
        "H. Peter Anvin" <hpa@zytor.com>, x86@kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] x86/boot/compressed/64: Remove .bss/.pgtable from
 bzImage
Message-ID: <20200219175717.GA1892094@rani.riverdale.lan>
References: <20200109150218.16544-1-nivedita@alum.mit.edu>
 <20200205162921.GA318609@rani.riverdale.lan>
 <20200218180353.GA930230@rani.riverdale.lan>
 <20200219120938.GB30966@zn.tnic>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20200219120938.GB30966@zn.tnic>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, Feb 19, 2020 at 01:09:38PM +0100, Borislav Petkov wrote:
> 
> You keep pinging. Why? Is it a showstopper or what is the urgency here?
> 
> This is shaving off some 100 - 200 KiB from the final bzImage, AFAICT. Or
> is there something more broken this is fixing?
> 

There isn't any particular urgency (at least until fg-kaslr patches try
to make it 64MiB bigger), but it's unclear how long to wait before
sending a reminder -- Documentation/process suggests that comments
should be received in a week or so, pinging after 4 and 6 weeks seemed
reasonable. If x86 has a longer queue, might be worth documenting that
somewhere?