netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <simon.horman@corigine.com>
To: "Csókás Bence" <csokas.bence@prolan.hu>
Cc: netdev@vger.kernel.org,
	Richard Cochran <richardcochran@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Ahmad Fatoum <a.fatoum@pengutronix.de>,
	Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
	Andrew Lunn <andrew@lunn.ch>,
	kernel@pengutronix.de
Subject: Re: [PATCH resubmit] net: fec: Refactor: rename `adapter` to `fep`
Date: Tue, 4 Jul 2023 20:38:01 +0100	[thread overview]
Message-ID: <ZKR1GfkhHIVW+iov@corigine.com> (raw)
In-Reply-To: <20230704114058.5785-1-csokas.bence@prolan.hu>

On Tue, Jul 04, 2023 at 01:40:59PM +0200, Csókás Bence wrote:
> Rename local `struct fec_enet_private *adapter` to `fep` in `fec_ptp_gettime()` to match the rest of the driver
> 
> Signed-off-by: Csókás Bence <csokas.bence@prolan.hu>

Hi Csókás,

I'm assuming this is targeted at 'net-next', as opposed to 'net',
which is for fixes (I'm never sure with documentation). In any case,
the target tree should be included in the subject.

        Subject: [PATCH net-next resubmit] ...

If it is for net-next, then please repost when net-next reopens after July 10th.

Link: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle

-- 
pw-bot: deferred


  reply	other threads:[~2023-07-04 19:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 11:40 [PATCH resubmit] net: fec: Refactor: rename `adapter` to `fep` Csókás Bence
2023-07-04 19:38 ` Simon Horman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-05  9:44 Csókás Bence
2023-06-05  9:51 ` Marc Kleine-Budde
2023-06-05 12:35   ` Csókás Bence
2023-06-05 12:43     ` Marc Kleine-Budde
2023-06-05 12:51     ` Ahmad Fatoum
2023-06-05 18:27 ` Maciej Fijalkowski

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=ZKR1GfkhHIVW+iov@corigine.com \
    --to=simon.horman@corigine.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=andrew@lunn.ch \
    --cc=csokas.bence@prolan.hu \
    --cc=davem@davemloft.net \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.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).