From: Kalle Valo <kvalo@codeaurora.org>
To: John Oldman <john.oldman@polehill.co.uk>
Cc: m@bues.ch, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org,
John Oldman <john.oldman@polehill.co.uk>
Subject: Re: [PATCH] ssb: sprom: fix block comments coding style issues
Date: Tue, 28 Apr 2020 09:01:25 +0000 (UTC) [thread overview]
Message-ID: <20200428090125.9F50CC432C2@smtp.codeaurora.org> (raw)
In-Reply-To: <20200424175043.16261-1-john.oldman@polehill.co.uk>
John Oldman <john.oldman@polehill.co.uk> wrote:
> Fixed coding style issues
>
> Signed-off-by: John Oldman <john.oldman@polehill.co.uk>
Patch applied to wireless-drivers-next.git, thanks.
2aad9f81d34c ssb: sprom: fix block comments coding style issues
--
https://patchwork.kernel.org/patch/11509841/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2020-04-28 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 17:50 [PATCH] :ssb sprom.c: Fixed block comments coding style issues John Oldman
2020-04-24 23:05 ` Michael Büsch
2020-04-27 5:26 ` Kalle Valo
2020-04-28 9:01 ` Kalle Valo [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=20200428090125.9F50CC432C2@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=john.oldman@polehill.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m@bues.ch \
/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;
as well as URLs for NNTP newsgroup(s).