From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Badal Nilawar <badal.nilawar@intel.com>
Cc: intel-xe@lists.freedesktop.org, anshuman.gupta@intel.com,
rodrigo.vivi@intel.com, raag.jadav@intel.com,
riana.tauro@intel.com, mallesh.koujalagi@intel.com,
aravind.iddamsetty@intel.com, himal.prasad.ghimiray@intel.com
Subject: Re: [PATCH 1/2] drm/xe/i2c: Not for review, Squash of I2C/AMC series
Date: Mon, 24 Aug 2026 14:27:00 +0200 [thread overview]
Message-ID: <aow4lOTbMenEkOE6@black.igk.intel.com> (raw)
In-Reply-To: <20260823103523.554184-5-badal.nilawar@intel.com>
On Sun, Aug 23, 2026 at 04:05:25PM +0530, Badal Nilawar wrote:
> From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
This patch is not from me.
> Squash of https://patchwork.freedesktop.org/series/168930/
Why? What are you trying to achieve with this patch??????
> Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Do not use my signature!
It does not matter that the code originates from me - you can express
that in a different way in the commit message. You don't use other
peoples' signature even if the patch was intended for development
purposes only.
Thanks,
--
heikki
next prev parent reply other threads:[~2026-08-24 12:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 10:35 [PATCH 0/2] Expose AMC alert reason sysfs Badal Nilawar
2026-08-23 10:35 ` [PATCH 1/2] drm/xe/i2c: Not for review, Squash of I2C/AMC series Badal Nilawar
2026-08-23 10:30 ` sashiko-bot
2026-08-24 12:27 ` Heikki Krogerus [this message]
2026-08-24 17:03 ` Nilawar, Badal
2026-08-24 19:29 ` Rodrigo Vivi
2026-08-23 10:35 ` [PATCH 2/2] drm/xe/i2c: Expose AMC Alert reason sysfs Badal Nilawar
2026-08-23 10:29 ` sashiko-bot
2026-08-24 19:26 ` Rodrigo Vivi
2026-09-04 12:08 ` Nilawar, Badal
2026-09-04 12:40 ` Nilawar, Badal
2026-08-24 7:33 ` ✗ CI.checkpatch: warning for Expose AMC alert " Patchwork
2026-08-24 7:35 ` ✓ CI.KUnit: success " Patchwork
2026-08-24 8:13 ` ✓ Xe.CI.BAT: " Patchwork
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=aow4lOTbMenEkOE6@black.igk.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@intel.com \
--cc=badal.nilawar@intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=mallesh.koujalagi@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.