[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKXUXMw731xNrqUzrCE1jRd25vfWdYFf-donLosOYOTqcm9JiQ@mail.gmail.com>
Date: Fri, 30 Sep 2022 09:22:17 +0200
From: Lukas Bulwahn <lukas.bulwahn@...il.com>
To: Huacai Chen <chenhuacai@...nel.org>
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org,
WANG Xuerui <kernel@...0n.name>, loongarch@...ts.linux.dev
Subject: Re: [PATCH] loongarch: update config files
On Fri, Sep 30, 2022 at 4:46 AM Huacai Chen <chenhuacai@...nel.org> wrote:
>
> On Thu, Sep 29, 2022 at 6:44 PM Lukas Bulwahn <lukas.bulwahn@...il.com> wrote:
> >
> > On Thu, Sep 29, 2022 at 12:42 PM Huacai Chen <chenhuacai@...nel.org> wrote:
> > >
> > > Hi, Lukas,
> > >
> > > Thank you for your patch, it is queued for loongarch-next, and may be
> > > squashed to another patch with your S-o-B if you have no objections.
> > >
> > > Huacai
> > >
> >
> > Feel free to squash as you see fit. I cannot recall sending something
> > specific for loongarch-next, though.
> Emmm, my meaning is squash your patch to mine and keep a S-o-B in that
> patch [1]. :)
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson.git/commit/?h=loongarch-next
>
Process-wise that seems a bit strange (i.e., just mixing S-o-B by
multiple people, how do you bisect which individual change broke
something [you would need a second manual step of investigation],
etc.), but sure go ahead.
No objections.
Lukas
Powered by blists - more mailing lists