All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Brandenburg <martin@omnibond.com>
To: Greg KH <greg@kroah.com>
Cc: hubcap@omnibond.com, stable@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/3] orangefs: Dan Carpenter influenced cleanups...
Date: Wed, 12 Apr 2017 11:27:25 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.20.1704121127150.2509@mbmbp.sysblue.org> (raw)
In-Reply-To: <20170412130021.GA10858@kroah.com>

On Wed, 12 Apr 2017, Greg KH wrote:

> On Tue, Apr 11, 2017 at 12:41:27PM -0400, Martin Brandenburg wrote:
> > From: Mike Marshall <hubcap@omnibond.com>
> > 
> > commit 05973c2efb40122f2a9ecde2d065f7ea5068d024 upstream.
> > 
> > This patch is simlar to one Dan Carpenter sent me, cleans
> > up some return codes and whitespace errors. There was one
> > place where he thought inserting an error message into
> > the ring buffer might be too chatty, I hope I convinced him
> > othewise. As a consolation <g> I changed a truly chatty
> > error message in another location into a debug message,
> > system-admins had already yelled at me about that one...
> > 
> > Signed-off-by: Mike Marshall <hubcap@omnibond.com>
> > 
> > I have removed the return code and whitespace fixes as they do not cause
> > a real bug.  I keep the removal of an error message.  This error shows
> > up when a process dies before the OrangeFS userspace client responds.
> > This happens all the time on production systems and fills up the ring
> > buffer.
> 
> No, please keep patches identical to what is in Linus's tree.  That way
> you don't mess something up, and any future patches over the next 2+
> years the kernel tree will be around apply cleanly.
> 
> Almost every single time we "modify" a patch from what is in Linus's
> tree it is broken.
> 
> I've taken the original patch here for 4.9 and 4.10 stable trees.

I based that on this line in stable-kernel-rules.rst

 - It cannot contain any "trivial" fixes in it (spelling changes,
   whitespace cleanups, etc).

but I do see your point.  Does that just mean pure trivial patches are
inappropriate, but that if one or two trivial changes comes part and
parcel with a more significant patch it should be kept?

(Honestly what I removed are slightly more than trivial whitespace,
though I wouldn't have sent them on their own if they didn't come with
the logging change.)

Martin

> 
> thanks,
> 
> greg k-h
> 

  reply	other threads:[~2017-04-12 15:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11 16:41 [PATCH 0/3] orangefs fixes for stable Martin Brandenburg
2017-04-11 16:41 ` [PATCH 1/3] orangefs: fix memory leak of string 'new' on exit path Martin Brandenburg
2017-04-11 16:41 ` [PATCH 2/3] orangefs: Dan Carpenter influenced cleanups Martin Brandenburg
2017-04-12 13:00   ` Greg KH
2017-04-12 15:27     ` Martin Brandenburg [this message]
2017-04-12 20:03       ` Greg KH
2017-04-11 16:41 ` [PATCH 3/3] orangefs: fix buffer size mis-match between kernel space and user space Martin Brandenburg
2017-04-12 13:01 ` [PATCH 0/3] orangefs fixes for stable Greg KH

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=alpine.DEB.2.20.1704121127150.2509@mbmbp.sysblue.org \
    --to=martin@omnibond.com \
    --cc=greg@kroah.com \
    --cc=hubcap@omnibond.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=stable@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 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.