From: John Garry <john.garry@huawei.com>
To: Olof Johansson <olof@lixom.net>, Wei Xu <xuwei5@hisilicon.com>
Cc: ARM-SoC Maintainers <arm@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Arnd Bergmann <arnd@arndb.de>, Linuxarm <linuxarm@huawei.com>,
"xuwei (O)" <xuwei5@huawei.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
<linux-pci@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Zhangyi ac <zhangyi.ac@huawei.com>,
"Liguozhu (Kenneth)" <liguozhu@hisilicon.com>,
<jinying@hisilicon.com>, huangdaode <huangdaode@hisilicon.com>,
Tangkunshan <tangkunshan@huawei.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
Shiju Jose <shiju.jose@huawei.com>,
Salil Mehta <salil.mehta@huawei.com>
Subject: Re: [GIT PULL] Hisilicon fixes for v5.2
Date: Tue, 25 Jun 2019 14:31:26 +0100 [thread overview]
Message-ID: <7e215bd7-daab-b6cf-8d0f-9513bd7c4f6d@huawei.com> (raw)
In-Reply-To: <CAOesGMj+aNkOT1YVHTSBLkOfEujk7uer3R1AmE-sa1TwCijbBg@mail.gmail.com>
On 25/06/2019 14:03, Olof Johansson wrote:
>>> are available in the Git repository at:
>>> > >
>>> > > git://github.com/hisilicon/linux-hisi.git tags/hisi-fixes-for-5.2
>>> > >
>>> > > for you to fetch changes up to 07c811af1c00d7b4212eac86900b023b6405a954:
>>> > >
>>> > > lib: logic_pio: Enforce LOGIC_PIO_INDIRECT region ops are set at registration (2019-06-25 09:40:42 +0100)
>>> > >
>>> > > ----------------------------------------------------------------
>>> > > Hisilicon fixes for v5.2-rc
>>> > >
>>> > > - fixed RCU usage in logical PIO
>>> > > - Added a function to unregister a logical PIO range in logical PIO
>>> > > to support the fixes in the hisi-lpc driver
>>> > > - fixed and optimized hisi-lpc driver to avoid potential use-after-free
>>> > > and driver unbind crash
>> >
>> > Merged to fixes, thanks.
>
> This broke arm64 allmodconfig:
>
> arm64.allmodconfig:
> drivers/bus/hisi_lpc.c:656:3: error: implicit declaration of function
> 'hisi_lpc_acpi_remove'; did you mean 'hisi_lpc_acpi_probe'?
> [-Werror=implicit-function-declaration]
>
>
Uhhh, that's my fault - I didn't provide a stub for !ACPI. Sorry. I'll
send a fixed v3 series.
>
> Please build and test your branches before you send pull requests, Wei.
>
> I've dropped the branch again; please re-submit when fixed. I think
> it's probably 5.3 material now.
>
Thanks,
John
>
> -Olof
>
> .
>
next prev parent reply other threads:[~2019-06-25 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 10:23 Wei Xu
2019-06-25 10:39 ` Wei Xu
2019-06-25 10:44 ` John Garry
2019-06-25 11:21 ` Olof Johansson
2019-06-25 13:03 ` Olof Johansson
2019-06-25 13:31 ` John Garry [this message]
2019-06-26 15:21 ` John Garry
2019-06-27 2:19 ` Olof Johansson
2019-07-01 6:22 ` Wei Xu
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=7e215bd7-daab-b6cf-8d0f-9513bd7c4f6d@huawei.com \
--to=john.garry@huawei.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=huangdaode@hisilicon.com \
--cc=jinying@hisilicon.com \
--cc=liguozhu@hisilicon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=olof@lixom.net \
--cc=rjw@rjwysocki.net \
--cc=salil.mehta@huawei.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=shiju.jose@huawei.com \
--cc=tangkunshan@huawei.com \
--cc=xuwei5@hisilicon.com \
--cc=xuwei5@huawei.com \
--cc=zhangyi.ac@huawei.com \
/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
all inboxes | Powered by JetHome®