From: David Miller <davem@davemloft.net>
To: colin.king@canonical.com
Cc: saeedm@mellanox.com, matanb@mellanox.com, leonro@mellanox.com,
ilant@mellanox.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][-next] net/mlx5: fix spelling mistake: "Allodating" -> "Allocating"
Date: Sat, 01 Jul 2017 14:40:03 -0700 (PDT) [thread overview]
Message-ID: <20170701.144003.1643313481741710568.davem@davemloft.net> (raw)
In-Reply-To: <20170630105922.10397-1-colin.king@canonical.com>
From: Colin King <colin.king@canonical.com>
Date: Fri, 30 Jun 2017 11:59:22 +0100
> From: Colin Ian King <colin.king@canonical.com>
>
> Trivial fix to spelling mistake in mlx5_core_dbg debug message
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Applied, thanks Colin.
Mellanox folks, I don't like how these lib/ objects are built.
I absolutely depend upon being able to try and build individual
object files, by name, in order to quickly smoke-test patches.
Like this:
[davem@kkuri net-next]$ make drivers/net/ethernet/mellanox/mlx5/core/lib/gid.o
But I can't for these files:
scripts/Makefile.build:44: drivers/net/ethernet/mellanox/mlx5/core/lib/Makefile: No such file or directory
make[1]: *** No rule to make target 'drivers/net/ethernet/mellanox/mlx5/core/lib/Makefile'. Stop.
Makefile:1663: recipe for target 'drivers/net/ethernet/mellanox/mlx5/core/lib/gid.o' failed
Please fix this so that I can build all object files by name in this driver
again.
Thanks.
next prev parent reply other threads:[~2017-07-01 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 10:59 [PATCH][-next] net/mlx5: fix spelling mistake: "Allodating" -> "Allocating" Colin King
2017-06-30 18:55 ` Ilan Tayari
2017-07-01 21:40 ` David Miller [this message]
2017-07-02 8:35 ` Saeed Mahameed
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=20170701.144003.1643313481741710568.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=colin.king@canonical.com \
--cc=ilant@mellanox.com \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matanb@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.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).