From: Yifeng Li <tomli@tomli.me>
To: Jiri Kosina <trivial@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-fbdev@vger.kernel.org, devel@driverdev.osuosl.org
Cc: Yifeng Li <tomli@tomli.me>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Teddy Wang <teddy.wang@siliconmotion.com>,
linux-kernel@vger.kernel.org
Subject: [RESEND][PATCH 0/2] staging: sm750fb: trivial style fixes.
Date: Sun, 03 Mar 2019 16:55:30 +0000 [thread overview]
Message-ID: <20190303165532.23727-1-tomli@tomli.me> (raw)
Hello.
From January to February, there have been two trivial sm750fb patches
submitted to linux-fbdev, one by me, one by Jin Chen, but both without
any response. Further, it seems both maintainers, Sudip Mukherjee and
Teddy Wang, are currently unavailable, getting an "Ack-by" would be
unfeasible.
Since they're extremely trivial. Hereby, I picked them up, reworded
commit message, and now resubmit them as trivial patches, and send them
to trivial@kernel.org. I hope it could be directly applied by either a
fbdev, a staging maintainer or by Jiri Kosina.
Thanks for your time!
Yifeng Li (2):
staging: sm750fb: trivial comment indention fix.
staging: sm750fb: trivial Camel Case removal for setDisplayControl().
drivers/staging/sm750fb/ddk750_display.c | 6 ++---
drivers/staging/sm750fb/sm750_accel.c | 32 ++++++++++++------------
2 files changed, 19 insertions(+), 19 deletions(-)
--
2.20.1
next reply other threads:[~2019-03-03 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 16:55 Yifeng Li [this message]
2019-03-03 16:55 ` [RESEND][PATCH 1/2] staging: sm750fb: trivial comment indention fix Yifeng Li
2019-03-03 16:55 ` [RESEND][PATCH 2/2] staging: sm750fb: trivial Camel Case removal for setDisplayControl() Yifeng Li
2019-03-07 20:22 ` Greg Kroah-Hartman
2019-03-20 12:36 ` Dan Carpenter
2019-03-03 17:56 ` [RESEND][PATCH 0/2] staging: sm750fb: trivial style fixes Greg Kroah-Hartman
2019-03-20 5:13 ` Greg Kroah-Hartman
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=20190303165532.23727-1-tomli@tomli.me \
--to=tomli@tomli.me \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.com \
--cc=trivial@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 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).