[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <eb5285a0f1ee2f7211a0e0687e0ed73ba8920fea.camel@sipsolutions.net>
Date: Tue, 30 Jul 2019 19:14:21 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Akinobu Mita <akinobu.mita@...il.com>, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, Keith Busch <keith.busch@...el.com>,
Jens Axboe <axboe@...com>, Christoph Hellwig <hch@....de>,
Sagi Grimberg <sagi@...mberg.me>,
Minwoo Im <minwoo.im.dev@...il.com>,
Kenneth Heitke <kenneth.heitke@...el.com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@....com>
Subject: Re: [PATCH 2/2] devcoredump: fix typo in comment
On Tue, 2019-07-30 at 19:11 +0200, Greg KH wrote:
> On Tue, Jul 30, 2019 at 06:49:12PM +0200, Johannes Berg wrote:
> > On Tue, 2019-07-30 at 18:45 +0200, Greg KH wrote:
> >
> > > > I mean, you take patches to devcoredump in general?
> > >
> > > I have no idea, run 'scripts/get_maintainer.pl' to be sure :)
> >
> > That actually points to me :-)
> >
> > So really I guess the question is how I should send these upstream? It's
> > to drivers/base/devcoredump.c and include/linux/devcoredump.h and I
> > kinda figured you wanted to see these things.
>
> Ah, sure, I can take them, I had no idea what devcoredump was. Remember
> my patch workload :)
:-)
> So send them on please.
Will do. Thanks Greg.
johannes
Powered by blists - more mailing lists