All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"sagi@grimberg.me" <sagi@grimberg.me>
Subject: Re: [PATCH 0/2] nvmet: nvme_excute_get_feat() cleanup
Date: Mon, 14 Mar 2022 23:00:15 +0000	[thread overview]
Message-ID: <cc10b52a-00fe-43ff-07cb-fa9cd3a4bbf9@nvidia.com> (raw)
In-Reply-To: <20220314074249.GB4570@lst.de>

On 3/14/22 00:42, Christoph Hellwig wrote:
> Thanks,
> 
> applied to nvme-5.18.
> 

When I pulled the changes today it didn't show this patch-series,
git HEAD is pointing to

"nvmet: use snprintf() with PAGE_SIZE in configfs" :-

nvme (nvme-5.18) # gitpulltheirs
warning: Pulling without specifying how to reconcile divergent branches is
discouraged. You can squelch this message by running one of the following
commands sometime before your next pull:

   git config pull.rebase false  # merge (the default strategy)
   git config pull.rebase true   # rebase
   git config pull.ff only       # fast-forward only

You can replace "git config" with "git config --global" to set a default
preference for all repositories. You can also pass --rebase, --no-rebase,
or --ff-only on the command line to override the configured default per
invocation.

Already up to date.
nvme (nvme-5.18) # gitlog -3
1720007a91d9 (HEAD -> nvme-5.18) Merge branch 'nvme-5.18' of 
git://git.infradead.org/nvme into nvme-5.18
98152eb70fff (origin/nvme-5.18) nvmet: use snprintf() with PAGE_SIZE in 
configfs
73d77c53ff34 nvmet: don't fold lines
nvme (nvme-5.18) # git log -3
commit 1720007a91d9146d537da662e3ce53e656b4850a (HEAD -> nvme-5.18)
Merge: ec7daf016113 98152eb70fff
Author: Chaitanya Kulkarni <kch@nvidia.com>
Date:   Mon Mar 14 15:51:27 2022 -0700

     Merge branch 'nvme-5.18' of git://git.infradead.org/nvme into nvme-5.18

commit 98152eb70fffad910ee7c511b110afe98f162fc5 (origin/nvme-5.18)
Author: Chaitanya Kulkarni <kch@nvidia.com>
Date:   Tue Mar 8 14:56:58 2022 -0800

     nvmet: use snprintf() with PAGE_SIZE in configfs

     Instead of using sprintf, use snprintf with buffer size limited to
     PAGE_SIZE just like what we have for the rest of the file.

     Signed-off-by: Chaitanya Kulkarni <kch@nvidia.com>
     Signed-off-by: Christoph Hellwig <hch@lst.de>

commit 73d77c53ff342bfa23daedf4475cdd06618e447b
Author: Chaitanya Kulkarni <kch@nvidia.com>
Date:   Tue Mar 8 14:56:57 2022 -0800

     nvmet: don't fold lines

     Don't fold line that can fit into 80 char limit. No functional change
     in this patch.

     Signed-off-by: Chaitanya Kulkarni <kch@nvidia.com>
     Signed-off-by: Christoph Hellwig <hch@lst.de>
nvme (nvme-5.18) #


  reply	other threads:[~2022-03-14 23:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 17:43 [PATCH 0/2] nvmet: nvme_excute_get_feat() cleanup Chaitanya Kulkarni
2022-03-09 17:43 ` [PATCH 1/2] nvmet: open code nvmet_get_feat_async_event() Chaitanya Kulkarni
2022-03-09 17:43 ` [PATCH 2/2] nvmet: open code nvmet_get_feat_kato() Chaitanya Kulkarni
2022-03-14  7:42 ` [PATCH 0/2] nvmet: nvme_excute_get_feat() cleanup Christoph Hellwig
2022-03-14 23:00   ` Chaitanya Kulkarni [this message]
2022-03-15  6:30     ` Christoph Hellwig
2022-03-14 23:05   ` Chaitanya Kulkarni

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=cc10b52a-00fe-43ff-07cb-fa9cd3a4bbf9@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=hch@lst.de \
    --cc=linux-nvme@lists.infradead.org \
    --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 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.