From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the gpio tree with the kspp-gustavo tree
Date: Wed, 18 Nov 2020 05:00:57 -0600 [thread overview]
Message-ID: <20201118110057.GA30719@embeddedor> (raw)
In-Reply-To: <CAHp75Vcuxc1Ypo6GV_a2hACWPFqg4m8mZr8mLHD=LgWpLLEWMg@mail.gmail.com>
Hi Andy,
On Wed, Nov 18, 2020 at 12:52:25PM +0200, Andy Shevchenko wrote:
> On Wed, Nov 18, 2020 at 11:29 AM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> > On Wed, Nov 18, 2020 at 9:53 AM Linus Walleij <linus.walleij@linaro.org> wrote:
> > > On Wed, Nov 18, 2020 at 4:24 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > > b8e0b635e6e6 ("gpio: Fix fall-through warnings for Clang")
> > > >
> > > > from the kspp-gustavo tree and commit:
>
> Gustavo, one remark though. It's not okay to hide changes from
> maintainers. I have checked
> b8e0b635e6e6 ("gpio: Fix fall-through warnings for Clang") and found
> nothing except your SoB.
>
> Please, inform maintainers about changes you are doing in their realm(s).
Sorry about that. I'll remove that change from my tree. I just wanted to
test some changes in linux-next.
Thanks for the feedback.
--
Gustavo
next prev parent reply other threads:[~2020-11-18 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 3:24 linux-next: manual merge of the gpio tree with the kspp-gustavo tree Stephen Rothwell
2020-11-18 7:49 ` Linus Walleij
2020-11-18 9:29 ` Andy Shevchenko
2020-11-18 10:52 ` Andy Shevchenko
2020-11-18 11:00 ` Gustavo A. R. Silva [this message]
2020-11-18 14:15 ` Andy Shevchenko
2020-11-18 20:38 ` Gustavo A. R. Silva
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=20201118110057.GA30719@embeddedor \
--to=gustavoars@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=gustavo@embeddedor.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).