From: krzk@kernel.org
To: linux-nfc@lists.01.org
Subject: [linux-nfc] Re: [PATCH net-next 1/3] nfc: s3fwrn5: Remove the max_payload
Date: Mon, 16 Nov 2020 10:06:47 +0100 [thread overview]
Message-ID: <20201116090647.GA5937@kozik-lap> (raw)
In-Reply-To: 20201116011205epcms2p566dbc946d6c7a0198d09b3a872e85f33@epcms2p5
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
On Mon, Nov 16, 2020@10:12:05AM +0900, Bongsu Jeon wrote:
> max_payload is unused.
>
> Signed-off-by: Bongsu Jeon <bongsu.jeon@samsung.com>
Please version your patches (this should be a v2) and describe changes
between versions in changelog, either in cover letter or after ---
separator.
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: krzk@kernel.org
To: linux-nfc@lists.01.org
Subject: Re: [PATCH net-next 1/3] nfc: s3fwrn5: Remove the max_payload
Date: Mon, 16 Nov 2020 10:06:47 +0100 [thread overview]
Message-ID: <20201116090647.GA5937@kozik-lap> (raw)
In-Reply-To: <20201116011205epcms2p566dbc946d6c7a0198d09b3a872e85f33@epcms2p5>
[-- Attachment #1: Type: text/plain, Size: 382 bytes --]
On Mon, Nov 16, 2020 at 10:12:05AM +0900, Bongsu Jeon wrote:
> max_payload is unused.
>
> Signed-off-by: Bongsu Jeon <bongsu.jeon@samsung.com>
Please version your patches (this should be a v2) and describe changes
between versions in changelog, either in cover letter or after ---
separator.
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: "krzk@kernel.org" <krzk@kernel.org>
To: Bongsu Jeon <bongsu.jeon@samsung.com>
Cc: Krzysztof Opasiak <k.opasiak@samsung.com>,
"linux-nfc@lists.01.org" <linux-nfc@lists.01.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 1/3] nfc: s3fwrn5: Remove the max_payload
Date: Mon, 16 Nov 2020 10:06:47 +0100 [thread overview]
Message-ID: <20201116090647.GA5937@kozik-lap> (raw)
In-Reply-To: <20201116011205epcms2p566dbc946d6c7a0198d09b3a872e85f33@epcms2p5>
On Mon, Nov 16, 2020 at 10:12:05AM +0900, Bongsu Jeon wrote:
> max_payload is unused.
>
> Signed-off-by: Bongsu Jeon <bongsu.jeon@samsung.com>
Please version your patches (this should be a v2) and describe changes
between versions in changelog, either in cover letter or after ---
separator.
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Best regards,
Krzysztof
next reply other threads:[~2020-11-16 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 9:06 krzk [this message]
2020-11-16 9:06 ` [PATCH net-next 1/3] nfc: s3fwrn5: Remove the max_payload krzk
2020-11-16 9:06 ` krzk
[not found] <CGME20201116011205epcms2p566dbc946d6c7a0198d09b3a872e85f33@epcms2p5>
2020-11-16 1:12 ` Bongsu Jeon
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=20201116090647.GA5937@kozik-lap \
--to=krzk@kernel.org \
--cc=linux-nfc@lists.01.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.