All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Wagner <dwagner@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] nvme: only call synhronize_srcu when clearing current path
Date: Wed, 1 Sep 2021 14:44:48 +0200	[thread overview]
Message-ID: <20210901124448.naki6kzntvsw4d6v@carbon.lan> (raw)
In-Reply-To: <YS9xKzRWW97L6ZN9@infradead.org>

On Wed, Sep 01, 2021 at 01:25:15PM +0100, Christoph Hellwig wrote:
> applied to nvme-5.15 with a cosmetic fixup to keep the lines from
> overflowing.

Thanks, forgot to check the length (I guess I should set max line length
back to 80). Looks way better anyway :)

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Wagner <dwagner@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] nvme: only call synhronize_srcu when clearing current path
Date: Wed, 1 Sep 2021 14:44:48 +0200	[thread overview]
Message-ID: <20210901124448.naki6kzntvsw4d6v@carbon.lan> (raw)
In-Reply-To: <YS9xKzRWW97L6ZN9@infradead.org>

On Wed, Sep 01, 2021 at 01:25:15PM +0100, Christoph Hellwig wrote:
> applied to nvme-5.15 with a cosmetic fixup to keep the lines from
> overflowing.

Thanks, forgot to check the length (I guess I should set max line length
back to 80). Looks way better anyway :)

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2021-09-01 12:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01  9:25 [PATCH v1] nvme: only call synhronize_srcu when clearing current path Daniel Wagner
2021-09-01  9:25 ` Daniel Wagner
2021-09-01 12:25 ` Christoph Hellwig
2021-09-01 12:25   ` Christoph Hellwig
2021-09-01 12:44   ` Daniel Wagner [this message]
2021-09-01 12:44     ` Daniel Wagner

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=20210901124448.naki6kzntvsw4d6v@carbon.lan \
    --to=dwagner@suse.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.