From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Fengguang Wu <wfg@linux.intel.com>
Cc: devel@driverdev.osuosl.org, linux-mtd@lists.infradead.org,
Kay Sievers <kay@vrfy.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [driver-core:driver-core-linus 6/6] drivers/firmware/iscsi_ibft_find.o: In function `kmsg_dump_rewind': (.text+0x18): multiple definition of `kmsg_dump_rewind'
Date: Fri, 15 Jun 2012 18:47:32 -0700 [thread overview]
Message-ID: <20120616014732.GA2981@kroah.com> (raw)
In-Reply-To: <20120616011646.GA7847@localhost>
On Sat, Jun 16, 2012 at 09:16:46AM +0800, Fengguang Wu wrote:
> Hi list,
>
> I'm sorry if this pile of build errors disturbed you too much. If
> the error notification is too permissive, I can limit it in two ways:
>
> 1) only notify build errors on the first kconfig. There may be a few
> new error messages show up in the other kconfig builds, however
> mostly are just irritating duplications.
Duplicates should be suppressed, they are just annoying.
> 2) only notify the mailing list directly associated with the git tree.
> In this particular case, to only CC devel@driverdev.osuosl.org, and
> to avoid the linux-mtd and linuxppc-dev lists.
Yes, that would be the best thing to do to start with, then let the
developers take it from there.
thanks,
greg k-h
next prev parent reply other threads:[~2012-06-16 1:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 0:02 [driver-core:driver-core-linus 6/6] drivers/firmware/iscsi_ibft_find.o: In function `kmsg_dump_rewind': (.text+0x18): multiple definition of `kmsg_dump_rewind' wfg
2012-06-16 1:15 ` Stephen Rothwell
2012-06-16 1:53 ` Fengguang Wu
2012-06-16 1:16 ` Fengguang Wu
2012-06-16 1:47 ` Greg Kroah-Hartman [this message]
2012-06-16 2:50 ` Reducing the noise level of build error notifications to 0 Fengguang Wu
2012-06-16 3:44 ` Greg Kroah-Hartman
2012-06-16 4:11 ` Fengguang Wu
2012-06-16 4:20 ` Fengguang Wu
2012-06-16 15:27 ` Greg Kroah-Hartman
2012-06-17 3:35 ` Fengguang Wu
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=20120616014732.GA2981@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=kay@vrfy.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=wfg@linux.intel.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 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.