From: Andrew Morton <akpm@linux-foundation.org>
To: akash.goel@intel.com
Cc: linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
Tom Zanussi <tzanussi@gmail.com>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [PATCH v2] relay: Add global mode support for buffer-only channels
Date: Mon, 11 Jul 2016 13:17:09 -0700 [thread overview]
Message-ID: <20160711131709.4b2417f54b2eb9fd0fa19900@linux-foundation.org> (raw)
In-Reply-To: <1468221456-15537-1-git-send-email-akash.goel@intel.com>
On Mon, 11 Jul 2016 12:47:36 +0530 akash.goel@intel.com wrote:
> From: Akash Goel <akash.goel@intel.com>
>
> The following patch added support to use channels with no associated files.
> relay: add buffer-only channels; useful for early logging
hm, 8 years ago. Normally we refer to previous commits using the form
20d8b67c06fa5e74f44e ("relay: add buffer-only channels; useful for
early logging"). But this one is so old that we should inform readers
about its vintage, so this form:
commit 20d8b67c06fa5e74f44e80b0a0fd68c8327f7c6a
Author: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
Date: Fri Jul 25 19:45:12 2008 -0700
relay: add buffer-only channels; useful for early logging
would be better.
> This is useful when the exact location of relay file is not known or the
> the parent directory of relay file is not available, while creating the
> channel and the logging has to start right from the boot.
>
> But there was no provision to use global mode with buffer-only channels,
> which is added by this patch, without modifying the interface where initially
> there will be a dummy invocation of create_buf_file callback through which
> kernel client can convey the need of a global buffer.
>
> For the use case where drivers/kernel clients want a simple interface for the
> userspace, which enables them to capture data/logs from relay file in order &
> without any post processing, support of Global buffer mode is warranted.
>
> ...
>
> @@ -706,6 +727,7 @@ int relay_late_setup_files(struct rchan *chan,
>
> return err;
> }
> +EXPORT_SYMBOL_GPL(relay_late_setup_files);
The export is unneeded and undocumented.
next prev parent reply other threads:[~2016-07-11 20:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 16:15 [PATCH] " akash.goel
2016-07-04 8:00 ` Chris Wilson
2016-07-04 13:03 ` Goel, Akash
2016-07-11 7:17 ` [PATCH v2] " akash.goel
2016-07-11 20:17 ` Andrew Morton [this message]
2016-07-12 9:24 ` Chris Wilson
2016-07-12 12:50 ` Goel, Akash
2016-07-12 13:01 ` Chris Wilson
2016-07-12 13:24 ` Goel, Akash
2016-07-12 19:51 ` Andrew Morton
2016-07-13 7:39 ` [PATCH v3] " akash.goel
2016-07-13 8:30 ` kbuild test robot
2016-07-13 10:09 ` [PATCH v4] " akash.goel
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=20160711131709.4b2417f54b2eb9fd0fa19900@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=akash.goel@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=eduard.munteanu@linux360.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=tzanussi@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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®