All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Pihet <jean.pihet@newoldbits.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Ryan Barnett <ryan.barnett@rockwellcollins.com>,
	Conrad Ratschan <conrad.ratschan@rockwellcollins.com>,
	Hugo Cornelis <hugo.cornelis@essensium.com>,
	Arnout Vandecappelle <arnout.vandecappelle@essensium.com>
Subject: Re: [PATCH 1/2] net: dsa: ksz: pad frame to 64 bytes for transmission
Date: Sun, 29 Nov 2020 20:35:04 +0100	[thread overview]
Message-ID: <CAORVsuXaSYR_n0s5DSqewMotPc+c6EPi-ANGrhuvoesqSddPYA@mail.gmail.com> (raw)
In-Reply-To: <20201129165734.GB2234159@lunn.ch>

Andrew,

On Sun, Nov 29, 2020 at 5:57 PM Andrew Lunn <andrew@lunn.ch> wrote:
>
> Hi Jean
>
> Please also include a patch 0/X which describes the patchset as a
> whole. This will be used as the branch merge commit.

Sure, will submit a v2 asap.

Thx,
Jean

>
>        Andrew

      reply	other threads:[~2020-11-29 19:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-29 10:23 [PATCH 1/2] net: dsa: ksz: pad frame to 64 bytes for transmission Jean Pihet
2020-11-29 10:24 ` [PATCH 2/2] net: dsa: ksz8795: adjust CPU link to host interface Jean Pihet
2020-11-29 12:51   ` kernel test robot
2020-11-29 12:51     ` kernel test robot
2020-11-29 12:51   ` [RFC PATCH] net: dsa: ksz8795: ksz8795_adjust_link() can be static kernel test robot
2020-11-29 12:51     ` kernel test robot
2020-11-29 13:17   ` [PATCH 2/2] net: dsa: ksz8795: adjust CPU link to host interface kernel test robot
2020-11-29 13:17     ` kernel test robot
2020-11-29 17:07   ` Andrew Lunn
2020-11-29 16:56 ` [PATCH 1/2] net: dsa: ksz: pad frame to 64 bytes for transmission Andrew Lunn
2020-11-29 19:34   ` Jean Pihet
2020-11-29 19:38     ` Andrew Lunn
2020-11-29 19:48       ` Jean Pihet
2020-11-29 16:57 ` Andrew Lunn
2020-11-29 19:35   ` Jean Pihet [this message]

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=CAORVsuXaSYR_n0s5DSqewMotPc+c6EPi-ANGrhuvoesqSddPYA@mail.gmail.com \
    --to=jean.pihet@newoldbits.com \
    --cc=andrew@lunn.ch \
    --cc=arnout.vandecappelle@essensium.com \
    --cc=conrad.ratschan@rockwellcollins.com \
    --cc=hugo.cornelis@essensium.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ryan.barnett@rockwellcollins.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.