From: David Miller <davem@davemloft.net>
To: ivan@de.ibm.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, chunkeey@gmail.com
Subject: Re: [PATCH 2/2] net/ibm/emac: deletion of unneeded macros definitions
Date: Fri, 31 Aug 2018 09:21:20 -0700 (PDT) [thread overview]
Message-ID: <20180831.092120.879936309673960672.davem@davemloft.net> (raw)
In-Reply-To: <20180831112345.16594-1-ivan@de.ibm.com>
From: Ivan Mikhaylov <ivan@de.ibm.com>
Date: Fri, 31 Aug 2018 14:23:45 +0300
>>Please do not delete these, they could be useful for other
>>developers and people reading this driver.
> Hmm, that's possible, need I resubmit first patch without this one?
Yes.
prev parent reply other threads:[~2018-08-31 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 16:43 [PATCH 2/2] net/ibm/emac: deletion of unneeded macros definitions Ivan Mikhaylov
2018-08-30 1:10 ` David Miller
2018-08-31 11:23 ` Ivan Mikhaylov
2018-08-31 16:21 ` 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=20180831.092120.879936309673960672.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chunkeey@gmail.com \
--cc=ivan@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 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).