From: Anssi Hannula <anssi.hannula@iki.fi>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Subbaraya Sundeep Bhatta <subbaraya.sundeep.bhatta@xilinx.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: iio commit dates in future (was: Re: [PATCH] iio: adc: xilinx-xadc: assign auxiliary channels address correctly)
Date: Sat, 04 Oct 2014 01:34:59 +0300 [thread overview]
Message-ID: <542F2493.2020805@iki.fi> (raw)
In-Reply-To: <5414A36B.3000106@kernel.org>
13.09.2014, 23:04, Jonathan Cameron kirjoitti:
> On 12/09/14 18:25, Lars-Peter Clausen wrote:
>> On 09/11/2014 10:55 AM, Subbaraya Sundeep Bhatta wrote:
>>> This patch fixes incorrect logic for assigning address
>>> to auxiliary channels of xilinx xadc.
>>>
>>> Signed-off-by: Subbaraya Sundeep Bhatta <sbhatta@xilinx.com>
>>
>> Acked-by: Lars-Peter Clausen <lars@metafoo.de>
> Applied to the fixes-togreg branch of iio.git and flagged
> for stable.
Something weird seems to have happened with this commit and at least a
few others:
1887e724e2 "iio: adc: xilinx-xadc: assign auxiliary channels address
correctly"
d4f51956ac "iio: adc: at91: don't use the last converted data register"
a31d092899 "iio:magnetometer: bugfix magnetometers gain values".
They all have their Date in the future (up to Nov 2014), looks to me
like month and day got swapped for some reason.
Not a big issue I guess, but worth looking into if it is something in
your workflow causing this :)
Noticed these strange Dates while looking at Greg's stable-queue repo.
--
Anssi Hannula
next parent reply other threads:[~2014-10-03 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <344d9464-c489-42cd-b9c4-a63759f8f6da@BL2FFO11FD040.protection.gbl>
[not found] ` <54132C78.9000300@metafoo.de>
[not found] ` <5414A36B.3000106@kernel.org>
2014-10-03 22:34 ` Anssi Hannula [this message]
2014-10-04 10:17 ` iio commit dates in future Jonathan Cameron
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=542F2493.2020805@iki.fi \
--to=anssi.hannula@iki.fi \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=subbaraya.sundeep.bhatta@xilinx.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;
as well as URLs for NNTP newsgroup(s).