All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	<intel-wired-lan-bounces@osuosl.org>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>,
	Victor Raj <victor.raj@intel.com>,
	"Michal Swiatkowski" <michal.swiatkowski@linux.intel.com>,
	Jacob Keller <jacob.e.keller@intel.com>,
	Martyna Szapar-Mudlaw <martyna.szapar-mudlaw@linux.intel.com>,
	Michal Wilczynski <michal.wilczynski@intel.com>,
	<netdev@vger.kernel.org>
Subject: Re: [PATCH iwl-next] ice: remove null checks before devm_kfree() calls
Date: Tue, 30 May 2023 13:24:03 -0700	[thread overview]
Message-ID: <8a60b531-09b2-2df4-a7bb-02e3a98e7591@intel.com> (raw)
In-Reply-To: <20230530112549.20916-1-przemyslaw.kitszel@intel.com>

On 5/30/2023 4:25 AM, Przemek Kitszel wrote:

This wasn't received by IWL; you shouldn't be send sending to the 
bounces address, please use intel-wired-lan@lists.osuosl.org

Thanks,
Tony

> We all know they are redundant.
> 
> Reviewed-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> Reviewed-by: Michal Wilczynski <michal.wilczynski@intel.com>
> Signed-off-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>


  parent reply	other threads:[~2023-05-30 20:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 11:25 [PATCH iwl-next] ice: remove null checks before devm_kfree() calls Przemek Kitszel
2023-05-30 18:10 ` Simon Horman
2023-05-30 22:06   ` Przemek Kitszel
2023-05-31  7:36     ` Simon Horman
2023-05-30 20:24 ` Tony Nguyen [this message]
2023-05-30 21:54   ` Przemek Kitszel
2023-05-30 22:10     ` Tony Nguyen

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=8a60b531-09b2-2df4-a7bb-02e3a98e7591@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=anirudh.venkataramanan@intel.com \
    --cc=intel-wired-lan-bounces@osuosl.org \
    --cc=jacob.e.keller@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=martyna.szapar-mudlaw@linux.intel.com \
    --cc=michal.swiatkowski@linux.intel.com \
    --cc=michal.wilczynski@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=victor.raj@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.