public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v2 2/2] staging: panel: fix lcd type in module parameters
Date: Wed, 25 Mar 2015 00:25:59 +0100	[thread overview]
Message-ID: <20150324232559.GA23298@1wt.eu> (raw)
In-Reply-To: <1427189193-7984-2-git-send-email-sudipm.mukherjee@gmail.com>

On Tue, Mar 24, 2015 at 02:56:33PM +0530, Sudip Mukherjee wrote:
> with reference to the previous patch of the series, fixed the
> lcd type in module parameters.

Sudip, it's better to avoid fragmenting patches like you did, because
it will result in a kernel state where there is an inconsistency between
the parameters actually used by the kernel and those reported by modinfo.
This can happen for example if someone does a bisect and ends up on patch
1/2 applied only. Obviously in this case there is very little harm, but
you get the idea : each patch should be a functional change, address one
thing and do it consistently. So if you change the #defines or enums or
whatever, all the locations where their old values were referenced must
be changed in the same patch, simply because in fact they are duplicate
entries. Another point is that someone who notices your patch v1 and
does not notice patch v2 could pick v1 for his kernel and end up with
something inconsistent. For this reason it would be better to merge your
patches into a single one here.

> might not apply properly to old versions, some reordering was done
> in commit <98e0e762e>

Appreciated, thanks for checking this!

Best regards,
Willy


  parent reply	other threads:[~2015-03-24 23:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24  9:26 [PATCH v2 1/2] staging: panel: fix lcd type Sudip Mukherjee
2015-03-24  9:26 ` [PATCH v2 2/2] staging: panel: fix lcd type in module parameters Sudip Mukherjee
2015-03-24 10:05   ` Dan Carpenter
2015-03-24 10:47     ` Sudip Mukherjee
2015-03-24 23:25   ` Willy Tarreau [this message]
2015-03-25  5:07     ` Sudip Mukherjee

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=20150324232559.GA23298@1wt.eu \
    --to=w@1wt.eu \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@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