[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1228c09032a2cabc4b11b3a1e78f1b5da3eb1f49.camel@intel.com>
Date: Tue, 12 Oct 2021 15:53:45 +0000
From: "Nguyen, Anthony L" <anthony.l.nguyen@...el.com>
To: "kuba@...nel.org" <kuba@...nel.org>,
"Brandeburg, Jesse" <jesse.brandeburg@...el.com>
CC: "richardcochran@...il.com" <richardcochran@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"kernel.hbk@...il.com" <kernel.hbk@...il.com>
Subject: Re: [PATCH net-next 0/4] igb: support PEROUT and EXTTS PTP pin
functions on 82580/i354/i350
On Tue, 2021-10-12 at 08:49 -0700, Jakub Kicinski wrote:
> On Tue, 12 Oct 2021 17:43:52 +0200 Ruud Bos wrote:
> > On Wed, Oct 6, 2021 at 3:09 PM Ruud Bos <kernel.hbk@...il.com>
> > wrote:
> > > 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.
> >
> > Ping?
> > I did not receive any response to my patches yet.
> > Does that mean I did something wrong?
>
> These are supposed to go via Intel's trees.
> Let's point To: at Intel's maintainers.
Sorry, I must have missed this. Could you resend and add
intel-wired-lan@...ts.osuosl.org so that it can be reviewed there and
picked up by the Intel tree's patchworks?
Thanks,
Tony
Powered by blists - more mailing lists