From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Fengguang Wu <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kbuild-all-JC7UmRfGjtg@public.gmane.org,
Anders Berg <anders.berg-1wcpHE2jlwO1Z/+hSey0Gg@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [wsa:i2c/quirks 7/11] drivers/i2c/busses/i2c-axxia.c:452:27: sparse: symbol 'axxia_i2c_quirks' was not declared. Should it be static?
Date: Fri, 9 Jan 2015 11:57:12 +0100 [thread overview]
Message-ID: <20150109105712.GA1053@katana> (raw)
In-Reply-To: <20150108215137.GA11727-q6ZYBFIlbFFi0tQiZxhdj1DQ4js95KgL@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
Hi Fengguang,
> It's normally private emails, except for the ones that carry patches
> with them. In which case public mailing lists will also be CCed.
OK, thought so.
> > Is there a way to achieve this? I know that adding "experimental" to the
> > branch name will skip the testing. Is there another pattern to prevent
> > sending mails to everyone?
>
> I wonder if the occasional public emails are acceptable to you.
Not really. If I push out development code which is good enough to be
build tested but not ready to be sent upstream yet, I think other people
and mailing lists should not be bothered.
> not, it'd be trivial for me to add a list of "personal git trees"
> where all emails including the auto generated patches will be kept
> private (if commit author == committer).
For my workflow, everything except "for-current" and "for-next" should
be private. I do appreciate the patches for those two, so thanks for
that in general!
All the best,
Wolfram
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Anders Berg <anders.berg@avagotech.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [wsa:i2c/quirks 7/11] drivers/i2c/busses/i2c-axxia.c:452:27: sparse: symbol 'axxia_i2c_quirks' was not declared. Should it be static?
Date: Fri, 9 Jan 2015 11:57:12 +0100 [thread overview]
Message-ID: <20150109105712.GA1053@katana> (raw)
In-Reply-To: <20150108215137.GA11727@wfg-t540p.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
Hi Fengguang,
> It's normally private emails, except for the ones that carry patches
> with them. In which case public mailing lists will also be CCed.
OK, thought so.
> > Is there a way to achieve this? I know that adding "experimental" to the
> > branch name will skip the testing. Is there another pattern to prevent
> > sending mails to everyone?
>
> I wonder if the occasional public emails are acceptable to you.
Not really. If I push out development code which is good enough to be
build tested but not ready to be sent upstream yet, I think other people
and mailing lists should not be bothered.
> not, it'd be trivial for me to add a list of "personal git trees"
> where all emails including the auto generated patches will be kept
> private (if commit author == committer).
For my workflow, everything except "for-current" and "for-next" should
be private. I do appreciate the patches for those two, so thanks for
that in general!
All the best,
Wolfram
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-01-09 10:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 17:57 [wsa:i2c/quirks 7/11] drivers/i2c/busses/i2c-axxia.c:452:27: sparse: symbol 'axxia_i2c_quirks' was not declared. Should it be static? kbuild test robot
2015-01-08 17:57 ` kbuild test robot
2015-01-08 17:57 ` [PATCH wsa] i2c: axxia: axxia_i2c_quirks can be static kbuild test robot
2015-01-08 18:28 ` [wsa:i2c/quirks 7/11] drivers/i2c/busses/i2c-axxia.c:452:27: sparse: symbol 'axxia_i2c_quirks' was not declared. Should it be static? Wolfram Sang
2015-01-08 21:51 ` Fengguang Wu
2015-01-08 21:51 ` Fengguang Wu
[not found] ` <20150108215137.GA11727-q6ZYBFIlbFFi0tQiZxhdj1DQ4js95KgL@public.gmane.org>
2015-01-09 10:57 ` Wolfram Sang [this message]
2015-01-09 10:57 ` 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=20150109105712.GA1053@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=anders.berg-1wcpHE2jlwO1Z/+hSey0Gg@public.gmane.org \
--cc=fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=kbuild-all-JC7UmRfGjtg@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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.