From: Stefan Wahren <stefan.wahren@i2se.com>
To: Gaston Gonzalez <gascoar@gmail.com>, linux-staging@lists.linux.dev
Cc: gregkh@linuxfoundation.org, nsaenz@kernel.org, arnd@arndb.de,
dan.carpenter@oracle.com, ojaswin98@gmail.com,
amarjargal16@gmail.com, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] staging: vchiq_arm: cleanup code alignment issues
Date: Thu, 16 Sep 2021 12:54:20 +0200 [thread overview]
Message-ID: <025d76f9-69ca-ee12-cc98-023a2ac2714d@i2se.com> (raw)
In-Reply-To: <20210915201824.413202-1-gascoar@gmail.com>
Hi Gaston,
Am 15.09.21 um 22:18 schrieb Gaston Gonzalez:
> Fix code alignment issues.
>
> Reported by checkpatch.pl
>
> Signed-off-by: Gaston Gonzalez <gascoar@gmail.com>
please:
- use a version for your patch series
- add a cover letter with version changes
- try to give reviewers more time before sending a new version
- try to avoid multiple patch series for the same driver at the same time
Regards
next prev parent reply other threads:[~2021-09-16 10:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 20:18 Gaston Gonzalez
2021-09-15 20:18 ` [PATCH 2/7] staging: vchiq_arm: remove unnecessary space in cast Gaston Gonzalez
2021-09-15 20:18 ` [PATCH 3/7] staging: vchiq_arm: clarify multiplication expressions Gaston Gonzalez
2021-09-16 11:24 ` Joe Perches
2021-09-15 20:18 ` [PATCH 4/7] staging: vchiq_arm: cleanup blank lines Gaston Gonzalez
2021-09-15 20:18 ` [PATCH 5/7] staging: vchiq_arm: fix quoted strings split across lines Gaston Gonzalez
2021-09-15 20:18 ` [PATCH 6/7] staging: vchiq_arm: remove extra blank line Gaston Gonzalez
2021-09-15 20:18 ` [PATCH 7/7] staging: vchiq_arm: use __func__ to get function name in debug message Gaston Gonzalez
2021-09-16 10:54 ` Stefan Wahren [this message]
2021-09-17 10:50 ` [PATCH 1/7] staging: vchiq_arm: cleanup code alignment issues Gaston Gonzalez
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=025d76f9-69ca-ee12-cc98-023a2ac2714d@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=amarjargal16@gmail.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.carpenter@oracle.com \
--cc=gascoar@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=nsaenz@kernel.org \
--cc=ojaswin98@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®