From: Andrew Lunn <andrew@lunn.ch>
To: Liang Xu <lxu@maxlinear.com>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>,
"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"vee.khee.wong@linux.intel.com" <vee.khee.wong@linux.intel.com>,
Hauke Mehrtens <hmehrtens@maxlinear.com>,
Thomas Mohren <tmohren@maxlinear.com>,
"mohammad.athari.ismail@intel.com"
<mohammad.athari.ismail@intel.com>
Subject: Re: [PATCH v5 2/2] net: phy: add Maxlinear GPY115/21x/24x driver
Date: Wed, 7 Jul 2021 17:22:15 +0200 [thread overview]
Message-ID: <YOXGp39i6foOHv02@lunn.ch> (raw)
In-Reply-To: <c4772ca8-42e3-9c9d-2388-e19acb19e073@maxlinear.com>
> Is the merging failure due to the tree declaration? Or something else I also
> need take care.
It is probably due to the tree declaration, assuming you are actually
using the correct tree.
> When did the net-next was closed? I saw some other patches after 1 Jul were
> accepted, how many days before the close should I submit?
It varies by subsystem. ARM SoC tends to close around a week before
the merge window opens. netdev sees some patches accepted one or two
days after the merge window opens, but you should not assume patches
will be accepted that late. Also, you should submit patches earlier,
rather than later. They get more testing that way, you have time to
fix issues etc.
> Do I need re-submit the patch when net_next is open again, or the current patch
> will be pulled in next open window?
You need to resubmit.
Andrew
next prev parent reply other threads:[~2021-07-07 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 8:26 [PATCH v5 1/2] net: phy: add API to read 802.3-c45 IDs Xu Liang
2021-07-01 8:26 ` [PATCH v5 2/2] net: phy: add Maxlinear GPY115/21x/24x driver Xu Liang
2021-07-06 15:34 ` Liang Xu
2021-07-06 15:44 ` Russell King (Oracle)
[not found] ` <c4772ca8-42e3-9c9d-2388-e19acb19e073@maxlinear.com>
2021-07-07 15:22 ` Andrew Lunn [this message]
2021-07-08 5:04 ` Liang Xu
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=YOXGp39i6foOHv02@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=hmehrtens@maxlinear.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lxu@maxlinear.com \
--cc=mohammad.athari.ismail@intel.com \
--cc=netdev@vger.kernel.org \
--cc=tmohren@maxlinear.com \
--cc=vee.khee.wong@linux.intel.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.