From: Jonathan Cameron <jic23@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PULL] IIO fixes 3.13 - set 4
Date: Tue, 24 Dec 2013 18:48:34 +0000 [thread overview]
Message-ID: <ee29edca-ee76-46b4-8237-76e2f39f5705@email.android.com> (raw)
In-Reply-To: <20131224182258.GA4587@kroah.com>
Greg KH <gregkh@linuxfoundation.org> wrote:
>On Sun, Dec 22, 2013 at 04:57:39PM +0000, Jonathan Cameron wrote:
>> The following changes since commit
>c6236c0ce39c809c336ca929f68cf8ad02cf94e0:
>>
>> staging: comedi: drivers: fix return value of
>comedi_load_firmware() (2013-12-17 13:05:53 -0800)
>>
>> are available in the git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
>tags/iio-fixes-for-3.13d
>>
>> for you to fetch changes up to
>83d5f3246fc05a629278240c09688fd9960b97db:
>>
>> staging:iio:ad799x fix incorrect endianness specification for
>buffer elements (2013-12-17 21:50:54 +0000)
>>
>> ----------------------------------------------------------------
>> 4th round of iio fixes for the 3.13 cycle.
>>
>> * Another miss reported endian fix that missed the last pull request
>due
>> to a bug in the first version posted (which made it look like a
>cleanup
>> rather than a fix).
>
>Is this a regression fix?
Nope. It was never right though I guess at one point it was not specified rather than incorrectly specified. Long ago though!
> Can it wait for 3.14-rc1 and then go into
>3.13-stable as I really didn't want to have any more pull requests for
>3.13-final due to vacations...
Sure. Have a good vacation.
>
>thanks,
>
>greg k-h
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
prev parent reply other threads:[~2013-12-24 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 16:57 [PULL] IIO fixes 3.13 - set 4 Jonathan Cameron
2013-12-24 18:22 ` Greg KH
2013-12-24 18:48 ` Jonathan Cameron [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=ee29edca-ee76-46b4-8237-76e2f39f5705@email.android.com \
--to=jic23@kernel.org \
--cc=gregkh@linuxfoundation.org \
--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.