From: Josh Law <hlcj1234567@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Josh Law <objecting@objecting.org>
Subject: Re: [PATCH] staging: axis-fifo: remove redundant goto end
Date: Mon, 9 Mar 2026 17:04:24 +0000 [thread overview]
Message-ID: <e65d636a-325c-41f4-978a-6c09a967a923@gmail.com> (raw)
In-Reply-To: <2026030928-smartly-spinster-ae05@gregkh>
9 Mar 2026 17:02:10 Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
> On Mon, Mar 09, 2026 at 04:59:58PM +0000, Josh Law wrote:
>> 9 Mar 2026 16:57:19 Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
>>
>>> On Mon, Mar 09, 2026 at 04:14:47PM +0000, Josh Law wrote:
>>>> 9 Mar 2026 16:12:17 Josh Law <hlcj1234567@gmail.com>:
>>>>
>>>>> 9 Mar 2026 16:09:27 Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
>>>>>
>>>>>> …
>>>>>
>>>>> I think I made V2s.
>>>>
>>>> Oh and also I made 10 V2 patches, come on.. atleast ONE is useful for you
>>>
>>> I have processed all pending staging patches now.
>>>
>>> thanks,
>>>
>>> greg k-h
>>
>> You've NAKed all 10 of my patches....?
>
> You have had review comments on all patches sent that I can see, did I
> miss any?
>
> thanks,
>
> greg k-h
You missed about 10 of my V2s
V/R
next prev parent reply other threads:[~2026-03-09 17:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 0:50 [PATCH] staging: axis-fifo: remove redundant goto end Josh Law
2026-03-02 9:17 ` Dan Carpenter
2026-03-09 16:09 ` Greg Kroah-Hartman
2026-03-09 16:12 ` Josh Law
2026-03-09 16:14 ` Josh Law
2026-03-09 16:57 ` Greg Kroah-Hartman
2026-03-09 16:59 ` Josh Law
2026-03-09 17:02 ` Greg Kroah-Hartman
2026-03-09 17:04 ` Josh Law [this message]
2026-03-09 17:06 ` Greg Kroah-Hartman
2026-03-09 17:09 ` Josh Law
2026-03-09 17:22 ` Josh Law
2026-03-09 22:00 ` Dan Carpenter
2026-03-09 22:02 ` Josh Law
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=e65d636a-325c-41f4-978a-6c09a967a923@gmail.com \
--to=hlcj1234567@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=objecting@objecting.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.