Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Mehdi Djait <mehdi.djait.k@gmail.com>
Cc: Matti Vaittinen <mazziesaccount@gmail.com>, linux-iio@vger.kernel.org
Subject: Re: [PATCH 0/1] iio: accel: kionix-kx022a: Timestamp minor fix
Date: Sat, 18 Feb 2023 17:26:09 +0000	[thread overview]
Message-ID: <20230218172609.4c613cc5@jic23-huawei> (raw)
In-Reply-To: <Y/DTfoFMkPQeZODL@carbian>

On Sat, 18 Feb 2023 14:32:46 +0100
Mehdi Djait <mehdi.djait.k@gmail.com> wrote:

> Hi Matti,
> 
> On Fri, Feb 17, 2023 at 10:04:30PM +0200, Matti Vaittinen wrote:
> > Thanks again Mehdi. It's great to have this fixed :)
> > 
> > On 2/17/23 21:19, Mehdi Djait wrote:  
> > > As discussed in [1] here is a patch to get the timestamp in the
> > > trigger handler from the driver's private data
> > > 
> > > [1] https://lore.kernel.org/linux-iio/Y+%2FLpcc0Wa2VGsGO@carbian/T/#mec923c14d1324ffabfa88dde225eeb227005b48f
> > >   
> > 
> > By the way, I don't think a cover-letter is required for single patches. You
> > can usually put the relevant information in the commit message.
> > Additionally, if there is some questions, suggestions or other relevant bits
> > you wish to say - but don't want to include in commit logs - you can usually
> > place them in the patch mail directly after the first
> > "---"
> > 
> > Eg:
> > 
> > <commit message>
> > <Signed-off-by and other tags>
> > 
> > ---
> > 
> > Here we can add a note / request if required.
> >   
> 
> Yes, that's why I sent a cover-letter, I wanted to include relevant bits
> but not in the commit message (a reference to the discussion). 
> 
> I should have sent the patch --in-reply-to the thread with the discussion 
> anyway. 

Don't do that.  Use a Link tag to the discussion instead.
Otherwise the patch series can get buried and lost.


> 
> Thank you for the help :) 
> 
> --
> Kind Regards
> Mehdi Djait


      reply	other threads:[~2023-02-18 17:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 19:19 [PATCH 0/1] iio: accel: kionix-kx022a: Timestamp minor fix Mehdi Djait
2023-02-17 19:19 ` [PATCH 1/1] iio: accel: kionix-kx022a: Get the timestamp from the driver's private data in the trigger_handler Mehdi Djait
2023-02-17 19:52   ` Matti Vaittinen
2023-02-17 19:55     ` Matti Vaittinen
2023-02-18 13:17       ` Mehdi Djait
2023-02-17 20:04 ` [PATCH 0/1] iio: accel: kionix-kx022a: Timestamp minor fix Matti Vaittinen
2023-02-18 13:32   ` Mehdi Djait
2023-02-18 17:26     ` Jonathan Cameron [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=20230218172609.4c613cc5@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=mazziesaccount@gmail.com \
    --cc=mehdi.djait.k@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