[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VeWMSeZiq6vUo25hRdueMbeEEQuzPqR=-ROsOufK+27LQ@mail.gmail.com>
Date: Fri, 21 Oct 2022 12:13:52 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: ChiYuan Huang <u0084500@...il.com>
Cc: lee@...nel.org, matthias.bgg@...il.com, chiaen_wu@...htek.com,
cy_huang@...htek.com, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] mfd: mt6370: Add the out-of-bound check to prevent the
null pointer
On Fri, Oct 21, 2022 at 12:02 PM ChiYuan Huang <u0084500@...il.com> wrote:
> Andy Shevchenko <andy.shevchenko@...il.com> 於 2022年10月21日 週五 下午4:34寫道:
> > On Fri, Oct 21, 2022 at 5:17 AM cy_huang <u0084500@...il.com> wrote:
> > It looks like you randomly cut the trace.
> > It's not what I meant and documentation suggests.
> >
> I checked the submitting-patch.rst.
> To satisfy the requirement for 70-75 chars per line, I only keep the
> important log.
>
> May I ask what you mean for the 'trim'?
> Is it 'Still keep 70-75 per line and cut the characters that's over
> the limit to the next line"?
> > https://www.kernel.org/doc/html/latest/process/submitting-patches.html#backtraces-in-commit-messages
Have you had a chance to read this section of the document?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists