From: Florian Westphal <fw@strlen.de>
To: "Peter Nørlund" <pch@ordbogen.com>
Cc: netdev@vger.kernel.org
Subject: Re: [net-next:master 647/682] fib_semantics.c:undefined reference to `__divdi3'
Date: Mon, 5 Oct 2015 23:35:20 +0200 [thread overview]
Message-ID: <20151005213520.GA12921@breakpoint.cc> (raw)
In-Reply-To: <20151005233158.2c09adce@tyr>
Peter Nørlund <pch@ordbogen.com> wrote:
> What is the proper way to supply fixes for this kind of errors? Should
> I submit the original patches again with the bug fixed, or should I
> submit a patch fixing this particular problem?
The latter, relative fix, with 'Fixes: <sha1> ("name of commit") tag'.
next prev parent reply other threads:[~2015-10-05 21:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 10:54 [net-next:master 647/682] fib_semantics.c:undefined reference to `__divdi3' kbuild test robot
2015-10-05 11:26 ` David Miller
2015-10-05 21:31 ` Peter Nørlund
2015-10-05 21:35 ` Florian Westphal [this message]
2015-10-06 6:42 ` David Miller
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=20151005213520.GA12921@breakpoint.cc \
--to=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=pch@ordbogen.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).