linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH 1/1] ptp: ptp_dte: simplify getting .driver_data
Date: Mon, 22 Oct 2018 15:43:11 -0700	[thread overview]
Message-ID: <20181022224311.xpzs6piq5khgg3t5@localhost> (raw)
In-Reply-To: <20181021200039.1933-2-wsa+renesas@sang-engineering.com>

On Sun, Oct 21, 2018 at 10:00:39PM +0200, Wolfram Sang wrote:
> We should get 'driver_data' from 'struct device' directly. Going via
> platform_device is an unneeded step back and forth.

Acked-by: Richard Cochran <richardcochran@gmail.com>

  reply	other threads:[~2018-10-22 22:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-21 20:00 [PATCH 0/1] ptp: " Wolfram Sang
2018-10-21 20:00 ` [PATCH 1/1] ptp: ptp_dte: " Wolfram Sang
2018-10-22 22:43   ` Richard Cochran [this message]
2018-10-23  2:49   ` David Miller

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=20181022224311.xpzs6piq5khgg3t5@localhost \
    --to=richardcochran@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    --subject='Re: [PATCH 1/1] ptp: ptp_dte: simplify getting .driver_data' \
    /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

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).