netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Christian Eggers <ceggers@arri.de>,
	Woojung Huh <woojung.huh@microchip.com>,
	Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	"David S . Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: dsa: tag_ksz: KSZ8795 and KSZ9477 also use tail tags
Date: Mon, 19 Oct 2020 17:36:33 -0700	[thread overview]
Message-ID: <20201019173633.5af4ab24@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20201016172449.nvfflbbkrdbzukwz@skbuf>

On Fri, 16 Oct 2020 20:24:49 +0300 Vladimir Oltean wrote:
> On Fri, Oct 16, 2020 at 07:16:03PM +0200, Christian Eggers wrote:
> > I added it manually because the commit ID is not from Linus' tree. Is there any
> > value using Fixes tags with id's from other trees?  
> 
> Yes, that's what "git merge" does, it keeps sha1sums.
> You should check out "git log --oneline --graph --decorate" some time.
> Every maintainer's history is linear, and so is Linus's.

One thing to add is that we never rebase net or net-next trees
(some maintainers would do that occasionally).

Applied, thanks everyone!

      reply	other threads:[~2020-10-20  0:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16 17:16 [PATCH net] net: dsa: tag_ksz: KSZ8795 and KSZ9477 also use tail tags Christian Eggers
2020-10-16 17:24 ` Vladimir Oltean
2020-10-20  0:36   ` 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=20201019173633.5af4ab24@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
    --to=kuba@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=ceggers@arri.de \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --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).