From: Keller, Jacob E <jacob.e.keller@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 4/6] fm10k: update driver summary and reduce code duplication
Date: Thu, 10 Mar 2016 00:19:45 +0000 [thread overview]
Message-ID: <1457569185.5545.7.camel@intel.com> (raw)
In-Reply-To: <804857E1F29AAC47BF68C404FC60A18490D8B06D@ORSMSX105.amr.corp.intel.com>
On Wed, 2016-03-09 at 23:51 +0000, Allan, Bruce W wrote:
> >
> > -----Original Message-----
> > From: Intel-wired-lan [mailto:intel-wired-lan-bounces at lists.osuosl.
> > org] On
> > Behalf Of Allan, Bruce W
> > Sent: Thursday, February 25, 2016 1:46 PM
> > To: Singh, Krishneil K <krishneil.k.singh@intel.com>; Keller, Jacob
> > E
> > <jacob.e.keller@intel.com>; Intel Wired LAN <intel-wired-
> > lan at lists.osuosl.org>
> > Subject: Re: [Intel-wired-lan] [PATCH 4/6] fm10k: update driver
> > summary
> > and reduce code duplication
> >
> > >
> > > -----Original Message-----
> > > From: Intel-wired-lan [mailto:intel-wired-lan-bounces at lists.osuos
> > > l.org]
> > On
> > >
> > > Behalf Of Singh, Krishneil K
> > > Sent: Thursday, February 25, 2016 12:30 PM
> > > To: Keller, Jacob E; Intel Wired LAN
> > > Subject: Re: [Intel-wired-lan] [PATCH 4/6] fm10k: update driver
> > > summary
> > > and reduce code duplication
> > >
> > > -----Original Message-----
> > > From: Intel-wired-lan [mailto:intel-wired-lan-bounces at lists.osuos
> > > l.org]
> > On
> > >
> > > Behalf Of Jacob Keller
> > > Sent: Wednesday, February 10, 2016 2:46 PM
> > > To: Intel Wired LAN <intel-wired-lan@lists.osuosl.org>
> > > Subject: [Intel-wired-lan] [PATCH 4/6] fm10k: update driver
> > > summary and
> > > reduce code duplication
> > >
> > > Use DRV_SUMMARY, similar to DRV_VERSION so that we don't have to
> > > duplicate the driver summary. Also update summary to more
> > > accurately
> > > describe the driver.
> > >
> > > Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
> > > ---
> > > Tested-by: Krishneil Singh <Krishneil.k.singh@intel.com>
> > Please hold off on submitting this patch to netdev...the driver
> > summary
> > might not be
> > correct based on recent events.
> The driver summary/module description should not be changed to what
> is in this
> patch.??Expect a v2 from Jake.
>
> Bruce.
Isn't there a replacement in the queue already? I'll rework this if so,
but I was pretty sure I already did.
Thanks,
Jake
next prev parent reply other threads:[~2016-03-10 0:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 22:45 [Intel-wired-lan] [PATCH 1/6] fm10k: Avoid crashing the kernel Jacob Keller
2016-02-10 22:45 ` [Intel-wired-lan] [PATCH 2/6] fm10k: prevent possibly uninitialized variable Jacob Keller
2016-02-25 20:27 ` Singh, Krishneil K
2016-02-10 22:45 ` [Intel-wired-lan] [PATCH 3/6] fm10k: use ethtool_rxfh_indir_default for default redirection table Jacob Keller
2016-02-16 4:41 ` Jeff Kirsher
2016-02-25 20:28 ` Singh, Krishneil K
2016-02-10 22:45 ` [Intel-wired-lan] [PATCH 4/6] fm10k: update driver summary and reduce code duplication Jacob Keller
2016-02-25 20:29 ` Singh, Krishneil K
2016-02-25 21:45 ` Allan, Bruce W
2016-03-09 23:51 ` Allan, Bruce W
2016-03-10 0:19 ` Keller, Jacob E [this message]
2016-02-10 22:45 ` [Intel-wired-lan] [PATCH 5/6] fm10k: correctly clean up when init_queueing_scheme fails Jacob Keller
2016-02-25 20:30 ` Singh, Krishneil K
2016-02-10 22:45 ` [Intel-wired-lan] [PATCH 6/6] fm10k: fix a minor typo in some comments Jacob Keller
2016-02-25 20:31 ` Singh, Krishneil K
2016-02-16 3:57 ` [Intel-wired-lan] [PATCH 1/6] fm10k: Avoid crashing the kernel Jeff Kirsher
2016-02-16 18:20 ` Keller, Jacob E
2016-02-25 20:27 ` Singh, Krishneil K
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=1457569185.5545.7.camel@intel.com \
--to=jacob.e.keller@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox