mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josh Cartwright <joshc@ni.com>
To: Kyle Roeschley <kyle.roeschley@ni.com>
Cc: gregkh@linuxfoundation.org, arnd@arndb.de,
	linux-kernel@vger.kernel.org, jeff.westfahl@ni.com,
	nathan.sullivan@ni.com, xander.huff@ni.com,
	aaron.rossetto@ni.com, gratian.crisan@ni.com
Subject: Re: [PATCH 2/2] misc: nirtfeatures: physical interface elements
Date: Tue, 15 Mar 2016 09:53:27 -0500	[thread overview]
Message-ID: <20160315145327.GD27081@jcartwri.amer.corp.natinst.com> (raw)
In-Reply-To: <1457992508-18745-1-git-send-email-kyle.roeschley@ni.com>

[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]

Hey Kyle-

On Mon, Mar 14, 2016 at 04:55:08PM -0500, Kyle Roeschley wrote:
> From: Gratian Crisan <gratian.crisan@ni.com>

From what I understand, this was mostly Aaron's work, so he should get
authorship.  I could be wrong, though, but you'll want to check.

> These changes add support for PIEs (physical interface elements), which
> are defined as physical elements fixed to a controller/chassis with
> which a user can interact (e.g. LEDs and switches) and whose meaning
> is user-defined and implementation-specific.
[..]
> ---
>  drivers/misc/nirtfeatures.c | 753 ++++++++++++++++++++++++++++++++++++++++----
>  1 file changed, 694 insertions(+), 59 deletions(-)

This patchset is awkwardly split up, especially because you are removing
what you are adding in the first patch.  I would suggest coming up with
a better patch breakdown that doesn't do this, to make it easier on
reviewers.

Perhaps, breaking it up into a patchset where each patch implements a
different class of functionality (leds, input).

  Josh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-03-15 14:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 21:55 Kyle Roeschley
2016-03-15 14:53 ` Josh Cartwright [this message]
2016-03-15 16:02   ` Kyle Roeschley

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=20160315145327.GD27081@jcartwri.amer.corp.natinst.com \
    --to=joshc@ni.com \
    --cc=aaron.rossetto@ni.com \
    --cc=arnd@arndb.de \
    --cc=gratian.crisan@ni.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jeff.westfahl@ni.com \
    --cc=kyle.roeschley@ni.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan.sullivan@ni.com \
    --cc=xander.huff@ni.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®