From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] e1000_main_c_Remove checkpatch coding style errors
Date: Wed, 30 Sep 2015 15:07:46 -0700 [thread overview]
Message-ID: <1443650866.2864.32.camel@intel.com> (raw)
In-Reply-To: <560C5AFF.5080701@gmail.com>
On Wed, 2015-09-30 at 23:58 +0200, Janusz Wolak wrote:
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan at lists.osuosl.org
> http://lists.osuosl.org/mailman/listinfo/intel-wired-lan
Is your intention to do a patch for every single file? If so, stop!
You should make just one patch to resolve issues with the driver of
interest. Also, please put the patch inline rather than as
attachments.
-------------- 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/e3ba2a92/attachment.asc>
next prev parent reply other threads:[~2015-09-30 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 21:58 [Intel-wired-lan] e1000_main_c_Remove checkpatch coding style errors Janusz Wolak
2015-09-30 22:07 ` Jeff Kirsher [this message]
2015-09-30 22:15 ` Janusz Wolak
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=1443650866.2864.32.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.