From: Vladimir Oltean <olteanv@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: kernel test robot <lkp@intel.com>,
Christian Eggers <ceggers@arri.de>,
Woojung Huh <woojung.huh@microchip.com>,
kbuild-all@lists.01.org,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: dsa: point out the tail taggers
Date: Sat, 17 Oct 2020 00:33:02 +0300 [thread overview]
Message-ID: <20201016213302.yeesw4jbw3rzfluf@skbuf> (raw)
In-Reply-To: <20201016211628.mw7jlvqx3audzo76@skbuf>
On Sat, Oct 17, 2020 at 12:16:28AM +0300, Vladimir Oltean wrote:
> On Fri, Oct 16, 2020 at 11:03:18PM +0200, Andrew Lunn wrote:
> > 2ecbc1f684482b4ed52447a39903bd9b0f222898 does not have net-next, as
> > far as i see,
>
> Not sure what you mean by that.
Ah, I do understand what you mean now. In git, that is what I see as
well. But in my cgit link, why would tail_tag be there?
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/tree/include/net/dsa.h#n93?id=2ecbc1f684482b4ed52447a39903bd9b0f222898
I think either cgit is plainly dumb at showing the kernel tree at a
particular commit, or I'm plainly incapable of using it.
next prev parent reply other threads:[~2020-10-16 21:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 16:28 [PATCH net] net: dsa: point out the tail taggers Christian Eggers
2020-10-16 16:46 ` Florian Fainelli
2020-10-16 16:56 ` Vladimir Oltean
2020-10-16 17:25 ` kernel test robot
2020-10-16 17:33 ` Vladimir Oltean
2020-10-16 20:14 ` Andrew Lunn
2020-10-16 20:19 ` Vladimir Oltean
2020-10-16 21:03 ` Andrew Lunn
2020-10-16 21:16 ` Vladimir Oltean
2020-10-16 21:33 ` Vladimir Oltean [this message]
2020-10-16 22:56 ` 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=20201016213302.yeesw4jbw3rzfluf@skbuf \
--to=olteanv@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=ceggers@arri.de \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@microchip.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).