netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: Vadim Fedorenko <vadfed@meta.com>,
	Jonathan Lemon <jonathan.lemon@gmail.com>,
	Richard Cochran <richardcochran@gmail.com>,
	netdev@vger.kernel.org
Subject: Re: [net-next] ptp_ocp: add force_irq to xilinx_spi configuration
Date: Wed, 8 Mar 2023 18:25:23 -0800	[thread overview]
Message-ID: <20230308182523.42c00e3b@kernel.org> (raw)
In-Reply-To: <520eb192-8b56-dde1-1b37-494a0d4d14b6@linux.dev>

On Wed, 8 Mar 2023 19:01:22 +0000 Vadim Fedorenko wrote:
> On 06/03/2023 21:22, Jakub Kicinski wrote:
> > On Mon, 6 Mar 2023 13:20:13 -0800 Jakub Kicinski wrote:  
> >> Hm, you're right. Any idea why both kbuild bot and our own CI think
> >> this doesn't build, then?  
> > 
> > Probably because they both use master :S
> > 
> > kernel test robot folks, could you please switch from master to main
> > as the base for networking patches?  
> 
> Should I re-send it? It's marked as Deffered and is not going forward...

Yes, please, not sure why it's Deferred so let's do a resend.

      reply	other threads:[~2023-03-09  2:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 15:57 [net-next] ptp_ocp: add force_irq to xilinx_spi configuration Vadim Fedorenko
2023-03-06 18:17 ` kernel test robot
2023-03-06 20:49 ` Jakub Kicinski
2023-03-06 21:10   ` Vadim Fedorenko
2023-03-06 21:20     ` Jakub Kicinski
2023-03-06 21:22       ` Jakub Kicinski
2023-03-06 22:47         ` Vadim Fedorenko
2023-03-08 19:01         ` Vadim Fedorenko
2023-03-09  2:25           ` Jakub Kicinski [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=20230308182523.42c00e3b@kernel.org \
    --to=kuba@kernel.org \
    --cc=jonathan.lemon@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=vadfed@meta.com \
    --cc=vadim.fedorenko@linux.dev \
    /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).