linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Bongsu Jeon <bongsu.jeon2@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-nfc@lists.01.org,
	Bongsu Jeon <bongsu.jeon@samsung.com>
Subject: Re: [PATCH net] net: nfc: nci: fix the wrong NCI_CORE_INIT parameters
Date: Mon, 18 Jan 2021 13:31:49 -0800	[thread overview]
Message-ID: <20210118133149.22f2fef1@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <CACwDmQDxa6WKq4UwCfk2sxC8JukV+CcnuSqrCdhSWSjJ9ppwOg@mail.gmail.com>

On Tue, 19 Jan 2021 06:19:23 +0900 Bongsu Jeon wrote:
> On Tue, Jan 19, 2021 at 6:01 AM Jakub Kicinski <kuba@kernel.org> wrote:
> >
> > On Tue, 19 Jan 2021 05:55:22 +0900 Bongsu Jeon wrote:  
> > > From: Bongsu Jeon <bongsu.jeon@samsung.com>
> > >
> > > Fix the code because NCI_CORE_INIT_CMD includes two parameters in NCI2.0
> > > but there is no parameters in NCI1.x.
> > >
> > > Signed-off-by: Bongsu Jeon <bongsu.jeon@samsung.com>  
> >
> > What's the Fixes tag for this change?  
> Sorry to miss the Fixes tag.
> This is the Fixes tag ( Fixes: bcd684aace34 ("net/nfc/nci: Support NCI
> 2.x initial sequence") )
> Could I resend this patch after adding that tag?

It's fine no need to repost, I can add the tag when applying the patch,
let's wait for reviews. Let me just place it on a line of its own,
patchwork is supposed to pick that up automatically:

Fixes: bcd684aace34 ("net/nfc/nci: Support NCI 2.x initial sequence")

  reply	other threads:[~2021-01-18 21:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 20:55 [PATCH net] net: nfc: nci: fix the wrong NCI_CORE_INIT parameters Bongsu Jeon
2021-01-18 21:01 ` Jakub Kicinski
2021-01-18 21:19   ` Bongsu Jeon
2021-01-18 21:31     ` Jakub Kicinski [this message]
2021-01-20  1:00 ` patchwork-bot+netdevbpf
2021-01-20  9:54   ` Bongsu Jeon
2021-01-20 16:58     ` Jakub Kicinski

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=20210118133149.22f2fef1@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
    --to=kuba@kernel.org \
    --cc=bongsu.jeon2@gmail.com \
    --cc=bongsu.jeon@samsung.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfc@lists.01.org \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).