From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1754116AbdK2KIB (ORCPT <rfc822;w@1wt.eu>);
        Wed, 29 Nov 2017 05:08:01 -0500
Received: from mail.linuxfoundation.org ([140.211.169.12]:55542 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1754078AbdK2KHf (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 29 Nov 2017 05:07:35 -0500
Date: Wed, 29 Nov 2017 11:07:36 +0100
From: Greg KH <gregkh@linuxfoundation.org>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: keescook@chromium.org, mfuzzey@parkeon.com, zohar@linux.vnet.ibm.com,
        dhowells@redhat.com, pali.rohar@gmail.com, tiwai@suse.de,
        arend.vanspriel@broadcom.com, zajec5@gmail.com, nbroeking@me.com,
        markivx@codeaurora.org, stephen.boyd@linaro.org, broonie@kernel.org,
        dmitry.torokhov@gmail.com, dwmw2@infradead.org,
        torvalds@linux-foundation.org, Abhay_Salunke@dell.com,
        bjorn.andersson@linaro.org, jewalt@lgsinnovations.com,
        linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/5] firmware: few fixes for v4.15
Message-ID: <20171129100736.GA12411@kroah.com>
References: <20171120174535.27000-1-mcgrof@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20171120174535.27000-1-mcgrof@kernel.org>
User-Agent: Mutt/1.9.1 (2017-09-22)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, Nov 20, 2017 at 09:45:30AM -0800, Luis R. Rodriguez wrote:
> Greg,
> 
> Here's a few fixes that I came up with over the weekend for the
> firmware loader while doing some other development. I realize we
> have a short merge window this time due to the upcoming holidays,
> so I understand if its too late, but considering they are simple
> fixes I figured I'd let you decide if this should wait for v4.16
> or be folded in for v4.15. The fixes are not critical as its
> very improbably you'll run into issues with them. The code
> folding helps make the fixes easier to manage and read.
> 
> I let 0-day test over the weekend and no build issues were found.

As these don't fix any reported issues, I'll just queue them up for
4.16-rc1.

thanks,

greg k-h