From: Valentin Rothberg <valentinrothberg@gmail.com>
To: lars@metafoo.de
Cc: jic23@kernel.org, LKML <linux-kernel@vger.kernel.org>,
Andreas Ziegler <ziegler@cs.fau.de>
Subject: staging:iio:adis162** cleanup
Date: Tue, 5 Apr 2016 08:03:12 +0200 [thread overview]
Message-ID: <20160405060312.GA2094@doudou.informatik.uni-erlangen.de> (raw)
Hi Lars-Peter,
both of your commits 88ae3aedb8ec ("staging:iio:adis16204: Remove
adis16204 driver") and 2bcdb3f2e05f ("staging:iio:adis16220: Remove
adis16220 driver") have shown up in today's linux-next.
The corresponding Kconfig options are still referenced in the __initdata
struct in arch/blackfin/mach-bf537/boards/stamp.c. Shall I send a
trivial patch removing the two #if's or do you prefer to keep them?
I detected the issue with scripts/checkkconfigsymbols.py by diffing
yesterday's and today's linux-next.
Best regards,
Valentin
next reply other threads:[~2016-04-05 6:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 6:03 Valentin Rothberg [this message]
2016-04-05 17:33 ` Lars-Peter Clausen
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=20160405060312.GA2094@doudou.informatik.uni-erlangen.de \
--to=valentinrothberg@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ziegler@cs.fau.de \
/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
all inboxes | Powered by JetHome®