From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/3] printk: Move console matching logic into a separate function
Date: Tue, 11 Feb 2020 16:26:42 +0100 [thread overview]
Message-ID: <66c67637ba097edb39efea7280989aaa20d710b1.camel@kernel.crashing.org> (raw)
In-Reply-To: <20200211142947.favkq56gkyexqkpg@pathway.suse.cz>
On Tue, 2020-02-11 at 15:29 +0100, Petr Mladek wrote:
> > @@ -2626,6 +2627,60 @@ static int __init keep_bootcon_setup(char *str)
> > + /*
> > + * Some consoles, such as pstore and netconsole, can be enabled even
> > + * without matching.
> > + */
>
> There are few lines in the patchset where the indentation is done
> by spaces instead of tabs. The above 3 lines are just one example.
Odd. Something must have gone wrong with my emacs config when I
switched laptops, I'll have a look thanks.
> I'll fix this when pushing. But please, be more careful next time ;-)
> I suggest to use some more clever editor that helps with code
> formatting.
I normally do :)
> Also I suggest to run ./scripts/checkpatch.pl on the patches
> before sending.
Yeah I never quite got that knack, I still keep forgetting ... the doom
of old habits, I didn't even when I was maintainer of arch/powerpc ...
oops :)
But yeah, I'll try to remember next time.
> Also the three patches were not send in a single thread so that
> it was harder to find all the pieces. I personally use:
>
> git format-patch --cover-letter origin/master -o some-dir
> ./scripts/checkpatch.pl some-dir/*
> $> edit some-dir/0000-*.patch
> git send-email --smtp-server=... --to= --cc= ... some-dir/*
I usually do when it's more than a couple of patches but yeah, again,
bad old habits. Sorry about that.
Cheers,
Ben.
next prev parent reply other threads:[~2020-02-11 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 4:02 Benjamin Herrenschmidt
2020-02-11 14:29 ` Petr Mladek
2020-02-11 15:26 ` Benjamin Herrenschmidt [this message]
2020-02-13 5:42 ` Sergey Senozhatsky
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=66c67637ba097edb39efea7280989aaa20d710b1.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky.work@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
Powered by JetHome