From: Krzysztof Kozlowski <krzk@kernel.org>
To: linux-nfc@lists.01.org
Subject: Re: [PATCH net-next v2 1/3] nfc: s3fwrn5: Remove the max_payload
Date: Tue, 17 Nov 2020 09:38:56 +0100 [thread overview]
Message-ID: <CAJKOXPdH49zOQ2caOvDDiZPkEptYiCjUmXw+O2dCC1tKHZgPag@mail.gmail.com> (raw)
In-Reply-To: <CAEx-X7epecwBYV7UYoesQ9+Q8ir+kjYGyysiyDtCa0BzKiCGtA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
On Tue, 17 Nov 2020 at 09:14, Bongsu Jeon <bs.jeon87@gmail.com> wrote:
>
> 2020-11-17 16:42 GMT+09:00, krzk(a)kernel.org <krzk@kernel.org>:
> > On Tue, Nov 17, 2020 at 10:16:11AM +0900, Bongsu Jeon wrote:
> >> max_payload is unused.
> >
> > Why did you resend the patch ignoring my review? I already provided you
> > with a tag, so you should include it.
> >
> > https://www.kernel.org/doc/html/latest/process/submitting-patches.html
> >
> > Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
> >
> > Best regards,
> > Krzysztof
> >
>
> Sorry about that. I included the tag.
You need to reduce the rate of sending new patches. You sent v1. Then
you sent again v1, which I reviewed. Then you send v2 without my
review. So I provided a review. Then you sent again a v2 with my
reviewed tags. So there are two v1 patches and two v2. Since I
provided you the review tags for v2, no need to send v2 again. It
confuses.
Best regards,
Krzysztof
next parent reply other threads:[~2020-11-17 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEx-X7epecwBYV7UYoesQ9+Q8ir+kjYGyysiyDtCa0BzKiCGtA@mail.gmail.com>
2020-11-17 8:38 ` Krzysztof Kozlowski [this message]
[not found] <CGME20201117080824epcms2p36f70e06e2d8bd51d1af278b26ca65725@epcms2p3>
2020-11-17 8:08 ` [PATCH net-next v2 1/3] nfc: s3fwrn5: Remove the max_payload Bongsu Jeon
[not found] <CGME20201117011611epcms2p22fb0315814144e94856a96014c376a04@epcms2p2>
2020-11-17 1:16 ` Bongsu Jeon
2020-11-17 7:42 ` krzk
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=CAJKOXPdH49zOQ2caOvDDiZPkEptYiCjUmXw+O2dCC1tKHZgPag@mail.gmail.com \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).