From: Greg KH <gregkh@linuxfoundation.org>
To: Pavel Machek <pavel@denx.de>
Cc: kernel list <linux-kernel@vger.kernel.org>,
colin.king@canonical.com, mmoese@suse.de, sashal@kernel.org
Subject: Re: 8250-men-mcb: fix signed/unsigned confusion
Date: Sat, 16 Nov 2019 14:37:48 +0100 [thread overview]
Message-ID: <20191116133748.GB454551@kroah.com> (raw)
In-Reply-To: <20191115211351.GB30273@duo.ucw.cz>
On Fri, Nov 15, 2019 at 10:13:51PM +0100, Pavel Machek wrote:
> On Fri 2019-11-15 23:09:42, Greg KH wrote:
> > On Fri, Nov 15, 2019 at 01:52:34PM +0100, Pavel Machek wrote:
> > > Hi!
> > >
> > > Commit 5210a3a722543fc25b8830d2236dcbe2c8178468 fixes part of
> > > signed/unsigned confusion, but not all of it.
> > >
> > > 8250-men-mcb: fix error checking when get_num_ports returns -ENODEV
> > > Upstream commit f50b6805dbb993152025ec04dea094c40cc93a0c
> > >
> > > Fix function returning -ENODEV to signed prototype, and make error
> > > check consistent between two functions.
> > >
> > > Signed-off-by: Pavel Machek <pavel@denx.de>
> > >
> >
> > 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
>
> Not sure what is supposed to be friendly about this bot.
How was it not? Did it not say exactly what was wrong with the patch
and how to change it to make it acceptable?
> Anyway, it would be nice if authors of
> 5210a3a722543fc25b8830d2236dcbe2c8178468 picked this up. I have no way
> to test it.
As the bot said, this patch is not acceptable as-is, sorry. There's no
way it can be 'picked up' in this format.
thanks,
greg k-h
prev parent reply other threads:[~2019-11-16 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191115125234.GC29996@duo.ucw.cz>
[not found] ` <20191115150942.GA375649@kroah.com>
2019-11-15 21:13 ` Pavel Machek
2019-11-16 13:37 ` 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=20191116133748.GB454551@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=colin.king@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmoese@suse.de \
--cc=pavel@denx.de \
--cc=sashal@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®