[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAC5umyjrYddqtQY8LdoXG8S7s7xaAO3oZz7WRDkfnjrkUj2AcQ@mail.gmail.com>
Date: Mon, 13 May 2019 23:59:52 +0900
From: Akinobu Mita <akinobu.mita@...il.com>
To: minwoo.im@...sung.com
Cc: "linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jens Axboe <axboe@...com>, Sagi Grimberg <sagi@...mberg.me>,
Kenneth Heitke <kenneth.heitke@...el.com>,
Keith Busch <keith.busch@...el.com>,
Minwoo Im <minwoo.im.dev@...il.com>,
Johannes Berg <johannes@...solutions.net>,
Christoph Hellwig <hch@....de>
Subject: Re: [PATCH v3 6/7] nvme-pci: trigger device coredump on command timeout
2019年5月13日(月) 16:41 Minwoo Im <minwoo.im@...sung.com>:
>
> > -static void __maybe_unused nvme_coredump_init(struct nvme_dev *dev);
> > -static void __maybe_unused nvme_coredump_logs(struct nvme_dev *dev);
> > -static void __maybe_unused nvme_coredump_complete(struct nvme_dev
> > *dev);
> > +static void nvme_coredump_init(struct nvme_dev *dev);
> > +static void nvme_coredump_logs(struct nvme_dev *dev);
> > +static void nvme_coredump_complete(struct nvme_dev *dev);
>
> You just have added those three prototypes in previous patch. Did I miss
> something here?
These __maybe_unused are needed only in the patch 5/7.
Because these functions are still unused before applying patch 6/7.
Powered by blists - more mailing lists