From: Doug Ledford <dledford@redhat.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Bernard Metzler <bmt@zurich.ibm.com>,
linux-rdma@vger.kernel.org, jgg@ziepe.ca
Subject: Re: [PATCH] siw: Fix potential NULL pointer in siw_connect().
Date: Wed, 21 Aug 2019 09:39:50 -0400 [thread overview]
Message-ID: <adc716f5d2105a3cc7978873cd0f14503ae323d8.camel@redhat.com> (raw)
In-Reply-To: <20190821125645.GE3964@kadam>
[-- Attachment #1: Type: text/plain, Size: 1917 bytes --]
On Wed, 2019-08-21 at 15:56 +0300, Dan Carpenter wrote:
> On Tue, Aug 20, 2019 at 12:05:33PM -0400, Doug Ledford wrote:
> > Please take a look (I pushed it out to my wip/dl-for-rc branch) so
> > you
> > can see what I mean about how to make both a simple subject line and
> > a
> > decent commit message. Also, no final punctuation on the subject
> > line,
> > and try to keep the subject length <= 50 chars total. If you have
> > to go
> > over to have a decent subject, then so be it, but we strive for that
> > 50
> > char limit to make a subject stay on one line when displayed using
> > git
> > log --oneline.
>
> 50 is really small.
50 is the vim syntax highlighting suggested limit. You can go over,
which is why I indicated it was a soft limit, but there you are. It
leaves room for the displayed hash length to grow as well.
> If it were based on git log --oneline output the
> limit would be 67 characters.
Only if you don't include room for the hash size to grow and other
possible things, like a tag.
> If you look at actual kernel git commits
> then the average subject is 52.4 characters and probably the upper
> bound
> is 60+ or so.
Yep, probably largely due to that very same vim syntax highlighting :-)
> I was surprised how well I had done personally at generating subjects
> when I looked at my own git log.
>
> My shortest subject was commit 0746556beab1 ("bna: off by one"). That
> was from 10 years ago and is not up to my current standards. My
> longest
> was commit 49d3d6c37a32 ("drivers/misc/sgi-gru/grukdump.c: unlocking
> should be conditional in gru_dump_context()"), but originally I used
> "gru:" as the patch prefix and Andrew changed it. :P
>
> regards,
> dan carpenter
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-08-21 13:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 14:02 [PATCH] siw: Fix potential NULL pointer in siw_connect() Bernard Metzler
2019-08-20 16:05 ` Doug Ledford
2019-08-20 16:11 ` Bernard Metzler
2019-08-21 12:56 ` Dan Carpenter
2019-08-21 13:39 ` Doug Ledford [this message]
2019-08-21 14:12 ` Jason Gunthorpe
2019-08-21 16:30 ` Leon Romanovsky
2019-08-22 6:35 ` Gal Pressman
2019-08-22 7:10 ` Dan Carpenter
2019-08-22 12:02 ` Jason Gunthorpe
2019-08-22 15:02 ` Doug Ledford
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=adc716f5d2105a3cc7978873cd0f14503ae323d8.camel@redhat.com \
--to=dledford@redhat.com \
--cc=bmt@zurich.ibm.com \
--cc=dan.carpenter@oracle.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@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