From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [jkirsher-next-queue:dev-queue 32/134] drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c:129:12: warning: 'ixgbe_get_cs4227_status' defined but not used
Date: Wed, 30 Sep 2015 13:50:45 -0700 [thread overview]
Message-ID: <1443646245.2864.29.camel@intel.com> (raw)
In-Reply-To: <8FC88943-9E70-46E7-8DE5-37E4B938A9B9@intel.com>
On Tue, 2015-09-29 at 10:08 -0700, Rustad, Mark D wrote:
> > On Sep 29, 2015, at 9:29 AM, Rustad, Mark D <
> mark.d.rustad at intel.com> wrote:
> >
> > In my repo this code is deleted by the patch "ixgbe: Remove CS4227
> diagnostic code". It almost seems like part of that patch got dropped
> or something.
>
> Yes. Most of the patch got lost. How did this happen?
It was most likely due to a merge issue, most likely due to those
function header changes we spoke about earlier.
If your latest patch has everything it supposed to, I can try re
-applying your patch. If I have issues, I will have you re-generate
your patch based on my next-queue tree.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20150930/7973055e/attachment.asc>
prev parent reply other threads:[~2015-09-30 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 6:20 [Intel-wired-lan] [jkirsher-next-queue:dev-queue 32/134] drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c:129:12: warning: 'ixgbe_get_cs4227_status' defined but not used kbuild test robot
2015-09-29 16:29 ` Rustad, Mark D
2015-09-29 17:08 ` Rustad, Mark D
2015-09-30 20:50 ` Jeff Kirsher [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=1443646245.2864.29.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=intel-wired-lan@osuosl.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: link
Be 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.