MIME-Version: 1.0
References: <a9466e48-77be-bb9e-bdfe-df8c763d7a76@oracle.com> <b9d302f5-a4a1-2481-a477-b31f25f8e73c@oracle.com>
In-Reply-To: <b9d302f5-a4a1-2481-a477-b31f25f8e73c@oracle.com>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed, 1 Mar 2023 08:50:13 -0800
Message-ID: <CAHk-=whe=S2BRMm63S6p53U6zOraSeb5K9zugNnBpqQjWe7fAw@mail.gmail.com>
Subject: Re: [GIT PULL] jfs updates for 6.3
To:     Dave Kleikamp <dave.kleikamp@oracle.com>
Cc:     linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Wed, Mar 1, 2023 at 8:02=E2=80=AFAM Dave Kleikamp <dave.kleikamp@oracle.=
com> wrote:
>
> Arrgh! Right after sending this I realized I hadn't even pushed my local
> jfs-next branch and it hasn't been in linux-next. It's a very low-risk
> patch, but ignore this request if you'd like to.

Heh. For basically a one-liner sign check, I really don't mind. That
patch looks like something that could have gone in as a fix after the
merge window.

Yes, we have rules, but no rule is _that_ black and white.

I appreciate the "oops, this missed linux-next", though, even if it
really doesn't matter for something like this ;)

           Linus