From: Marcel Holtmann <marcel@holtmann.org>
To: David Miller <davem@davemloft.net>
Cc: sjur.brandeland@stericsson.com, netdev@vger.kernel.org,
daniel.martensson@stericsson.com, sjurbr@gmail.com
Subject: Re: [PATCH net-next-2.6 v7 04/12] net-caif: add CAIF Link layer device header files
Date: Mon, 29 Mar 2010 18:29:27 -0700 [thread overview]
Message-ID: <1269912567.11714.223.camel@localhost.localdomain> (raw)
In-Reply-To: <20100329.171108.98400982.davem@davemloft.net>
Hi Dave,
> > +#endif /* CAIF_DEVICE_H_ */
> > +
>
> There are extra empty newlines at the end of several files
> just like this here, GIT warns about this when I try to
> apply your patches, therefore please fix this.
>
> It happens in several files in several of your patch postings,
> so please audit them all for this problem.
some editors tend to do this for no reason. I don't know which ones, but
I have seen it lately as well :(
Regards
Marcel
prev parent reply other threads:[~2010-03-30 1:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 22:11 [PATCH net-next-2.6 v7 00/12] net-caif: introducing CAIF protocol stack sjur.brandeland
2010-03-29 22:11 ` [PATCH net-next-2.6 v7 01/12] net-caif: add CAIF protocol definitions sjur.brandeland
2010-03-29 22:11 ` [PATCH net-next-2.6 v7 02/12] net-caif: add CAIF socket and configuration headers sjur.brandeland
2010-03-29 22:11 ` [PATCH net-next-2.6 v7 03/12] net-caif: add CAIF core protocol stack header files sjur.brandeland
2010-03-29 22:11 ` [PATCH net-next-2.6 v7 04/12] net-caif: add CAIF Link layer device " sjur.brandeland
2010-03-29 22:11 ` [PATCH net-next-2.6 v7 05/12] net-caif: add CAIF core protocol stack sjur.brandeland
2010-03-29 22:11 ` [PATCH net-next-2.6 v7 06/12] net-caif: add CAIF generic caif support functions sjur.brandeland
2010-03-29 22:11 ` [PATCH net-next-2.6 v7 07/12] net-caif: add CAIF device registration functionality sjur.brandeland
2010-03-29 22:11 ` [PATCH net-next-2.6 v7 08/12] net-caif: add CAIF socket implementation sjur.brandeland
2010-03-29 22:11 ` [PATCH net-next-2.6 v7 09/12] net-caif: add CAIF netdevice sjur.brandeland
2010-03-29 22:11 ` [PATCH net-next-2.6 v7 10/12] net-caif: add CAIF Kconfig and Makefiles sjur.brandeland
2010-03-29 22:11 ` [PATCH net-next-2.6 v7 11/12] net-caif: add CAIF documentation sjur.brandeland
2010-03-29 22:11 ` [PATCH net-next-2.6 v7 12/12] net-caif-driver: add CAIF serial driver (ldisc) sjur.brandeland
2010-03-30 0:11 ` [PATCH net-next-2.6 v7 05/12] net-caif: add CAIF core protocol stack David Miller
2010-03-30 0:11 ` [PATCH net-next-2.6 v7 04/12] net-caif: add CAIF Link layer device header files David Miller
2010-03-30 1:29 ` Marcel Holtmann [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=1269912567.11714.223.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=daniel.martensson@stericsson.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sjur.brandeland@stericsson.com \
--cc=sjurbr@gmail.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).