[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220426092818.530b7e9b@xps13>
Date: Tue, 26 Apr 2022 09:28:18 +0200
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Jean-Marc Eurin <jmeurin@...gle.com>
Cc: Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 0/3] mtd: mtdoops: Add timestamp to the dumped oops
header.
Hi Jean-Marc,
jmeurin@...gle.com wrote on Mon, 25 Apr 2022 09:14:08 -0700:
> Hi Miquel,
>
>
> On Mon, Apr 25, 2022 at 1:42 AM Miquel Raynal <miquel.raynal@...tlin.com> wrote:
> >
> > Hi Jean-Marc,
> >
> > jmeurin@...gle.com wrote on Thu, 21 Apr 2022 16:42:41 -0700:
> >
> > > The current header consists of 2 32-bit values which makes it difficult
> > > and error prone to expand. This creates a structure for the header.
> > >
> > > Some oops only have time relative to boot, this adds an absolute timestamp.
> > >
> > > Changelog since v3:
> > > Fix the printk format for sizeof to %zu.
> > >
> > > Changelog since v2:
> > > - Add a timestamp to the header.
> > >
> > > Changelog since v1:
> > > - Create a header structure to simplify code.
> > > - Patches in series.
> > > - Patch prefix.
> > >
> > > Jean-Marc Eurin (3):
> > > mtd: mtdoops: Fix the size of the header read buffer.
> > > mtd: mtdoops: Create a header structure for the saved mtdoops.
> > > mtd: mtdoops: Add a timestamp to the mtdoops header.
> >
> > Looks like the last patch was not sent to the list?
> >
>
> I'm not sure what happened. I've just sent it and then noticed that
> the mail threading is wrong. Let me know if you want me to resend the
> full thread.
It's fine like that.
>
> I'm really sorry about that :-( and thanks for all your help.
No problem!
Cheers,
Miquèl
Powered by blists - more mailing lists