From: Greg KH <gregkh@linuxfoundation.org>
To: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
Cc: johan@kernel.org, vireshk@kernel.org, elder@kernel.org,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, outreachy@lists.linux.dev
Subject: Re: [PATCH v4] staging: greybus: replace PTR_ERR() with %pe in error messages
Date: Sun, 18 Oct 2026 08:33:14 +0200 [thread overview]
Message-ID: <2026101846-surfboard-fender-a3ce@gregkh> (raw)
In-Reply-To: <atN8FallRb8IbXT0@user>
On Sat, Oct 17, 2026 at 07:15:57PM +0530, Yalagada Pavan Kumar wrote:
> On Sat, Oct 17, 2026 at 01:20:39PM +0200, Greg KH wrote:
> > On Thu, Oct 15, 2026 at 01:52:38PM +0530, pavankumaryalagada@gmail.com wrote:
> > > From: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
> > >
> > > Use %pe to print error pointers directly and display their
> > > error names.
> > >
> > > Keep PTR_ERR() calls when the numeric error value is needed
> > > for returning the error code.
> > >
> > > Signed-off-by: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
> > > ---
> > > v4:
> > > - Return error codes directly instead of storing them in ret,
> > > as suggested by Julia Lawall.
> > > - Remove the unused ret variable.
> >
> >
> > Hi,
> >
> > This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
> > a patch that has triggered this response. He used to manually respond
> > to these common problems, but in order to save his sanity (he kept
> > writing the same thing over and over, yet to different people), I was
> > created. Hopefully you will not take offence and will fix the problem
> > in your patch and resubmit it so that it can be accepted into the Linux
> > kernel tree.
> >
> > You are receiving this message because of the following common error(s)
> > as indicated below:
> >
> > - Your patch did not apply to any known trees that Greg is in control
> > of. Possibly this is because you made it against Linus's tree, not
> > the linux-next tree, which is where all of the development for the
> > next version of the kernel is at. Please refresh your patch against
> > the linux-next tree, or even better yet, the development tree
> > specified in the MAINTAINERS file for the subsystem you are submitting
> > a patch for, and resend it.
>
> This v4 patch did not apply because arche-apb-ctrl.c and arche-platform.c
> were removed by commit 2f75b2eac999.
>
> The fw-core.c changes from my earlier v1 patch present in staging/staging-next.
>
> Only the change to uart.c remains.
>
> Should i send a v5 containing only the remaining change in uart.c?
If you wish to see this patch applied, yes.
> Also, should i keep Alex Elder's Reviewed-by tag in v5?
If the only change is removal of other parts of the patch, yes.
thanks,
greg k-h
prev parent reply other threads:[~2026-10-18 6:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 8:22 pavankumaryalagada
2026-10-15 12:13 ` Alex Elder
2026-10-15 18:10 ` Julia Lawall
2026-10-15 19:57 ` Dan Carpenter
2026-10-17 11:20 ` Greg KH
2026-10-17 13:45 ` Yalagada Pavan Kumar
2026-10-18 6:33 ` 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=2026101846-surfboard-fender-a3ce@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=elder@kernel.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=pavankumaryalagada@gmail.com \
--cc=vireshk@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
all inboxes | Powered by JetHome®