From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Łukasz Bartosik" <ukaszb@chromium.org>
Cc: Tzung-Bi Shih <tzungbi@kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Lee Jones <lee@kernel.org>, Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Abhishek Pandit-Subedi <abhishekpandit@chromium.org>,
Pavan Holla <pholla@chromium.org>,
linux-usb@vger.kernel.org, chrome-platform@lists.linux.dev
Subject: Re: [PATCH v5 2/8] platform/chrome: Update EC feature flags
Date: Fri, 6 Sep 2024 16:07:46 +0200 [thread overview]
Message-ID: <2024090608-slick-shaft-1c8b@gregkh> (raw)
In-Reply-To: <CALwA+NbiW+Gt9fi6Y+_xJFUEQWZFp5cvB5kqw_LVd4Mcf03Xtw@mail.gmail.com>
On Fri, Sep 06, 2024 at 03:53:06PM +0200, Łukasz Bartosik wrote:
> On Fri, Sep 6, 2024 at 10:44 AM Tzung-Bi Shih <tzungbi@kernel.org> wrote:
> >
> > On Tue, Sep 03, 2024 at 04:30:27PM +0000, Łukasz Bartosik wrote:
> > > From: Pavan Holla <pholla@chromium.org>
> > >
> > > Define EC_FEATURE_UCSI_PPM to enable usage of the cros_ec_ucsi
> > > driver. Also, add any feature flags that are implemented by the EC
> > > but are missing in the kernel header.
> > >
> > > Signed-off-by: Pavan Holla <pholla@chromium.org>
> >
> > Same as previous patch, it needs your S-o-b tag at the end. See [1].
> >
> > [1]: https://www.kernel.org/doc/html/latest/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by
>
> I have not added any modifications to this patch. I understand that my
> S-o-b tag is not needed in such a case. Is that not correct ?
If you are forwarding on patches from someone else, yes, you HAVE TO
sign off on it as well saying that you are allowed to do the forwarding.
thanks,
greg k-h
next prev parent reply other threads:[~2024-09-06 14:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 16:30 [PATCH v5 0/8] usb: typec: Implement UCSI driver for ChromeOS Łukasz Bartosik
2024-09-03 16:30 ` [PATCH v5 1/8] platform/chrome: Update ChromeOS EC header for UCSI Łukasz Bartosik
2024-09-06 8:44 ` Tzung-Bi Shih
2024-09-06 13:01 ` Łukasz Bartosik
2024-09-03 16:30 ` [PATCH v5 2/8] platform/chrome: Update EC feature flags Łukasz Bartosik
2024-09-06 8:44 ` Tzung-Bi Shih
2024-09-06 13:53 ` Łukasz Bartosik
2024-09-06 14:07 ` Greg Kroah-Hartman [this message]
2024-09-06 15:11 ` Łukasz Bartosik
2024-09-03 16:30 ` [PATCH v5 3/8] usb: typec: ucsi: Implement ChromeOS UCSI driver Łukasz Bartosik
2024-09-05 11:23 ` Heikki Krogerus
2024-09-06 14:19 ` Heikki Krogerus
2024-09-06 15:19 ` Łukasz Bartosik
2024-09-03 16:30 ` [PATCH v5 4/8] usb: typec: cros_ec_ucsi: Use complete instead of resume Łukasz Bartosik
2024-09-03 16:30 ` [PATCH v5 5/8] usb: typec: cros_ec_ucsi: Add trace events Łukasz Bartosik
2024-09-03 16:30 ` [PATCH v5 6/8] usb: typec: cros_ec_ucsi: Add netlink Łukasz Bartosik
2024-09-03 16:30 ` [PATCH v5 7/8] mfd: cros_ec: Load cros_ec_ucsi on supported ECs Łukasz Bartosik
2024-09-03 16:30 ` [PATCH v5 8/8] mfd: cros_ec: Don't load charger with UCSI Łukasz Bartosik
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=2024090608-slick-shaft-1c8b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=abhishekpandit@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=lee@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pholla@chromium.org \
--cc=tzungbi@kernel.org \
--cc=ukaszb@chromium.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