From: Stephen Hemminger <shemminger@vyatta.com>
To: "Williams, Mitch A" <mitch.a.williams@intel.com>
Cc: Jeff Garzik <jeff@garzik.org>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] e1000e: get rid of wasted space
Date: Wed, 22 Oct 2008 11:07:07 -0700 [thread overview]
Message-ID: <20081022110707.3ab8f68b@extreme> (raw)
In-Reply-To: <EA929A9653AAE14F841771FB1DE5A1365F49CD6EE4@rrsmsx501.amr.corp.intel.com>
On Wed, 22 Oct 2008 12:01:16 -0600
"Williams, Mitch A" <mitch.a.williams@intel.com> wrote:
> Jeff Garzik wrote:
>
> >
> >Stephen Hemminger wrote:
> >> The name in the ring is only used once during setup so it shouldn't
> >> be in the data structure.
> >>
> >> Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
> [snip]
> >
> >ACK
> >
> >for what it's worth... I am following DaveM's lead, and waiting until
> >net-next opens to start taking patches for 2.6.29. He wants
> >us to focus
> >on bug fixing for now.
> >
> >So, please resend once the merge window opens... thanks.
> >
>
> NAK. Seriously. Don't resend this. NAK.
>
> That string DOES get used later, like when you cat /proc/interrupts.
> So you can't allocate it on the stack. It's got to be persistent,
> just like we have it. Heck, look at the declaration for
> request_irq(). The devname param is declared as const char *.
>
> So NAK. Same for igb and ixgbe. Don't do this.
>
> -Mitch
The comments were right, this needs to stay, although it might be better
to use a bigger field to allow full width of IFNAME+5
prev parent reply other threads:[~2008-10-22 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 2:11 [PATCH] e1000e: get rid of wasted space Stephen Hemminger
2008-10-21 10:23 ` Ben Hutchings
2008-10-22 11:03 ` Jeff Garzik
2008-10-22 18:01 ` Williams, Mitch A
2008-10-22 18:07 ` Stephen Hemminger [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=20081022110707.3ab8f68b@extreme \
--to=shemminger@vyatta.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeff@garzik.org \
--cc=jesse.brandeburg@intel.com \
--cc=mitch.a.williams@intel.com \
--cc=netdev@vger.kernel.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 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).