netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ruud Bos <kernel.hbk@gmail.com>
To: netdev@vger.kernel.org
Cc: richardcochran@gmail.com, davem@davemloft.net, kuba@kernel.org,
	jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com
Subject: Re: [PATCH net-next 0/4] igb: support PEROUT and EXTTS PTP pin functions on 82580/i354/i350
Date: Tue, 12 Oct 2021 17:43:52 +0200	[thread overview]
Message-ID: <CAA0z7By8Rz+3dqMF8_WXRZuvG7K_Mrgm209Zpsk6C0urG1cOnA@mail.gmail.com> (raw)
In-Reply-To: <YV2f7F/WmuJq/A79@bullseye>

On Wed, Oct 6, 2021 at 3:09 PM Ruud Bos <kernel.hbk@gmail.com> wrote:
>
> Hi,
>
> My apologies for the huge delay in resending this patch set.
>
> I tried  setting up my corporate e-mail to work on Linux to be able to use
> git send-email and getting rid of the automatically appended
> confidentiality claim. Eventually I gave up on getting this sorted, hence
> the different e-mail address.
>
> Anyway, I have re-spun the patch series atop net-next.
> Feedback is welcome.
>
> Regards,
> Ruud

Ping?
I did not receive any response to my patches yet.
Does that mean I did something wrong?

Regards,
Ruud

  reply	other threads:[~2021-10-12 15:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06 12:58 [PATCH net-next 0/4] igb: support PEROUT and EXTTS PTP pin functions on 82580/i354/i350 Ruud Bos
2021-10-06 12:58 ` [PATCH net-next 1/4] igb: move SDP config initialization to separate function Ruud Bos
2021-10-06 12:58 ` [PATCH net-next 2/4] igb: move PEROUT and EXTTS isr logic to separate functions Ruud Bos
2021-10-06 12:58 ` [PATCH net-next 3/4] igb: support PEROUT on 82580/i354/i350 Ruud Bos
2021-10-06 12:58 ` [PATCH net-next 4/4] support EXTTS " Ruud Bos
2021-10-06 13:09 ` [PATCH net-next 0/4] igb: support PEROUT and EXTTS PTP pin functions " Ruud Bos
2021-10-12 15:43   ` Ruud Bos [this message]
2021-10-12 15:49     ` Jakub Kicinski
2021-10-12 15:53       ` Nguyen, Anthony L
  -- strict thread matches above, loose matches on Subject: below --
2021-07-19  6:25 Ruud Bos
2021-07-19 10:09 ` Jakub Kicinski

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=CAA0z7By8Rz+3dqMF8_WXRZuvG7K_Mrgm209Zpsk6C0urG1cOnA@mail.gmail.com \
    --to=kernel.hbk@gmail.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=jesse.brandeburg@intel.com \
    --cc=kuba@kernel.org \
    --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).