public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <simon.horman@corigine.com>
To: Peter Seiderer <ps.report@gmx.net>
Cc: linux-kernel@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Yunsheng Lin <linyunsheng@huawei.com>,
	Pavel Begunkov <asml.silence@gmail.com>,
	Richard Gobert <richardbgobert@gmail.com>
Subject: Re: [PATCH v1] skbuff: remove unused HAVE_HW_TIME_STAMP feature define
Date: Mon, 24 Jul 2023 13:27:55 +0200	[thread overview]
Message-ID: <ZL5gO1PZyrYS0ft0@corigine.com> (raw)
In-Reply-To: <20230721191805.20411-1-ps.report@gmx.net>

On Fri, Jul 21, 2023 at 09:18:05PM +0200, Peter Seiderer wrote:
> Remove unused HAVE_HW_TIME_STAMP feature define (introduced by
> commit ac45f602ee3d ("net: infrastructure for hardware time stamping").
> 
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>

Hi Peter,

this patch looks good to me, however a few tweaks are needed to the
submission in order for it to enter the review pipeline, and thus
path to being accepted.

1. For networking patches, please specify the target tree.
   Fixes go to 'net'. Other patches go to 'net-next'
   This appears to be in the latter category. So:

   Subject: [PATCH net-next] ...

2. Looking at the git history of include/linux/skbuff.h,
   it seems that 'net: skbuff: is the preferred prefix.
   So:

   Subject: [PATCH net-next] net: skubff: ...

3. Please CC netdev@vger.kernel.org

   This is the most important part, else our automated systems don't see
   the patch, and it doesn't exist in the pipeline.

   As an aside, in general, and in this case, there is no need to copy
   linux-kernel@vger.kernel.org on Networking patches.

4. Please do CC parties to any patches mentioned, in this case
   ac45f602ee3d. Which I think means:

   Patrick Ohly <patrick.ohly@intel.com>

Ref: https://docs.kernel.org/process/maintainer-netdev.html

> ---
>  include/linux/skbuff.h | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
> index faaba050f843..16a49ba534e4 100644
> --- a/include/linux/skbuff.h
> +++ b/include/linux/skbuff.h
> @@ -441,8 +441,6 @@ static inline bool skb_frag_must_loop(struct page *p)
>  	     copied += p_len, p++, p_off = 0,				\
>  	     p_len = min_t(u32, f_len - copied, PAGE_SIZE))		\
>  
> -#define HAVE_HW_TIME_STAMP
> -
>  /**
>   * struct skb_shared_hwtstamps - hardware time stamps
>   * @hwtstamp:		hardware time stamp transformed into duration
> -- 
> 2.41.0
> 

      reply	other threads:[~2023-07-24 11:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21 19:18 [PATCH v1] skbuff: remove unused HAVE_HW_TIME_STAMP feature define Peter Seiderer
2023-07-24 11:27 ` Simon Horman [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=ZL5gO1PZyrYS0ft0@corigine.com \
    --to=simon.horman@corigine.com \
    --cc=asml.silence@gmail.com \
    --cc=ast@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linyunsheng@huawei.com \
    --cc=ps.report@gmx.net \
    --cc=richardbgobert@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox