From: Andrew Morton <akpm@linux-foundation.org>
To: "Farber, Eliav" <farbere@amazon.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
<linux-kernel@vger.kernel.org>, <yangyicong@hisilicon.com>,
<viro@zeniv.linux.org.uk>, <jonnyc@amazon.com>,
<hhhawa@amazon.com>, <andriy.shevchenko@intel.com>
Subject: Re: + libfs-fix-error-format-in-simple_attr_write.patch added to mm-nonmm-unstable branch
Date: Fri, 16 Sep 2022 13:14:08 -0700 [thread overview]
Message-ID: <20220916131408.f86352344027e77056c894ee@linux-foundation.org> (raw)
In-Reply-To: <ce553e2b-0a13-08ee-283c-bc749e41ca61@amazon.com>
On Fri, 16 Sep 2022 14:19:29 +0300 "Farber, Eliav" <farbere@amazon.com> wrote:
> Should I still revert the original patch as is, or send a new patch that
> fixes the issue by using kstrtoll()?
That sounds better.
prev parent reply other threads:[~2022-09-16 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220915213426.3BC15C433D6@smtp.kernel.org>
2022-09-16 6:11 ` Alexey Dobriyan
2022-09-16 11:19 ` Farber, Eliav
2022-09-16 20:14 ` Andrew Morton [this message]
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=20220916131408.f86352344027e77056c894ee@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=farbere@amazon.com \
--cc=hhhawa@amazon.com \
--cc=jonnyc@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yangyicong@hisilicon.com \
/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
all inboxes | Powered by JetHome®