From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Steven Rostedt <rostedt@goodmis.org>, kernel-janitors@vger.kernel.org
Cc: linux-kselftest@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Trond Myklebust <trondmy@primarydata.com>
Subject: Re: Difficulties for compilation without extra optimisation
Date: Mon, 4 Dec 2017 10:55:19 +0100 [thread overview]
Message-ID: <513fa42d-5d4a-1b6e-3164-3f06ac6e4901@users.sourceforge.net> (raw)
In-Reply-To: <20171203214046.23b1937e@vmware.local.home>
>> Can the software areas distinguished where such special handling matters?
>
> No idea.
I would like to point another example out.
> That's something you are going to have to figure out on your own.
How do you think about information from an other clarification request
for the topic “caif: Use common error handling code in cfdgml_receive()”?
https://lkml.org/lkml/2017/11/7/486
https://patchwork.kernel.org/patch/10046849/
https://lkml.kernel.org/r/<034c0760-b8af-0fe2-e7a0-81199ff31931@users.sourceforge.net>
Regards,
Markus
next prev parent reply other threads:[~2017-12-04 9:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 16:53 [PATCH RFC v1] nfs/write: Use common error handling code in nfs_lock_and_join_requests() SF Markus Elfring
2017-12-03 14:15 ` Difficulties for compilation without extra optimisation SF Markus Elfring
2017-12-03 15:17 ` Trond Myklebust
2017-12-03 21:22 ` Steven Rostedt
2017-12-03 21:56 ` SF Markus Elfring
2017-12-04 2:40 ` Steven Rostedt
2017-12-04 9:55 ` SF Markus Elfring [this message]
2017-12-04 9:00 ` SF Markus Elfring
2017-12-04 9:48 ` Steven Rostedt
2017-12-04 10:18 ` SF 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=513fa42d-5d4a-1b6e-3164-3f06ac6e4901@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=trondmy@primarydata.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).