mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Simon Que <sque@chromium.org>, linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Ben Chan <benchan@chromium.org>,
	Chun-Ta Lin <itspeter@chromium.org>,
	Zhongze Hu <frankhu@chromium.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Rob Springer <rspringer@google.com>,
	John Joseph <jnjoseph@google.com>
Subject: Re: [PATCH v7] drivers/staging: Gasket driver framework + Apex driver
Date: Fri, 29 Jun 2018 20:21:24 -0700	[thread overview]
Message-ID: <2d0d235418958e8b60913b1e0d630b8c9213ea5b.camel@perches.com> (raw)
In-Reply-To: <20180630024938.107529-1-sque@chromium.org>

On Fri, 2018-06-29 at 22:49 -0400, Simon Que wrote:
> The Gasket (Google ASIC Software, Kernel Extensions, and Tools) kernel
> framework is a generic, flexible system that supports thin kernel
> drivers. Gasket kernel drivers are expected to handle opening and
> closing devices, mmap'ing BAR space as requested, a small selection of
> ioctls, and handling page table translation (covered below). Any other
> functions should be handled by userspace code.
[]
> [PATCH v4]
> - Deleted unused field "base" in struct gasket_coherent_buffer
> - Moved maintainer info to top-level MAINTAINERS file
> [PATCH v5]
> - Updated drivers/staging/Makefile change to apply to gregkh's staging
>   tree.

Why delete all the logging by adding if (false} tests
and then not mention it?


  reply	other threads:[~2018-06-30  3:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-30  2:49 Simon Que
2018-06-30  3:21 ` Joe Perches [this message]
2018-06-30 14:07 ` Alan Cox

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=2d0d235418958e8b60913b1e0d630b8c9213ea5b.camel@perches.com \
    --to=joe@perches.com \
    --cc=benchan@chromium.org \
    --cc=frankhu@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=itspeter@chromium.org \
    --cc=jnjoseph@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=rspringer@google.com \
    --cc=sque@chromium.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

all inboxes | Powered by JetHome®