From: Greg KH <greg@kroah.com>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH 00/10] staging:iio:various fixes
Date: Sat, 26 Nov 2011 16:33:49 -0800 [thread overview]
Message-ID: <20111127003349.GA13232@kroah.com> (raw)
In-Reply-To: <1319646465-2788-1-git-send-email-jic23@cam.ac.uk>
On Wed, Oct 26, 2011 at 05:27:35PM +0100, Jonathan Cameron wrote:
> Hi Greg,
>
> A mixed bag of fixes. Nothing controversial and all have been on
> the mailing list in various series.
All applied, thanks.
greg k-h
prev parent reply other threads:[~2011-11-27 0:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 16:27 [PATCH 00/10] staging:iio:various fixes Jonathan Cameron
2011-10-26 16:27 ` [PATCH 01/10] staging:iio:light:tsl2563 both intensity channels have same chan_spec Jonathan Cameron
2011-10-26 16:27 ` [PATCH 02/10] staging:iio:light:tsl2563 missing setting of id in get id function Jonathan Cameron
2011-10-26 16:27 ` [PATCH 03/10] staging:iio:triggers Remove unecessary existence checks and return val Jonathan Cameron
2011-10-26 16:27 ` [PATCH 04/10] staging:iio:industrialio-trigger.c Trivial code style brackets fix Jonathan Cameron
2011-10-26 16:27 ` [PATCH 05/10] staging:iio:kfifo remove entirely pointless code Jonathan Cameron
2011-10-26 16:27 ` [PATCH 06/10] staging:iio: trigger fixes for repeat request of same trigger and allocation failure Jonathan Cameron
2011-10-26 16:27 ` [PATCH 07/10] staging:iio:core shared attrs do not work with modifier Jonathan Cameron
2011-10-26 16:27 ` [PATCH 08/10] staging:iio:events: Make sure userspace buffer is large enough Jonathan Cameron
2011-10-26 16:27 ` [PATCH 09/10] staging:iio:iio_utils.h: Add missing include Jonathan Cameron
2011-10-26 16:27 ` [PATCH 10/10] staging:iio: core. Allow for event chrdev obtaining ioctl if no buffer present Jonathan Cameron
2011-11-27 0:33 ` Greg KH [this message]
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=20111127003349.GA13232@kroah.com \
--to=greg@kroah.com \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.