On Thu, May 09, 2019 at 01:41:44PM +0200, Greg KH wrote:
> On Thu, May 09, 2019 at 12:38:01PM +0200, Nicholas Mc Guire wrote:
> > On Thu, May 09, 2019 at 06:28:39PM +0800, wuzhouhui wrote:
> > > Hi,
> > >
> > > Stupid question, maybe. But I just could find the answer vi Bing or
> > > Google.
> >
> On May 9, 2019, at 7:41 PM, Greg KH wrote:
>
> On Thu, May 09, 2019 at 12:38:01PM +0200, Nicholas Mc Guire wrote:
>> On Thu, May 09, 2019 at 06:28:39PM +0800, wuzhouhui wrote:
>>> Hi,
>>>
>>> Stupid question, maybe. But I just could find the answer vi Bing or Google.
>>>
>>> How to generate
On Thu, May 09, 2019 at 12:38:01PM +0200, Nicholas Mc Guire wrote:
> On Thu, May 09, 2019 at 06:28:39PM +0800, wuzhouhui wrote:
> > Hi,
> >
> > Stupid question, maybe. But I just could find the answer vi Bing or Google.
> >
> > How to generate
> > Fixes: ("")
> > E.g.
> > Fixes: 298a32b1
On Thu, May 09, 2019 at 06:28:39PM +0800, wuzhouhui wrote:
> Hi,
>
> Stupid question, maybe. But I just could find the answer vi Bing or Google.
>
> How to generate
> Fixes: ("")
> E.g.
> Fixes: 298a32b13208 ("kmemleak: powerpc: skip scanning holes in the .bss
> section")
>
> Or they j
Hi,
Stupid question, maybe. But I just could find the answer vi Bing or Google.
How to generate
Fixes: ("")
E.g.
Fixes: 298a32b13208 ("kmemleak: powerpc: skip scanning holes in the .bss
section")
Or they just write it manually?
Thanks.
___
K