netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@codeaurora.org>
To: David Miller <davem@davemloft.net>
Cc: alokc@codeaurora.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] net: qcom/emac: move phy init code to separate files
Date: Thu, 24 Nov 2016 10:39:42 -0600	[thread overview]
Message-ID: <583717CE.9070704@codeaurora.org> (raw)
In-Reply-To: <20161124.113220.1130207009395086230.davem@davemloft.net>

David Miller wrote:
> Please do not place empty blank lines at the end of files.
>
> GIT even warns about this.

I need to rework this patchset anyway, and it won't be ready in time for 
4.10.  I will definitely fix this problem.  Thanks.

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, hosted by The Linux Foundation.

  reply	other threads:[~2016-11-24 16:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21 22:58 [PATCH 0/2] net: qcom/emac: simplify support for different SOCs Timur Tabi
2016-11-21 22:58 ` [PATCH 1/2] net: qcom/emac: move phy init code to separate files Timur Tabi
2016-11-24 16:32   ` David Miller
2016-11-24 16:39     ` Timur Tabi [this message]
2016-11-21 22:58 ` [PATCH 2/2] net: qcom/emac: add support for the Qualcomm Technologies QDF2400 Timur Tabi
2016-11-22 22:14   ` Timur Tabi
  -- strict thread matches above, loose matches on Subject: below --
2016-12-07 20:39 [PATCH 0/2] net: qcom/emac: simplify support for different SOCs Timur Tabi
2016-12-07 20:39 ` [PATCH 1/2] net: qcom/emac: move phy init code to separate files Timur Tabi

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=583717CE.9070704@codeaurora.org \
    --to=timur@codeaurora.org \
    --cc=alokc@codeaurora.org \
    --cc=davem@davemloft.net \
    --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).