From: Amey Narkhede <ameynarkhede03@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH] block: aoe: Use seq_putc() if possible
Date: Mon, 21 Dec 2020 21:34:50 +0530 [thread overview]
Message-ID: <20201221160450.t74ylcxazg4nryla@archlinux> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 1621 bytes --]
From: Amey Narkhede <ameynarkhede03@gmail.com>
To: Markus Elfring <Markus.Elfring@web.de>
Subject: Re: [PATCH] block: aoe: Use seq_putc() if possible
Date: Mon, 21 Dec 2020 21:30:13 +0530
Message-ID: <20201221160013.pohxcqob35pk44k6@archlinux>
On 20/12/21 04:04PM, Markus Elfring wrote:
> > This is a single character that is printed out. Use seq_putc() for
> > it to simplify the code.
>
> How do you think about to reconsider the integration of a previous update suggestion once more?
>
> [PATCH 1/3] block-aoe: Use seq_putc() in aoedisk_debugfs_show()
> https://lore.kernel.org/lkml/58b532fc-14c5-6e87-75d0-d78703b289dc@users.sourceforge.net/
> https://lore.kernel.org/patchwork/patch/785968/
> https://lkml.org/lkml/2017/5/8/90
>
> Regards,
> Markus
Apologies. I didn't find those patches.
I'm a beginner so I'm submitting style changes mainly
to get familiar with email based workflow of linux
kernel. I'll keep in mind to search previous
patches next time before submitting a patch.
Amey
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-12-21 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 16:04 Amey Narkhede [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-20 15:28 [PATCH] block: aoe: Use seq_putc() if possible Amey Narkhede
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=20201221160450.t74ylcxazg4nryla@archlinux \
--to=ameynarkhede03@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@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