Re: [PATCH bpf-next] Fix incorrect integer literal used for marking scratched registers in verifier logs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jan 10, 2022 at 2:13 PM Christy Lee <christyc.y.lee@xxxxxxxxx> wrote:
>
> On Mon, Jan 10, 2022 at 1:52 PM Song Liu <song@xxxxxxxxxx> wrote:
> >
> > On Fri, Jan 7, 2022 at 4:59 PM Christy Lee <christylee@xxxxxx> wrote:
> > >
> > > env->scratched_stack_slots is a 64-bit value, we should use ULL
> > > instead of UL literal values.
> > >
> > > Reported-by: kernel test robot <lkp@xxxxxxxxx>
> > > Reported-by: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
> > > Signed-off-by: Christy Lee <christylee@xxxxxx>
> >
> > The fix looks good to me. Thus:
> >
> > Acked-by: Song Liu <songliubraving@xxxxxx>
> >
> > However, the patch looks corrupted. Also, the subject is probably too
> > long (./scripts/checkpatch.pl should complain about it).
> >
>
> I just checked that even with an absurdly long subject (more than 200
> characters), ./scripts/checkpatch.pl doesn't complain. It only complains
> when the commit message body has longer than 75 characters but not the
> subject line.  What's the maximum subject line length?

Hmm..  you are right. I somehow thought there was a limit by checkpatch.
I would personally limit it to 75 characters though.




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux