From: Luca Coelho <luca@coelho.fi>
To: Thomas Backlund <tmb@tmb.nu>,
"linux-firmware@kernel.org" <linux-firmware@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"kyle@infradead.org" <kyle@infradead.org>,
"jwboyer@kernel.org" <jwboyer@kernel.org>,
"ben@decadent.org.uk" <ben@decadent.org.uk>,
golan.ben.ami@intel.com
Subject: Re: pull request: iwlwifi firmware updates 2021-03-05-v2
Date: Wed, 10 Mar 2021 11:50:06 +0200 [thread overview]
Message-ID: <ef3f23b48013acf22b07e2b13be10a5cbce5fdd7.camel@coelho.fi> (raw)
In-Reply-To: <dc668115-049c-0bbc-b25e-917ccf1bbdee@tmb.nu>
On Wed, 2021-03-10 at 09:46 +0000, Thomas Backlund wrote:
> Den 10.3.2021 kl. 11:26, skrev Luca Coelho:
>
> > > Luca Coelho (3):
> > > iwlwifi: update 7265D firmware
> > >
> > > This one looks old... stuck in limbo for over 1.5 years... is that
> > > correct ?
> > > author Luca Coelho <luciano.coelho@intel.com> 2019-08-23
> > > 07:35:14 +0300
> > > committer Luca Coelho <luciano.coelho@intel.com> 2021-03-05
> > > 11:37:56 +0200
> > Oh, I just reused the commit message from before and edited it as
> > needed. Does it really matter?
>
>
> I guess not..
>
> it was more a "is it acctually a correct commit " as it looked weird
> when being so old...
>
> considering the last update to the same firmware happend on 2020-10-14
I guess I've been reusing them for quite a while. ;)
--
Luca.
next prev parent reply other threads:[~2021-03-10 9:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 11:57 pull request: iwlwifi firmware updates 2021-03-05-v2 Luca Coelho
2021-03-09 11:57 ` Luca Coelho
2021-03-10 9:09 ` Thomas Backlund
2021-03-10 9:26 ` Luca Coelho
2021-03-10 9:26 ` Luca Coelho
2021-03-10 9:46 ` Thomas Backlund
2021-03-10 9:50 ` Luca Coelho [this message]
2021-03-10 9:50 ` Luca Coelho
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=ef3f23b48013acf22b07e2b13be10a5cbce5fdd7.camel@coelho.fi \
--to=luca@coelho.fi \
--cc=ben@decadent.org.uk \
--cc=golan.ben.ami@intel.com \
--cc=jwboyer@kernel.org \
--cc=kyle@infradead.org \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tmb@tmb.nu \
/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;
as well as URLs for NNTP newsgroup(s).