From: Nick Kossifidis <mick@ics.forth.gr>
To: Palmer Dabbelt <palmer@dabbelt.com>
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
Subject: Re: [PATCH] RISC-V-fixes: relocate DTB if it's outside memory region
Date: Fri, 29 Apr 2022 22:18:14 +0300 [thread overview]
Message-ID: <e3b6a7ed7dc612d7338bc95d8fbbfdfc@mailhost.ics.forth.gr> (raw)
In-Reply-To: <mhng-6c123e84-9530-46f6-a5ec-6b908bb92f95@palmer-ri-x1c9>
Στις 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 ?
Regards,
Nick
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Nick Kossifidis <mick@ics.forth.gr>
To: Palmer Dabbelt <palmer@dabbelt.com>
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
Subject: Re: [PATCH] RISC-V-fixes: relocate DTB if it's outside memory region
Date: Fri, 29 Apr 2022 22:18:14 +0300 [thread overview]
Message-ID: <e3b6a7ed7dc612d7338bc95d8fbbfdfc@mailhost.ics.forth.gr> (raw)
In-Reply-To: <mhng-6c123e84-9530-46f6-a5ec-6b908bb92f95@palmer-ri-x1c9>
Στις 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 ?
Regards,
Nick
next prev parent reply other threads:[~2022-04-29 19:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 13:28 [PATCH] RISC-V-fixes: relocate DTB if it's outside memory region Nick Kossifidis
2022-03-22 13:28 ` Nick Kossifidis
2022-03-23 17:21 ` Conor Dooley
2022-03-23 17:21 ` Conor Dooley
2022-03-24 9:37 ` Conor.Dooley
2022-03-24 9:37 ` Conor.Dooley
2022-03-27 8:52 ` Nick Kossifidis
2022-03-27 8:52 ` Nick Kossifidis
2022-04-28 21:48 ` Palmer Dabbelt
2022-04-28 21:48 ` Palmer Dabbelt
2022-04-28 21:58 ` Conor Dooley
2022-04-28 21:58 ` Conor Dooley
2022-04-26 6:11 ` Nick Kossifidis
2022-04-26 6:11 ` Nick Kossifidis
2022-04-28 21:48 ` Palmer Dabbelt
2022-04-28 21:48 ` Palmer Dabbelt
2022-04-29 15:28 ` Palmer Dabbelt
2022-04-29 15:28 ` Palmer Dabbelt
2022-04-29 19:18 ` Nick Kossifidis [this message]
2022-04-29 19:18 ` Nick Kossifidis
2022-05-06 16:36 ` Palmer Dabbelt
2022-05-06 16:36 ` Palmer Dabbelt
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=e3b6a7ed7dc612d7338bc95d8fbbfdfc@mailhost.ics.forth.gr \
--to=mick@ics.forth.gr \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.