public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Fred Akers <knivey@botops.net>
Cc: abbotti@mev.co.uk, hsweeten@visionengravers.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: comedi: range: remove unnecessary sanity check
Date: Wed, 5 Mar 2014 22:23:33 -0800	[thread overview]
Message-ID: <20140306062333.GA19862@kroah.com> (raw)
In-Reply-To: <1394086023-10852-1-git-send-email-knivey@botops.net>

On Thu, Mar 06, 2014 at 01:07:03AM -0500, Fred Akers wrote:
> This check is unnecessary because range_table will always be
> initialized to range_unknown by comedi_device_postconfig() for
> drivers that do not initialize range_table or range_table_list
> 
> Signed-off-by: Fred Akers <knivey@botops.net>
> ---
> Apply this after first patch

What "first" patch?

If you have patches that need a sequence, then send a series of patches,
all numbered, like git will export for you, so I know for sure that I've
gotten them all, and that they are in the correct order.

You don't want me to have to guess :)

Care to try again?

thanks,

greg k-h

  reply	other threads:[~2014-03-06  6:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53176DC0.9070503@mev.co.uk>
2014-03-06  6:07 ` [PATCH] Staging: comedi: range: remove unnecessary sanity check Fred Akers
2014-03-06  6:23   ` Greg KH [this message]
2014-03-06  6:57     ` [PATCH v2 1/2] Staging: comedi: range: tidy up comedi_check_chanlist() Fred Akers
2014-03-06  9:05       ` Ian Abbott
2014-03-06 16:43       ` Hartley Sweeten
2014-03-06  6:57     ` [PATCH v2 2/2] Staging: comedi: range: remove unnecessary sanity check Fred Akers
2014-03-06  9:18       ` Ian Abbott
2014-03-06  9:24       ` Dan Carpenter
2014-03-06 16:44       ` Hartley Sweeten

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=20140306062333.GA19862@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=abbotti@mev.co.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=hsweeten@visionengravers.com \
    --cc=knivey@botops.net \
    --cc=linux-kernel@vger.kernel.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