From: Christoph Hellwig <hch@lst.de>
To: Max Gurtovoy <mgurtovoy@nvidia.com>
Cc: hch@lst.de, linux-nvme@lists.infradead.org, sagi@grimberg.me,
kbusch@kernel.org, kch@nvidia.com
Subject: Re: [PATCH 1/1] nvme: remove un-needed include from constants file
Date: Tue, 10 May 2022 08:13:57 +0200 [thread overview]
Message-ID: <20220510061357.GA10997@lst.de> (raw)
In-Reply-To: <20220510061312.GA10966@lst.de>
On Tue, May 10, 2022 at 08:13:12AM +0200, Christoph Hellwig wrote:
> On Thu, Apr 28, 2022 at 12:15:24PM +0300, Max Gurtovoy wrote:
> > No usage of blkdev.h elements.
> >
> > Signed-off-by: Max Gurtovoy <mgurtovoy@nvidia.com>
>
> git-am is not happy with this one:
>
> Applying: nvme: remove un-needed include from constants file
> warning: Patch sent with format=flowed; space at the end of lines might be lost.
> Patch is empty.
Hmm, but after complaining it actually applied it just fine, not sure
what went on there.
prev parent reply other threads:[~2022-05-10 6:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 9:15 [PATCH 1/1] nvme: remove un-needed include from constants file Max Gurtovoy
2022-05-10 6:13 ` Christoph Hellwig
2022-05-10 6:13 ` Christoph Hellwig [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220510061357.GA10997@lst.de \
--to=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=mgurtovoy@nvidia.com \
--cc=sagi@grimberg.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox