On Wed, Nov 14, 2018 at 01:14:57AM -0600, Kees Cook wrote:
> On Sat, Nov 3, 2018 at 6:38 PM, Joel Fernandes (Google)
> wrote:
> > Here are some simple cleanups and fixes for ramoops in pstore. Let me know
> > what you think, thanks.
>
> I took these and slightly tweaked code locations for the
On Wed, Nov 14, 2018 at 01:14:57AM -0600, Kees Cook wrote:
> On Sat, Nov 3, 2018 at 6:38 PM, Joel Fernandes (Google)
> wrote:
> > Here are some simple cleanups and fixes for ramoops in pstore. Let me know
> > what you think, thanks.
>
> I took these and slightly tweaked code locations for the
On Sat, Nov 3, 2018 at 6:38 PM, Joel Fernandes (Google)
wrote:
> Here are some simple cleanups and fixes for ramoops in pstore. Let me know
> what you think, thanks.
I took these and slightly tweaked code locations for the first one.
I'll send out the series for review when I'm back from
On Sat, Nov 3, 2018 at 6:38 PM, Joel Fernandes (Google)
wrote:
> Here are some simple cleanups and fixes for ramoops in pstore. Let me know
> what you think, thanks.
I took these and slightly tweaked code locations for the first one.
I'll send out the series for review when I'm back from
Here are some simple cleanups and fixes for ramoops in pstore. Let me know
what you think, thanks.
Joel Fernandes (Google) (3):
pstore: map pstore types to names
pstore: simplify ramoops_get_next_prz arguments
pstore: donot treat empty buffers as valid
fs/pstore/inode.c | 53
Here are some simple cleanups and fixes for ramoops in pstore. Let me know
what you think, thanks.
Joel Fernandes (Google) (3):
pstore: map pstore types to names
pstore: simplify ramoops_get_next_prz arguments
pstore: donot treat empty buffers as valid
fs/pstore/inode.c | 53
6 matches
Mail list logo