All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: "Enrico Weigelt, metux IT consult" <info@metux.net>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH] s390: Kconfig: pedantic cleanups
Date: Sat, 1 Jun 2019 12:56:38 +0200	[thread overview]
Message-ID: <20190601105638.GH3600@osiris> (raw)
In-Reply-To: <1551904321-23099-1-git-send-email-info@metux.net>

On Wed, Mar 06, 2019 at 09:32:01PM +0100, Enrico Weigelt, metux IT consult wrote:
> Formatting of Kconfig files doesn't look so pretty, so just
> take damp cloth and clean it up.
> 
> Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
> ---
>  arch/s390/Kconfig          |  2 +-
>  drivers/s390/block/Kconfig |  2 +-
>  drivers/s390/char/Kconfig  | 15 +++++++--------
>  drivers/s390/net/Kconfig   |  8 ++++----
>  4 files changed, 13 insertions(+), 14 deletions(-)

Applied, thanks.

      reply	other threads:[~2019-06-01 10:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06 20:32 [PATCH] s390: Kconfig: pedantic cleanups Enrico Weigelt, metux IT consult
2019-06-01 10:56 ` Heiko Carstens [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=20190601105638.GH3600@osiris \
    --to=heiko.carstens@de.ibm.com \
    --cc=info@metux.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@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.