mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Mariusz Gorski <marius.gorski@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] staging: panel: Module parameters clean-up
Date: Wed, 12 Nov 2014 06:29:33 +0100	[thread overview]
Message-ID: <20141112052933.GA14818@1wt.eu> (raw)
In-Reply-To: <1415754489-9097-1-git-send-email-marius.gorski@gmail.com>

On Wed, Nov 12, 2014 at 02:08:05AM +0100, Mariusz Gorski wrote:
> This small set of patches (although it also could be a single patch...)
> rearranges groups of defines, redefines and module parameter declarations,
> so that they always appear in the same order defined by Kconfig, which
> makes it more pleasant to read and understand. It's a preparation for
> a bigger clean-up of current init code.
> 
> Mariusz Gorski (4):
>   staging: panel: Reorder initial DEFAULT_* defines
>   staging: panel: Reorder DEFAULT_* values redefines
>   staging: panel: Reorder module parameter declarations
>   staging: panel: Use better names for two defined values

Whole patchset Acked-By: Willy Tarreau <w@1wt.eu>

BTW Mariusz, please use this e-mail address instead of the meta-x.org
one in the future.

Thanks,
Willy


      parent reply	other threads:[~2014-11-12  5:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12  1:08 Mariusz Gorski
2014-11-12  1:08 ` [PATCH 1/4] staging: panel: Reorder initial DEFAULT_* defines Mariusz Gorski
2014-11-12  1:08 ` [PATCH 2/4] staging: panel: Reorder DEFAULT_* values redefines Mariusz Gorski
2014-11-12  1:08 ` [PATCH 3/4] staging: panel: Reorder module parameter declarations Mariusz Gorski
2014-11-12  1:08 ` [PATCH 4/4] staging: panel: Use better names for two defined values Mariusz Gorski
2014-11-12  5:29 ` Willy Tarreau [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=20141112052933.GA14818@1wt.eu \
    --to=w@1wt.eu \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marius.gorski@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
all inboxes | Powered by JetHome®