[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a3TE+ou_-Gban+__n+n8bN0B0jK7ofpoOr_=hmuHtcuuw@mail.gmail.com>
Date: Fri, 9 Nov 2018 12:08:01 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Sunil Kovvuri <sunil.kovvuri@...il.com>
Cc: Networking <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>, linux-soc@...r.kernel.org,
Sunil Goutham <sgoutham@...vell.com>
Subject: Re: [PATCH 00/20] octeontx2-af: NPC MCAM support and FLR handling
On Fri, Nov 9, 2018 at 5:35 AM Sunil Kovvuri <sunil.kovvuri@...il.com> wrote:
> On Fri, Nov 9, 2018 at 2:32 AM Arnd Bergmann <arnd@...db.de> wrote:
> > On Thu, Nov 8, 2018 at 7:36 PM <sunil.kovvuri@...il.com> wrote:
> > > From: Sunil Goutham <sgoutham@...vell.com>
> >
> > Hmm, I noticed that you use a different address as the patch author
> > and the submitter. I'm guessing that "Sunil Goutham" and
> > "Sunil Kovvuri" actually refer to the same person, and you just
> > need to pick which of the two email addresses you want to use
> > for public communication, but that's not obvious here.
> >
> > However, if there are actually two different Sunil's here, then
> > you need to add that second Signed-off-by.
> >
>
> No, it's just me.
> Sometimes code indentation becomes messy and difficult to read, if i use
> corporate mail server to submit patches. So i have been using gmail.
Ok, I see. Ideally you should try to get the company mail server fixed
of course. A possible workaround is to add your marvell address as
an alias in gmail, which allows 'git send email' to send out mails with
the other address as the sender. This may however fail if the marvell
mail server uses SPF, as mail clients might then consider your
mails as forged.
Arnd
Powered by blists - more mailing lists