From: Wolfram Sang <wsa@the-dreams.de>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Wolfram Sang <wsa-dev@sang-engineering.com>,
kbuild-all@01.org, linux-i2c@vger.kernel.org
Subject: Re: [wsa:renesas/sdhi-uniphier 2/22] drivers/mmc/host/tmio_mmc.h:249:2: error: implicit declaration of function 'readsw'
Date: Mon, 4 Dec 2017 17:00:27 +0100 [thread overview]
Message-ID: <20171204160024.yv3ztu2ntn2l2l3j@ninjato> (raw)
In-Reply-To: <201712030902.U17suQaZ%fengguang.wu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
Hey guys,
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/sdhi-uniphier
buildbot is a really great and helpful service, so a lot of thanks for
that.
But please, again, drop the i2c mailing list for my personal development
branches. *Only* include the i2c list, if there is an "i2c/" prefix in
the branch name. This branch, for example, is MMC related and has
nothing to do with I2C! Or, if this is not possible, drop the I2C list
from all my branches and just mail me and the author.
The current state creates too much noise and it starts to get a little
annoying. Please let's find some fix for that. buildbot is so useful
otherwise.
Kind regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-04 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 1:30 [wsa:renesas/sdhi-uniphier 2/22] drivers/mmc/host/tmio_mmc.h:249:2: error: implicit declaration of function 'readsw' kbuild test robot
2017-12-04 16:00 ` Wolfram Sang [this message]
2017-12-05 3:24 ` Fengguang Wu
2017-12-05 10:30 ` Wolfram Sang
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=20171204160024.yv3ztu2ntn2l2l3j@ninjato \
--to=wsa@the-dreams.de \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-i2c@vger.kernel.org \
--cc=wsa-dev@sang-engineering.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