Hi Mark,
On Thu, Sep 28, 2017 at 2:01 AM, Mark Brown wrote:
> On Wed, Sep 27, 2017 at 02:36:01PM +0900, Magnus Damm wrote:
>> On Wed, Sep 27, 2017 at 2:30 AM, Mark Brown wrote:
>> > On Mon, Sep 25, 2017 at 09:15:53PM +0200, Geert Uytterhoeven wrote:
>
>>
Hi Mark, Geert, everyone,
On Wed, Sep 27, 2017 at 2:30 AM, Mark Brown wrote:
> On Mon, Sep 25, 2017 at 09:15:53PM +0200, Geert Uytterhoeven wrote:
>
>> My rebuttal is threefold:
>> 1. Listing the fallback property is mandatory for new SoCs. We only keep
>> the per-SoC
On Mon, Sep 25, 2017 at 09:15:53PM +0200, Geert Uytterhoeven wrote:
> My rebuttal is threefold:
> 1. Listing the fallback property is mandatory for new SoCs. We only keep
> the per-SoC compatible values in the driver for older SoCs that predate
> the introduction of fallback
sas <linux-renesas-soc@vger.kernel.org>; Chris
> Paterson <chris.paters...@renesas.com>; Biju Das <biju@bp.renesas.com>
> Subject: Re: Applied "spi: sh-msiof: Add compatible strings for r8a774[35]"
> to the spi tree
>
> Hi Mark,
>
> On Mon, Se
Hi Mark,
On Mon, Sep 25, 2017 at 8:45 PM, Mark Brown wrote:
> On Mon, Sep 25, 2017 at 07:48:44PM +0200, Geert Uytterhoeven wrote:
>> Please drop this patch, as there's no need to add explicit matching for these
>> compatible values. The family-specific compatible values
On Mon, Sep 25, 2017 at 07:48:44PM +0200, Geert Uytterhoeven wrote:
> Please drop this patch, as there's no need to add explicit matching for these
> compatible values. The family-specific compatible values (which the driver
> already matches against) are sufficient.
While the patch is not
Hi Mark,
On Mon, Sep 25, 2017 at 6:16 PM, Mark Brown wrote:
> The patch
>
>spi: sh-msiof: Add compatible strings for r8a774[35]
>
> has been applied to the spi tree at
>
>git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
>
> All being well this means that
The patch
spi: sh-msiof: Add compatible strings for r8a774[35]
has been applied to the spi tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent