From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Jakub Kicinski <kuba@kernel.org>
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: Mon, 6 Mar 2023 22:47:17 +0000 [thread overview]
Message-ID: <8d7c2cd4-3a79-d10a-4939-2aee152221b2@linux.dev> (raw)
In-Reply-To: <20230306132200.15d2dbfb@kernel.org>
On 06.03.2023 21:22, Jakub Kicinski wrote:
> On Mon, 6 Mar 2023 13:20:13 -0800 Jakub Kicinski wrote:
>> On Mon, 6 Mar 2023 21:10:40 +0000 Vadim Fedorenko wrote:
>>> On 06.03.2023 20:49, Jakub Kicinski wrote:
>>>> Give it until Friday, the patch needs to be in the networking trees
>>>> (our PR cadence during the merge window is less regular than outside
>>>> it).
>>>
>>> Looks like "1dd46599f83a spi: xilinx: add force_irq for QSPI mode" is in net and
>>> net-next trees already? Or which patch are you talking about?
>>
>> 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?
Very interesting side effect of renaming!
Thanks!
next prev parent reply other threads:[~2023-03-06 22:47 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 [this message]
2023-03-08 19:01 ` Vadim Fedorenko
2023-03-09 2:25 ` 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=8d7c2cd4-3a79-d10a-4939-2aee152221b2@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=vadfed@meta.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.