Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 24 Jul 2019 11:14:35 -0700 (PDT)
Message-Id: <20190724.111435.1790922345411569346.davem@davemloft.net>
To:     hslester96@gmail.com
Cc:     klassert@kernel.org, jcliburn@gmail.com, chris.snook@gmail.com,
        rmody@marvell.com, michael.chan@broadcom.com,
        siva.kallam@broadcom.com, prashant@broadcom.com,
        GR-Linux-NIC-Dev@marvell.com, jeffrey.t.kirsher@intel.com,
        cooldavid@cooldavid.org, intel-wired-lan@lists.osuosl.org,
        netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/8] Use dev_get_drvdata where possible
From:   David Miller <davem@davemloft.net>
In-Reply-To: <20190724060512.23899-1-hslester96@gmail.com>
References: <20190724060512.23899-1-hslester96@gmail.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

From: Chuhong Yuan <hslester96@gmail.com>
Date: Wed, 24 Jul 2019 14:05:12 +0800

> These patches use dev_get_drvdata instead of
> using to_pci_dev + pci_get_drvdata to make
> code simpler where possible.
> 
> Changelog:
> 
> v1 -> v2:
> - Change pci_set_drvdata to dev_set_drvdata
>   to keep consistency.

Some of these patches were applied yesterday, weren't they?

Please take that into consideration when you repost, especially
when the maintainer(s) explicitly reply to your patches saying
"Applied." or similar like I always do.

Thanks.