Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 06 May 2022 09:36:52 -0700 (PDT)
Subject:     Re: [PATCH] RISC-V-fixes: relocate DTB if it's outside memory region
In-Reply-To: <e3b6a7ed7dc612d7338bc95d8fbbfdfc@mailhost.ics.forth.gr>
CC:     mick@ics.forth.gr, Paul Walmsley <paul.walmsley@sifive.com>,
        aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
        linux-kernel@vger.kernel.org
From:   Palmer Dabbelt <palmer@dabbelt.com>
To:     mick@ics.forth.gr
Message-ID: <mhng-506fb56e-9288-4a73-b984-91a54e11081c@palmer-mbp2014>
Mime-Version: 1.0 (MHng)
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 29 Apr 2022 12:18:14 PDT (-0700), mick@ics.forth.gr wrote:
> Στις 2022-04-29 18:28, Palmer Dabbelt έγραψε:
>> On Thu, 28 Apr 2022 14:48:14 PDT (-0700), Palmer Dabbelt wrote:
>>> On Mon, 25 Apr 2022 23:11:23 PDT (-0700), mick@ics.forth.gr wrote:
>>>> Hello Palmer,
>>>>
>>>> Any updates on this ?
>>>
>>> Sorry about that, it's on fixes.
>>
>> Not sure if I just wasn't paying attention yesterday or if I'm
>> grumpier this morning, but that "RISC-V-fixes: " prefix is just a bit
>> too odd -- I know we've got a split between "RISC-V" and "riscv" so
>> maybe it doesn't matter, but even that is kind of ugly.
>>
>> I re-wrote it, but I'm going to let it round trip through linux-next
>> so I'll send it up next time.
>>
>> Sorry, I know this happened twice recently but I'll try not to make a
>> habit of it.
>>
>
> Don't worry about it, just let me know what works better for you, would
> "[PATCH -fixes] riscv:" be ok next time ?

That's generally how folks do it, but I just look for "fix" anywhere in 
the subject line.