[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAAhV-H49Te6h4Qx0xaKwk8y29pgW+12=hpsJh8w6Tkyp84f0UQ@mail.gmail.com>
Date: Thu, 13 Oct 2022 23:27:24 +0800
From: Huacai Chen <chenhuacai@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Huacai Chen <chenhuacai@...ngson.cn>,
Arnd Bergmann <arnd@...db.de>, loongarch@...ts.linux.dev,
linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
Guo Ren <guoren@...nel.org>, Xuerui Wang <kernel@...0n.name>,
Jiaxun Yang <jiaxun.yang@...goat.com>
Subject: Re: [GIT PULL] LoongArch changes for v6.1
Hi, Linus,
On Thu, Oct 13, 2022 at 2:24 AM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> On Wed, Oct 12, 2022 at 7:51 AM Huacai Chen <chenhuacai@...ngson.cn> wrote:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson.git tags/loongarch-6.1
>
> Grr.
>
> This was rebased mere hours before the pull request.
>
> Much (all?) of it has been in next - with different commit IDs, of
> course, but the question remains why you have rebased it?
I'm very sorry for that. The patches are in linux-next for some days,
but the kernel test robot reports that there is a "define but not
used" warning, so I fixed that warning and rebased.
> It just makes it much less convenient for me to check "was this in
> next?" and is generally a *horrible* thing to do.
I will avoid such operations in future, sorry for that again.
Huacai
>
> Linus
Powered by blists - more mailing lists