From: Greg KH <gregkh@linuxfoundation.org>
To: Angelo Dureghello <angelo.dureghello@timesys.com>
Cc: linux-kernel@vger.kernel.org, Evgeniy Polyakov <zbr@ioremap.net>
Subject: Re: [PATCH] w1: ds2430: non functional fixes
Date: Fri, 6 Mar 2020 15:39:51 +0100 [thread overview]
Message-ID: <20200306143951.GA3830738@kroah.com> (raw)
In-Reply-To: <CALJHbkBcv_On-QtoQ-9kecE7f+M_UP350DXTDfNax3eVcZne7w@mail.gmail.com>
On Fri, Mar 06, 2020 at 03:21:23PM +0100, Angelo Dureghello wrote:
> Hi all,
>
> sorry, no intention to be rude, i replied previously to greg
> (email-bot message) only,
> without including all, just a mistake.
>
> Was just about asking what to do to fix the issue reported by the bot.
Do what it says, break this up into at different patches (only do one
thing per patch, and fix the subject and changelog text to be contain
the needed information, based on the links to the documentation it
provided you.
thanks,
greg k-h
prev parent reply other threads:[~2020-03-06 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 18:39 [PATCH] w1: ds2430: non functional fixes Angelo Dureghello
2020-03-05 18:45 ` Greg KH
2020-03-06 14:21 ` Angelo Dureghello
2020-03-06 14:39 ` 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=20200306143951.GA3830738@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=angelo.dureghello@timesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zbr@ioremap.net \
/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