From: Dan Carpenter <dan.carpenter@oracle.com> To: Colin King <colin.king@canonical.com> Cc: "David S . Miller" <davem@davemloft.net>, Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>, James Morris <jmorris@namei.org>, Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>, Patrick McHardy <kaber@trash.net>, netdev@vger.kernel.org, kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH][net-next] esp6: fix incorrect null pointer check on xo Date: Tue, 18 Apr 2017 23:11:20 +0300 [thread overview] Message-ID: <20170418201119.72la2hstf47dpply@mwanda> (raw) In-Reply-To: <20170418140653.8839-1-colin.king@canonical.com> It's in Steffen's tree, not the networking tree and he's not CC'd. You should really be adding Fixes tags because it helps to ensure you CC the guilty parties. regards, dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com> To: Colin King <colin.king@canonical.com> Cc: "David S . Miller" <davem@davemloft.net>, Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>, James Morris <jmorris@namei.org>, Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>, Patrick McHardy <kaber@trash.net>, netdev@vger.kernel.org, kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH][net-next] esp6: fix incorrect null pointer check on xo Date: Tue, 18 Apr 2017 20:11:20 +0000 [thread overview] Message-ID: <20170418201119.72la2hstf47dpply@mwanda> (raw) In-Reply-To: <20170418140653.8839-1-colin.king@canonical.com> It's in Steffen's tree, not the networking tree and he's not CC'd. You should really be adding Fixes tags because it helps to ensure you CC the guilty parties. regards, dan carpenter
next prev parent reply other threads:[~2017-04-18 20:12 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-04-18 14:06 [PATCH][net-next] esp6: fix incorrect null pointer check on xo Colin King 2017-04-18 14:06 ` Colin King 2017-04-18 17:12 ` David Miller 2017-04-19 5:20 ` Steffen Klassert 2017-04-18 20:11 ` Dan Carpenter [this message] 2017-04-18 20:11 ` Dan Carpenter
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=20170418201119.72la2hstf47dpply@mwanda \ --to=dan.carpenter@oracle.com \ --cc=colin.king@canonical.com \ --cc=davem@davemloft.net \ --cc=jmorris@namei.org \ --cc=kaber@trash.net \ --cc=kernel-janitors@vger.kernel.org \ --cc=kuznet@ms2.inr.ac.ru \ --cc=linux-kernel@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=yoshfuji@linux-ipv6.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.