From: David Miller <davem@davemloft.net>
To: nikita.yoush@cogentembedded.com
Cc: lkp@intel.com, kbuild-all@01.org, fugang.duan@nxp.com,
troy.kisky@boundarydevices.com, andrew@lunn.ch, eric@nelint.com,
tremyfr@gmail.com, johannes@sipsolutions.net,
netdev@vger.kernel.org, cphealy@gmail.com, fabio.estevam@nxp.com,
linux-kernel@vger.kernel.org
Subject: Re: [patch net v2] net: fec: fix compile with CONFIG_M5272
Date: Mon, 05 Dec 2016 12:28:20 -0500 (EST) [thread overview]
Message-ID: <20161205.122820.1477248218044200770.davem@davemloft.net> (raw)
In-Reply-To: <90474527-926c-b66f-831b-3fb6f7128394@cogentembedded.com>
From: Nikita Yushchenko <nikita.yoush@cogentembedded.com>
Date: Mon, 5 Dec 2016 20:26:52 +0300
>> From: Nikita Yushchenko <nikita.yoush@cogentembedded.com>
>> Date: Mon, 5 Dec 2016 16:55:04 +0300
>>
>>> Aieee I was typing too fast today, sorry...
>>>
>>> send separate "fix for the fix", or re-send patch without that silly typo?
>>
>> If the patch hasn't been applied yet, you resend a fixed version of the
>> patch, always.
>
> Ok, will repost shortly.
>
> What I don't understand is - how could test robot fetch it before it was
> applied?
It takes them from the mailing list, and exactly this is the value of
the robot. It can test patches before I add them to my tree.
prev parent reply other threads:[~2016-12-05 17:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 8:16 [patch net v2] net: fec: fix compile with CONFIG_M5272 Nikita Yushchenko
2016-12-05 9:08 ` Andy Duan
2016-12-05 9:16 ` Geert Uytterhoeven
2016-12-05 10:02 ` Fabio Estevam
2016-12-05 13:18 ` kbuild test robot
2016-12-05 13:55 ` Nikita Yushchenko
2016-12-05 14:03 ` Nikita Yushchenko
[not found] ` <51f44adf-486c-2e60-97c1-037d448fad49@cogentembedded.com>
2016-12-05 17:14 ` David Miller
2016-12-05 17:26 ` Nikita Yushchenko
2016-12-05 17:28 ` David Miller [this message]
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=20161205.122820.1477248218044200770.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=cphealy@gmail.com \
--cc=eric@nelint.com \
--cc=fabio.estevam@nxp.com \
--cc=fugang.duan@nxp.com \
--cc=johannes@sipsolutions.net \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nikita.yoush@cogentembedded.com \
--cc=tremyfr@gmail.com \
--cc=troy.kisky@boundarydevices.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).