DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Asaf Penso <asafp@nvidia.com>,
	dev@dpdk.org, viacheslavo@nvidia.com, matan@nvidia.com,
	rasland@nvidia.com, Michael Baum <michaelba@nvidia.com>
Subject: Re: [PATCH 1/1] doc: add steps to configure VF interface as trusted
Date: Sun, 27 Feb 2022 10:24:35 -0800	[thread overview]
Message-ID: <20220227102435.4275f945@hermes.local> (raw)
In-Reply-To: <12204927.nUPlyArG6x@thomas>

On Sun, 27 Feb 2022 18:24:42 +0100
Thomas Monjalon <thomas@monjalon.net> wrote:

> 27/02/2022 17:44, Stephen Hemminger:
> > On Sun, 27 Feb 2022 17:46:17 +0200
> > Asaf Penso <asafp@nvidia.com> wrote:
> >   
> > > +#. For each VF PCIe, using the following command to bind the driver::
> > > +
> > > +   $ echo "0000:82:00.2" >> /sys/bus/pci/drivers/mlx5_core/bind
> > > \ No newline at end of file  
> > 
> > Please change your editor and/or git settings so there is a new line
> > at the end of all text files.  
> 
> Isn't it a problem with Eclipse editor?

It is a configuration option in almost all editors:

Eclipse:
https://www.newt.com/java/eclipse/

Customize code formatting
Go to Windows > Preferences > Java > Code Style > Code Formatter and click on the Edit button.

Check New Lines > Insert new line at end of file

https://thoughtbot.com/blog/no-newline-at-end-of-file

Following the rules in your editor
You can make sure you follow this rule easily:

For Vim users, you’re all set out of the box! Just don’t change your eol setting.
For Emacs users, add (setq require-final-newline t) to your .emacs or .emacs.d/init.el file.
For Android Studio, RubyMine, PyCharm, and other IntelliJ, set “Ensure line feed at file end on Save” under “Editor.”
For Atom, you’re also all set out of the box. Keep that via the Whitespace plugin.
For VS Code, set "files.insertFinalNewline": true.
For Sublime, set the ensure_newline_at_eof_on_save option to true.
For TextMate, you can install the Avian Missing Bundle and add TM_STRIP_WHITESPACE_ON_SAVE = true to your .tm_properties file.


  reply	other threads:[~2022-02-27 18:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-27 15:46 Asaf Penso
2022-02-27 16:44 ` Stephen Hemminger
2022-02-27 17:24   ` Thomas Monjalon
2022-02-27 18:24     ` Stephen Hemminger [this message]
2022-02-28  8:13       ` Asaf Penso
2022-02-28  7:39 ` [PATCH v2] " Asaf Penso
2022-02-28  8:09   ` Asaf Penso
2022-02-28  8:11   ` [PATCH v3] " Asaf Penso
2022-03-07 12:10     ` Raslan Darawsheh
2022-03-07 10:42   ` [PATCH v2] " Raslan Darawsheh

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=20220227102435.4275f945@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=asafp@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=michaelba@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.com \
    /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).