linux-staging.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Tanjuate Brunostar <tanjubrunostar0@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	outreachy@lists.linux.dev
Subject: Re: [PATCH v3 0/2] staging: vt6655: some checkpatch fixes in the file rxtx.c
Date: Wed, 2 Nov 2022 08:20:39 +0100	[thread overview]
Message-ID: <Y2IaR0jqcaXq2UIA@kroah.com> (raw)
In-Reply-To: <cover.1667326000.git.tanjubrunostar0@gmail.com>

On Tue, Nov 01, 2022 at 06:17:47PM +0000, Tanjuate Brunostar wrote:
> These fixes are focused on the function s_vFillRTSHead
> 
> v3: changed the function name from fill_rts_head to fill_rts_header as
> head is conventionally used in lists
> 
> v2: changed confusing changelog messages
> 
> Tanjuate Brunostar (2):
>   staging: vt6655: change the function name s_vFillRTSHead
>   staging: vt6655: Join some lines of code to avoid code lines ending in
>     (

Neither of these changes apply to my tree.  Please rebase against the
staging-next branch of the staging.git tree and resend a new version.

thanks,

greg k-h

      parent reply	other threads:[~2022-11-02  7:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 18:17 [PATCH v3 0/2] staging: vt6655: some checkpatch fixes in the file rxtx.c Tanjuate Brunostar
2022-11-01 18:17 ` [PATCH v3 1/2] staging: vt6655: change the function name s_vFillRTSHead Tanjuate Brunostar
2022-11-01 18:17 ` [PATCH v3 2/2] staging: vt6655: Join some lines of code to avoid code lines ending in ( Tanjuate Brunostar
2022-11-01 22:15 ` [PATCH v3 0/2] staging: vt6655: some checkpatch fixes in the file rxtx.c Philipp Hortmann
2022-11-02  7:19   ` Greg KH
2022-11-02  7:20 ` Greg KH [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=Y2IaR0jqcaXq2UIA@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=outreachy@lists.linux.dev \
    --cc=tanjubrunostar0@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;
as well as URLs for NNTP newsgroup(s).