From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Yogesh Hegde <yogi.kernel@gmail.com>
Cc: Philipp Hortmann <philipp.g.hortmann@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
dan.carpenter@linaro.org,
linux-kernel-mentees@lists.linuxfoundation.org,
skhan@linuxfoundation.org, ivan.orlov0322@gmail.com
Subject: Re: [PATCH v3 0/4] Trivial code cleanup patches
Date: Mon, 19 Jun 2023 15:53:29 +0200 [thread overview]
Message-ID: <2023061922-numeric-runner-f36d@gregkh> (raw)
In-Reply-To: <ZJBc4bok1krfjqWf@zephyrusG14>
On Mon, Jun 19, 2023 at 07:19:21PM +0530, Yogesh Hegde wrote:
> Hi Greg,
> On Mon, Jun 19, 2023 at 02:57:56PM +0200, Greg Kroah-Hartman wrote:
> > On Sun, Jun 18, 2023 at 10:26:37PM +0200, Philipp Hortmann wrote:
> > > This patch series alone is fine. But when my patch series ([PATCH 0/9]
> > > staging: rtl8192e: Remove unsupported modes a and 5G) is applied before it
> > > fails as we change same lines. Will see what happens.
> >
> > Yes, none of these apply :(
> >
> > Yogesh, can you rebase this on my staging-next branch and resend?
> Sure, will rebase and resend. Did you mean staging-testing branch instead of
> staging-next branch ?
Yes, sorry.
prev parent reply other threads:[~2023-06-19 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 13:03 [PATCH v3 0/4] Trivial code cleanup patches Yogesh Hegde
2023-06-18 13:05 ` [PATCH v3 1/4] staging: rtl8192e: Rename variable SetWirelessMode Yogesh Hegde
2023-06-18 13:05 ` [PATCH v3 2/4] staging: rtl8192e: Rename variable SetBWModeHandler Yogesh Hegde
2023-06-18 13:06 ` [PATCH v3 3/4] staging: rtl8192e: Rename variable LeisurePSLeave Yogesh Hegde
2023-06-18 13:06 ` [PATCH v3 4/4] staging: rtl8192e: Rename variable InitialGainHandler Yogesh Hegde
2023-06-18 20:26 ` [PATCH v3 0/4] Trivial code cleanup patches Philipp Hortmann
2023-06-19 12:57 ` Greg Kroah-Hartman
2023-06-19 13:49 ` Yogesh Hegde
2023-06-19 13:53 ` Greg Kroah-Hartman [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=2023061922-numeric-runner-f36d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dan.carpenter@linaro.org \
--cc=ivan.orlov0322@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=philipp.g.hortmann@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=yogi.kernel@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).