devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Rafal Ozieblo <rafalo@cadence.com>
Cc: devicetree@vger.kernel.org, netdev@vger.kernel.org,
	nicolas.ferre@atmel.com, linux-kernel@vger.kernel.org,
	andrei.pistirica@microchip.com, harini.katakam@xilinx.com,
	David Miller <davem@davemloft.net>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/4] net: macb: macb.c changed to macb_main.c
Date: Tue, 6 Jun 2017 20:39:33 +0200	[thread overview]
Message-ID: <20170606183933.GA1205@localhost.localdomain> (raw)
In-Reply-To: <1496413661-21452-1-git-send-email-rafalo@cadence.com>

On Fri, Jun 02, 2017 at 03:27:41PM +0100, Rafal Ozieblo wrote:
>  drivers/net/ethernet/cadence/macb.c      | 3568 ------------------------------
>  drivers/net/ethernet/cadence/macb_main.c | 3568 ++++++++++++++++++++++++++++++

You deleted macb.c, and so ...

> diff --git a/drivers/net/ethernet/cadence/Makefile b/drivers/net/ethernet/cadence/Makefile
> index 4ba7559..31ea6e3 100644
> --- a/drivers/net/ethernet/cadence/Makefile
> +++ b/drivers/net/ethernet/cadence/Makefile
> @@ -1,6 +1,7 @@
>  #
>  # Makefile for the Atmel network device drivers.
>  #
> +macb-y	:= macb_main.o
>  
>  obj-$(CONFIG_MACB) += macb.o

how does this rule make sense any more?

Thanks,
Richard

  reply	other threads:[~2017-06-06 18:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 14:23 [PATCH v2 0/4] PTP support for macb driver Rafal Ozieblo
2017-06-02 14:26 ` [PATCH v2 1/4] net: macb: Add support for PTP timestamps in DMA descriptors Rafal Ozieblo
2017-06-02 14:27 ` [PATCH v2 2/4] net: macb: Add tsu_clk to device tree Rafal Ozieblo
     [not found] ` <1496413439-12900-1-git-send-email-rafalo-vna1KIf7WgpBDgjK7y7TUQ@public.gmane.org>
2017-06-02 14:27   ` [PATCH v2 3/4] net: macb: macb.c changed to macb_main.c Rafal Ozieblo
2017-06-06 18:39     ` Richard Cochran [this message]
     [not found]       ` <20170606183933.GA1205-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2017-06-06 19:00         ` David Miller
     [not found]           ` <20170606.150015.1247326483451270973.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-06-06 20:22             ` Richard Cochran
2017-06-02 14:28 ` [PATCH v2 4/4] net: macb: Add hardware PTP support Rafal Ozieblo
     [not found]   ` <1496413690-22826-1-git-send-email-rafalo-vna1KIf7WgpBDgjK7y7TUQ@public.gmane.org>
2017-06-04 20:55     ` Richard Cochran
2017-06-06  8:54       ` Rafal Ozieblo
     [not found]         ` <BN3PR07MB251673623B941CAF5DEAB474C9CB0-EldUQEzkDQfxGZiqM5fOI+FPX92sqiQdvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-06-06 18:36           ` Richard Cochran
2017-06-06 18:33   ` Richard Cochran
2017-06-07 11:13     ` Rafal Ozieblo
     [not found]       ` <BN3PR07MB2516A47C2CFEB58BCFFB2C46C9C80-EldUQEzkDQfxGZiqM5fOI+FPX92sqiQdvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-06-07 13:28         ` Richard Cochran
2017-06-08 12:48           ` Rafal Ozieblo

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=20170606183933.GA1205@localhost.localdomain \
    --to=richardcochran@gmail.com \
    --cc=andrei.pistirica@microchip.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=harini.katakam@xilinx.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.ferre@atmel.com \
    --cc=rafalo@cadence.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).