From: Jonathan Cameron <jic23@kernel.org>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] iio: adc: rockchip_saradc: add missing MODULE_* data
Date: Mon, 13 Jul 2015 21:52:06 +0100 [thread overview]
Message-ID: <55A424F6.6080304@kernel.org> (raw)
In-Reply-To: <9AE8F596-1594-4B92-B06E-C6F14527239D@kernel.org>
On 13/07/15 10:23, Jonathan Cameron wrote:
>
>
> On 11 July 2015 19:59:31 BST, "Heiko Stübner" <heiko@sntech.de> wrote:
>> Hi Jonathan,
>>
>> Am Samstag, 11. Juli 2015, 18:32:42 schrieb Jonathan Cameron:
>>> On 08/07/15 15:17, Heiko Stuebner wrote:
>>>> The module-data is currently missing. This includes the
>>>> license-information
>>>> which makes the driver taint the kernel and miss symbols when
>> compiled as
>>>> module.
>>>>
>>>> Fixes: 44d6f2ef94f9 ("iio: adc: add driver for Rockchip saradc")
>>>> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
>>>
>>> Sorry Heiko,
>>>
>>> Not entirely sure why I haven't picked this up before.
>>>
>>> Anyhow, now applied to the fixes-for-4.2 branch of iio.git
>>> and marked for stable. I need to catch up with a bit of a
>>> backlog, but should get a pull request out to Greg sometime
>>> early next week.
>>
>> really no problem. I track my patches and generally simply keep
>> pestering
>> people for as long as it takes ;-)
>>
> Very sensible!
In this case I was being a muppet. Had two running fixes branches
(requests just sent for both of them) and I'd applied it to the other
one. Hence when I got to the pull request it was in both of them.
Have dropped it from the post merge window one as it was fine in the
other.
Oops!
>> Heiko
>
prev parent reply other threads:[~2015-07-13 20:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 14:17 [PATCH RESEND] iio: adc: rockchip_saradc: add missing MODULE_* data Heiko Stuebner
2015-07-08 14:17 ` Heiko Stuebner
2015-07-11 17:32 ` Jonathan Cameron
2015-07-11 17:32 ` Jonathan Cameron
2015-07-11 18:59 ` Heiko Stübner
2015-07-11 18:59 ` Heiko Stübner
2015-07-13 9:23 ` Jonathan Cameron
2015-07-13 9:23 ` Jonathan Cameron
2015-07-13 20:52 ` 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=55A424F6.6080304@kernel.org \
--to=jic23@kernel.org \
--cc=heiko@sntech.de \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pmeerw@pmeerw.net \
/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.