linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ansuel Smith <ansuelsmth@gmail.com>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net-next PATCH 1/4] drivers: net: dsa: qca8k: drop MTU tracking from qca8k_priv
Date: Fri, 25 Mar 2022 00:24:44 +0100	[thread overview]
Message-ID: <Yjz9vNrHvFxCxAY1@Ansuel-xps.localdomain> (raw)
In-Reply-To: <20220324231423.qyyyd72nn75i7kdc@skbuf>

On Fri, Mar 25, 2022 at 01:14:23AM +0200, Vladimir Oltean wrote:
> On Fri, Mar 25, 2022 at 12:10:19AM +0100, Ansuel Smith wrote:
> > Ok i'm reworking this in v2 with the stmmac change and the change to
> > change mtu following what is done for mt7530. Thx a lot for the
> > suggestion. Happy that the additional space can be dropped and still use
> > a more correct and simple approach.
> 
> That's all fine, but if you read the news you'll notice that net-next is
> currently closed and will probably be so for around 2 weeks.
> The pull request for 5.18 was sent by Jakub yesterday:
> https://patchwork.kernel.org/project/netdevbpf/patch/20220323180738.3978487-1-kuba@kernel.org/
> Not sure why the status page says it's still open, it'll probably be
> updated eventually:
> http://vger.kernel.org/~davem/net-next.html

Thanks for the alert! I will send an RFC then hoping to get some review
tag.
About the html page, I was also confused some times ago where net-next
was closed and the page was with the "We are open" image. Wonder if it's
a CDN problem? No idea but to me that page looks to be a quicker way
than checking net-next last commit or checking the mailing list.

-- 
	Ansuel

  reply	other threads:[~2022-03-24 23:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22  1:45 [net-next PATCH 0/4] Reduce qca8k_priv space usage Ansuel Smith
2022-03-22  1:45 ` [net-next PATCH 1/4] drivers: net: dsa: qca8k: drop MTU tracking from qca8k_priv Ansuel Smith
2022-03-22 11:58   ` Vladimir Oltean
2022-03-22 13:38     ` Ansuel Smith
2022-03-22 13:55       ` Vladimir Oltean
2022-03-22 14:03         ` Ansuel Smith
2022-03-24 10:45           ` Vladimir Oltean
2022-03-24 20:44             ` Ansuel Smith
2022-03-24 21:05               ` Vladimir Oltean
2022-03-24 23:10                 ` Ansuel Smith
2022-03-24 23:14                   ` Vladimir Oltean
2022-03-24 23:24                     ` Ansuel Smith [this message]
2022-03-22  1:45 ` [net-next PATCH 2/4] drivers: net: dsa: qca8k: drop port_sts " Ansuel Smith
2022-03-22  1:45 ` [net-next PATCH 3/4] drivers: net: dsa: qca8k: rework and simplify mdiobus logic Ansuel Smith
2022-03-22  1:45 ` [net-next PATCH 4/4] drivers: net: dsa: qca8k: drop dsa_switch_ops from qca8k_priv Ansuel Smith

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=Yjz9vNrHvFxCxAY1@Ansuel-xps.localdomain \
    --to=ansuelsmth@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=vivien.didelot@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).