From: Markus Elfring <Markus.Elfring@web.de>
To: Keyur Patel <iamkeyur96@gmail.com>,
devel@driverdev.osuosl.org, kernel-janitors@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Christian Gromm <christian.gromm@microchip.com>,
Eugeniu Rosca <erosca@de.adit-jv.com>,
Suresh Udipi <sudipi@jp.adit-jv.com>,
Colin Ian King <colin.king@canonical.com>,
linux-kernel@vger.kernel.org
Subject: Re: [v4] staging: most: Delete an error message for a failed memory allocation
Date: Sun, 14 Jul 2019 19:12:24 +0200 [thread overview]
Message-ID: <425b30ac-623c-065e-1a2f-fc131dee28d1@web.de> (raw)
In-Reply-To: <20190714170424.GA3615@keyur-pc>
> I think commit message is clear enough to understand why this is needed.
There are differences to consider between the involved software developers.
> You can send me what should I include in commit description
The clarification should be continued with the number “v5”
in the message subject.
> and I will add and send it again. Otherwise, Greg can comment on this.
Would you like to recheck information sources for the safe description
of the Linux allocation failure report?
Regards,
Markus
next prev parent reply other threads:[~2019-07-14 17:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 11:08 [PATCH 2/2] staging: most: remove redundant print statement when kfifo_alloc fails Keyur Patel
2019-07-11 17:39 ` [PATCH v2] staging: most: remove redundant print statement when Keyur Patel
2019-07-11 17:50 ` [PATCH v3] staging: most: remove redundant print statement when kfifo_alloc fails Keyur Patel
2019-07-14 14:42 ` [v3] " Markus Elfring
2019-07-14 15:05 ` [PATCH v4] " Keyur Patel
2019-07-14 15:23 ` [v4] " Markus Elfring
2019-07-14 15:45 ` Keyur Patel
2019-07-14 15:47 ` Keyur Patel
2019-07-14 16:20 ` Markus Elfring
2019-07-15 7:32 ` Greg Kroah-Hartman
2019-07-14 16:41 ` [PATCH v4] staging: most: Delete an error message for a failed memory allocation Keyur Patel
2019-07-14 16:55 ` [v4] " Markus Elfring
2019-07-14 17:04 ` Keyur Patel
2019-07-14 17:12 ` Markus Elfring [this message]
2019-07-14 17:27 ` [PATCH v5] " Keyur Patel
2019-07-14 17:38 ` [v5] " Markus Elfring
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=425b30ac-623c-065e-1a2f-fc131dee28d1@web.de \
--to=markus.elfring@web.de \
--cc=christian.gromm@microchip.com \
--cc=colin.king@canonical.com \
--cc=devel@driverdev.osuosl.org \
--cc=erosca@de.adit-jv.com \
--cc=gregkh@linuxfoundation.org \
--cc=iamkeyur96@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipi@jp.adit-jv.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;
as well as URLs for NNTP newsgroup(s).