From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH 1/3] nvmet-tcp: fix endianess annotations
Date: Mon, 17 Dec 2018 23:24:55 -0800 [thread overview]
Message-ID: <8c17ae39-ba72-bc79-712f-e991cafe0f75@grimberg.me> (raw)
In-Reply-To: <20181216162457.GA12572@lst.de>
> Can I get an ACK for this for now? I can also send the proper fix
> on top then..
Acked-by: Sagi Grimberg <sagi at grimberg.me>
next prev parent reply other threads:[~2018-12-18 7:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 8:51 sparse fixes Christoph Hellwig
2018-12-13 8:51 ` [PATCH 1/3] nvmet-tcp: fix endianess annotations Christoph Hellwig
2018-12-13 16:42 ` Sagi Grimberg
2018-12-13 20:10 ` Christoph Hellwig
2018-12-16 16:24 ` Christoph Hellwig
2018-12-18 7:24 ` Sagi Grimberg [this message]
2018-12-13 8:51 ` [PATCH 2/3] " Christoph Hellwig
2018-12-13 16:42 ` Sagi Grimberg
2018-12-13 8:51 ` [PATCH 3/3] nvme-pci: refactor nvme_poll_irqdisable to make sparse happy Christoph Hellwig
2018-12-13 16:43 ` Sagi Grimberg
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=8c17ae39-ba72-bc79-712f-e991cafe0f75@grimberg.me \
--to=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