Re: [PATCH v2 1/3] riscv: Add support for mem=

[Jan Kiszka]

On 15.02.20 14:44, Nikolay Borisov wrote:
> On 15.02.20 Ð. 13:49 Ñ., Jan Kiszka wrote:
> > From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
> >
> > This sets a memory limit provided via mem=3D on the command line,
> > analogously to many other architectures.
> >
> > Signed-off-by: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
> > =2D--
> >   arch/riscv/mm/init.c | 19 +++++++++++++++++++
> >   1 file changed, 19 insertions(+)
> >
> > diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c
> > index 965a8cf4829c..aec39a56d6cf 100644
> > =2D-- a/arch/riscv/mm/init.c
> > +++ b/arch/riscv/mm/init.c
> > @@ -118,6 +118,23 @@ static void __init setup_initrd(void)
> >   }
> >   #endif /* CONFIG_BLK_DEV_INITRD */
> >
> > +static phys_addr_t memory_limit =3D PHYS_ADDR_MAX;
>
> 3d is the ascii code for =, meaning your client is somehow br0ken?

The client is called git send-email, and I just checked what was passed
to it - all fine. It must be my beloved freemail provider that enables
quoted-printable encoding for this series (interestingly not for another
one I sent to a different community today). I've resent the same patch
files to both corporate and private providers, and only the latter shows
this behavior. Sigh.

IIRC, git am processes this correctly, but I can resent via the
corporate server as well, whatever is preferred.

Thanks,
Jan