From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Badel, Laurent" <LaurentBadel@eaton.com>
Cc: "fugang.duan@nxp.com" <fugang.duan@nxp.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"richard.leitner@skidata.com" <richard.leitner@skidata.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"alexander.levin@microsoft.com" <alexander.levin@microsoft.com>,
"Quette, Arnaud" <ArnaudQuette@eaton.com>
Subject: Re: [EXTERNAL] Re: [PATCH 1/2] Revert commit 1b0a83ac04e383e3bed21332962b90710fcf2828
Date: Wed, 29 Apr 2020 13:54:32 +0200 [thread overview]
Message-ID: <20200429115432.GA2119907@kroah.com> (raw)
In-Reply-To: <CH2PR17MB3542C31656800914A5D61977DFAD0@CH2PR17MB3542.namprd17.prod.outlook.com>
On Wed, Apr 29, 2020 at 11:22:58AM +0000, Badel, Laurent wrote:
> Dear Greg,
>
> Thanks for your reply and sorry for my mistake.
> Looks to me like the issue is the commit hash which should be 12 chars.
> Does that mean I need to fix and resend the whole thing to everyone?
Yes please, never force a maintainer to hand-edit a patch, they will not
do so :)
thanks,
greg k-h
next prev parent reply other threads:[~2020-04-29 11:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 9:03 [PATCH 1/2] Revert commit 1b0a83ac04e383e3bed21332962b90710fcf2828 Badel, Laurent
2020-04-29 9:40 ` gregkh
2020-04-29 11:22 ` [EXTERNAL] " Badel, Laurent
2020-04-29 11:54 ` gregkh [this message]
2020-04-29 13:56 ` Andrew Lunn
-- strict thread matches above, loose matches on Subject: below --
2020-04-29 11:59 Badel, Laurent
2020-04-29 15:25 ` Andrew Lunn
2020-04-29 15:48 ` [EXTERNAL] " Badel, Laurent
2020-04-29 16:35 ` Andrew Lunn
2020-04-30 9:02 ` Badel, Laurent
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=20200429115432.GA2119907@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ArnaudQuette@eaton.com \
--cc=LaurentBadel@eaton.com \
--cc=alexander.levin@microsoft.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=hkallweit1@gmail.com \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=richard.leitner@skidata.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;
as well as URLs for NNTP newsgroup(s).